diff --git a/38202-j00.docx b/38202-j00.docx new file mode 100644 index 0000000000000000000000000000000000000000..be8ca8bdf709572a6da0756e31339e6b0c47ae18 Binary files /dev/null and b/38202-j00.docx differ diff --git a/38202.tex b/38202.tex new file mode 100644 index 0000000000000000000000000000000000000000..7cd778509d558c73edd33c01d176a081d2f71a1f --- /dev/null +++ b/38202.tex @@ -0,0 +1,743 @@ +\documentclass{article} +\usepackage{3gpp} + +\begin{document} + +\configureheader{Release 19}{TS 38.202}{V19.0.0}{2025-09} +\thispagestyle{empty} + +\tstitlepage{Technical Specification Group Radio Access Network}{NR}{Services provided by the physical layer} + +\coverdisclaimner + +\newpage + +\keywordpostalofficeinternet{3GPP, New Radio, Layer 1}{}{650 Route des Lucioles - Sophia Antipolis \\ Valbonne - FRANCE \\ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16} + +\copyrightnotice + +\hfill + +\trademarkinfo + +\newpage +\tableofcontentswbar + +\newpage +\sectionnonum{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: + +\begin{itemize} + \item[] Version x.y.z + \item[] where: + + \begin{itemize} + \item[x] the first digit: + + \begin{enumerate}[label=\arabic*] + \item presented to TSG for information; + \item presented to TSG for approval; + \item or greater indicates TSG approved document under change control. + \end{enumerate} + + \item[y] the second digit is incremented for all changes of substance, i.e. + technical enhancements, corrections, updates, etc. + + \item[z] the third digit is incremented when editorial only changes have been + incorporated in the document. + \end{itemize} +\end{itemize}% Options for packages loaded elsewhere + +\newpage +\sectionnum{Scope} + +The present document is a technical specification of the services +provided by the physical layer of 5G-NR to upper layers. + +\sectionnum{References} + +The following documents contain provisions which, through reference in +this text, constitute provisions of the present document. + +\begin{enumerate}[label={[\arabic*]}] +\item 3GPP~TR~21.905: ``Vocabulary for 3GPP Specifications'' +\item 3GPP TS 38.201: ``NR; Physical Layer -- General Description'' +\item 3GPP TS 38.211: ``NR; Physical channels and modulation'' +\item 3GPP TS 38.212: ``NR; Multiplexing and channel coding'' +\item 3GPP TS 38.213: ``NR; Physical layer procedures for control'' +\item 3GPP TS 38.214: ``NR; Physical layer procedures for data'' +\item 3GPP TS 38.215: ``NR; Physical layer measurements'' +\item 3GPP TS 38.306: ``NR; User Equipment (UE) radio access capabilities'' +\end{enumerate} + +\sectionnum{Definitions of terms, symbols and abbreviations} + + +\subsection{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{]}. + +\subsection{Symbols} + +For the purposes of the present document, the following symbols apply: + +\subsection{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{]}. + +For the purposes of the present document, the following abbreviations +apply: + +\begin{abbrv} +\item[ARQ ]Automatic Repeat Request +\item[BCH] Broadcast Channel +\item[CA] Carrier Aggregation +\item[CRC] Cyclic Redundancy Check +\item[DC] Dual Connectivity +\item[DL] Downlink +\item[FEC] Forward Error Correction +\item[GF] Grant-Free +\item[MAC] Medium Access Control +\item[MIMO] Multiple Input Multiple Output +\item[PBCH] Physical Broadcast Channel +\item[PCH] Paging Channel +\item[PDCCH] Physical Downlink Control Channel +\item[PDSCH] Physical Downlink Shared Channel +\item[PRACH] Physical Random Access Channel +\item[PUCCH] Physical Uplink Control Channel +\item[PUSCH] Physical Uplink Shared Channel +\item[RACH] Random Access Channel +\item[RF] Radio Frequency +\item[RNTI] Radio Network Temporary Identifier +\item[SCH] Shared Channel +\item[SI] System Information +\item[SPS] Semi-Persistent Scheduling +\item[SRS] Sounding Reference Signal +\item[TPC] Transmit Power Control +\item[UL] Uplink +\end{abbrv} + +\sectionnum{Services and functions of the physical layer} + +\subsection{General} + +The physical layer offers data transport services to higher layers. + +The access to these services is through the use of transport channels via the MAC sub-layer. + +A transport block is defined as the data delivered by MAC layer to the physical layer and vice versa. + +\subsection{Overview of L1 functions} + +As mentioned in {[}2, TS 38.201{]}, +the physical layer is expected to perform the following functions to provide the data transport service: + +\begin{itemize} +\item[-] Error detection on the transport channel and indication to higher layers; +\item[-] FEC encoding/decoding of the transport channel; +\item[-] Hybrid ARQ soft-combining; +\item[-] Rate matching of the coded transport channel to physical channels; +\item[-] Mapping of the coded transport channel onto physical channels; +\item[-] Power weighting of physical channels; +\item[-] Modulation and demodulation of physical channels; +\item[-] Frequency and time synchronisation; +\item[-] Radio characteristics measurements and indication to higher layers; +\item[-] Multiple Input Multiple Output (MIMO) antenna processing; +\item[-] RF processing. +\end{itemize} + +L1 functions are modelled for each transport channel in clause 5. + +\sectionnum{Model of physical layer of the UE} + +The 5G-NR physical-layer model captures those characteristics of the 5G-NR physical-layer that are relevant from the point-of-view of higher layers. +More specifically, the physical-layer model captures: + +\begin{itemize} +\item[-] The structure of higher-layer data being passed down to or up from the physical layer; +\item[-] The means by which higher layers can configure the physical layer; +\item[-] The different indications (error indications, channel-quality indications, etc.) that are provided by the physical layer to higher layers. +\end{itemize} + +\subsection{Uplink model} + +\subsubsection{Uplink shared channel} + +The physical-layer model for Uplink Shared Channel transmission is described based on the corresponding PUSCH physical-layer-processing chain, see Figure 5.1.1-1. +Processing steps that are relevant for the physical-layer model, +e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer +\item[-] CRC and transport-block-error indication +\item[-] FEC and rate matching +\item[-] Data modulation +\item[-] Mapping to physical resource +\item[-] Multi-antenna processing +\item[-] Support of L1 control and Hybrid-ARQ-related signalling +\end{itemize} + +\insertcenterfigure{5.1.1-1}{Physical-layer model for UL-SCH transmission} +{0.8}{media/image3.png} + + +\subsubsection{Random access channel} + +The physical-layer model for RACH transmission is characterized by +a PRACH preamble format that consists of a cyclic prefix, +a preamble, and a guard time during which nothing is transmitted. + +\subsection{Downlink model} + +\subsubsection{Downlink shared channel} + +The physical-layer model for Downlink Shared Channel transmission is described based on the corresponding PDSCH physical-layer-processing chain, see Figure 5.2.1-1. +Processing steps that are relevant for the physical-layer model, +e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer; +\item[-] CRC and transport-block-error indication; +\item[-] FEC and rate matching; +\item[-] Data modulation; +\item[-] Mapping to physical resource; +\item[-] Multi-antenna processing; +\item[-] Support of L1 control and Hybrid-ARQ-related signalling. +\end{itemize} + +\insertcenterfigure{5.2.1-1}{Physical-layer model for DL-SCH transmission} +{0.8}{media/image4.png} + + +\subsubsection{Broadcast channel} + +The physical-layer model for BCH transmission is characterized by a fixed pre-defined transport format. +There is one transport block for the BCH every 80ms. +The BCH physical-layer model is described based on the corresponding PBCH physical-layer-processing chain, see Figure 5.2.2-1: + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer; +\item[-] CRC and transport-block-error indication; +\item[-] FEC and rate matching; +\item[-] Data modulation; +\item[-] Mapping to physical resource; +\item[-] Multi-antenna processing. +\end{itemize} + +\insertcenterfigure{5.2.2-1}{Physical-layer model for BCH transmission} +{0.8}{media/image5.png} + +\subsubsection{Paging channel} + +The physical-layer model for PCH transmission is described based on the corresponding physical-layer-processing chain, see Figure 5.2.3-1. +The PCH is carried on PDSCH. +Processing steps that are relevant for the physical-layer model, +e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer; +\item[-] CRC and transport-block-error indication; +\item[-] FEC and rate matching; +\item[-] Data modulation; +\item[-] Mapping to physical resource; +\item[-] Multi-antenna processing. +\end{itemize} + +\insertcenterfigure{5.2.3-1}{Physical-layer model for PCH transmission} +{0.8}{media/image6.png} + + +\subsection{Sidelink model} + +\subsubsection{Sidelink shared channel} + +The physical-layer model for Sidelink Shared Channel transmission is described based on the corresponding SL-SCH physical-layer-processing chain, see Figure 5.3.1-1. +Processing steps that are relevant for the physical-layer model, +e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer; +\item[-] CRC and transport-block-error indication; +\item[-] FEC and rate matching; +\item[-] Data modulation; +\item[-] Mapping to physical resource; +\item[-] Multi-antenna processing; +\item[-] Support of L1 control and Hybrid-ARQ-related signalling. +\end{itemize} + +\insertcenterfigure{5.3.1-1}{Physical-layer model for SL-SCH transmission} +{0.8}{media/image7.png} + + +\subsubsection{Broadcast channel} + +The physical-layer model for Sidelink Broadcast Channel transmission is characterized by a fixed pre-defined transport format. +There is one transport block for every slot in which the UE transmits SL-BCH, +if the UE is configured to transmit on SL-BCH. +The SL-BCH physical-layer model is described based on the corresponding SL-BCH physical-layer-processing chain, see Figure 5.3.2-1: + +\begin{itemize} +\item[-] Higher-layer data passed to/from the physical layer; +\item[-] CRC and transport-block-error indication; +\item[-] FEC and rate matching; +\item[-] Data modulation; +\item[-] Mapping to physical resource; +\item[-] Multi-antenna processing. +\end{itemize} + + +\insertcenterfigure{5.3.2-1}{Physical-layer model for SL-BCH transmission} +{0.8}{media/image8.png} + + +\sectionnum{Simultaneous transmission and reception of physical channels and physical signals} + +This clause describes the requirements from the UE to send and receive multiple physical channels and physical signals simultaneously depending on the capabilities and service requirements. +The following notation is used between both the uplink and downlink clauses below. + +\begin{itemize} +\item[-] \(p\) is the number of uplink carriers configured for the UE on which physical channels can be transmitted +\item[-] \(p'\) is the number of uplink carriers configured for the UE on which SRS can be transmitted +\item[-] \(q\) is the number of downlink carriers configured for the UE +\item[-] \(j\) is the number of cell groups configured for the UE. +\item[-] \(k\) is the number of PUCCH groups configured for the UE. +\end{itemize} + +\subsection{Uplink} + +The tables 6.1-1 and 6.1-2 describe the possible combinations of physical channels and SRS that can be sent in simultaneously in the uplink by one UE. +Table 6.1-1 introduces notation for a ``Transmission Type'' +which represents a physical channel or sounding reference signal, and any associated transport channel. +Table 6.1-2 describes the combinations of these ``Transmission Types'' +which are supported by the UE depending on capabilities {[}8, TS 38.306{]}, +and enumerates how many of each can be transmitted simultaneously. + +\centertablecaption{6.1-1}{Uplink ``Transmission Types''} +{ |p{4cm}|p{4cm}|p{4cm}|p{3cm}| }{ +\textbf{``Transmission Type''} & \textbf{Physical Channel or SRS Associated} & +\textbf{Transport Channel} & \textbf{Comment} \\ \hline +A & PRACH & RACH & Note 1, Note 3 \\ \hline +B & PUCCH & N/A & \\ \hline +C & PUSCH & UL-SCH & Note 2, Note 3 \\ \hline +D & SRS & N/A & \\ \hline +\multicolumn{4}{|p{16cm}|}{ + Note 1: RACH corresponds to contention based. + + Note 2: UCI on PUSCH without UL-SCH is possible. + + Note 3: For SCell, MsgA PRACH and MsgA PUSCH is not supported. +} \\ +} + +\centertablecaption{6.1-2}{Uplink ``Transmission Type'' combinations} +{ |p{10cm}|p{5cm}| }{ +\textbf{Supported Combinations} & \textbf{Comment} \\ \hline +\emph{j} x A & Note 1 \\ \hline +\emph{k} x B & Note 2 \\ \hline +(\(\sum_{i = 1}^{p}{m_{i})} \times\)C & Note 3, Note 4, Note 10 \\ \hline +\emph{p\textquotesingle{}} x D & Note 3, Note 5 \\ \hline +\(\widetilde{j} \times\) A + \(\widetilde{k} \times\)B & Note 6 \\ \hline +\(\widetilde{j} \times\) A + \(\widetilde{(\sum_{i = 1}^{\widetilde{p}}{{\widetilde{m}}_{i})}} \times\)C +& Note 6, Note 10 \\ \hline +\(\widetilde{j} \times\) A + \(\widetilde{p}' \times\)D & Note 6 \\ \hline +\(\widehat{k} \times\) B + \(\widehat{(\sum_{i = 1}^{\widehat{p}}{{\widehat{m}}_{i})}} \times\)C & +Note 8, Note 10 \\ \hline +B + \(\ (\sum_{i = 1}^{\widehat{p}'}{\widehat{m}}_{i}')\ \times\)C & +Note 9, Note 10 \\ +\(\widetilde{k} \times\) B + \(\widetilde{p}' \times\)D & Note 7 \\ \hline +\(\ (\sum_{i = 1}^{\widetilde{p}}{\widetilde{m}}_{i})\ \times\)C + +\(\widetilde{p}' \times\)D & Note 7, Note 10 \\ \hline +\multicolumn{2}{|p{16cm}|}{ + Note 1: The number of cell groups \emph{j} in the supported combination is subject to UE capability. + + Note 2: The number of PUCCH groups \emph{k} in the supported combination is subject to UE capability. + + Note 3: The number of carriers \emph{p,} and \emph{p\textquotesingle{}} in the supported combinations are subject to UE capability. + + Note 4: In the case there is one SUL carrier, then \emph{p}-1 would be supported. + + Note 5: UE may be configured with \emph{p\textquotesingle{}} but may also have capability to simultaneously sound less than this number. + + Note 6: Simultaneous PRACH with PUCCH (or PUSCH or SRS) is supported only in the case of inter-band CA, with \(\widetilde{j} \leq j\), \(\widetilde{k} \leq k\), \(\widetilde{p} \leq p\), and \(\widetilde{p}' \leq p\)\textquotesingle{} depending on the configuration, and subject to UE capability for parallel transmission. + + Note 7: Simultaneous SRS with PUCCH (or PUSCH) is supported only in the case of inter-band CA, with \(\widetilde{k} \leq k\), \(\widetilde{p} \leq p\), and \(\widetilde{p}' \leq p\)\textquotesingle{} depending on the configuration, and subject to UE capability for parallel transmission. + + Note 8: Simultaneous PUCCH and PUSCH(s) for the case that multiple PUCCH groups are configured and the respective PUCCH and PUSCH(s) are transmitted in the different PUCCH groups, with \(\widehat{k} < k\) and + \(\widehat{p} \leq p\). \(k\) and \(p\) are subject to UE capability for supported number of PUCCH groups and UL carriers, respectively. \(\widehat{k}\) and \(\widehat{p}\) depend on configuration. + + Note 9: Simultaneous PUCCH and PUSCH(s) within the same PUCCH group in the case of inter-band CA, \({\widehat{p}}'\ \)depending on the configuration, and subject to UE capability for parallel transmission of + PUCCH and PUSCH within the same PUCCH group. + + Note 10: Simultaneous transmission of up to 2 PUSCHs within the same active UL BWP, with + \(p,\ \widetilde{p},\ \ \widehat{p},\ \ {\widehat{p}}'\ \)depending on the configuration, + \(m_{i},\ {\widetilde{m}}_{i},\ {\widehat{m}}_{i},\ {\widehat{m}}_{i}'\) equal to 1 or 2, subject to UE capability for parallel transmission of PUSCH and PUSCH within the same active UL BWP. +} \\ +} + +\subsection{Downlink} + +The tables 6.2-1, 6.2-2 describe the possible combinations of physical +channels that can be received simultaneously in the downlink by one UE. +Table 6.2-1 introduces notation for a "Reception Type" which represents +a physical channel and any associated transport channel. Table 6.2-2 +describes the combinations of these "Reception Types" which are +supported by the UE depending on capabilities {[}8, TS 38.306{]}, and +enumerates how many of each can be received simultaneously. The UE shall +be able to receive all TBs according to the indication on PDCCH. Any +subset of the combinations specified in table 6.2-2 is also supported. + +\centertablecaption{6.2-1}{Downlink ``Reception Types''} +{ |p{3cm}|p{3cm}|p{3cm}|p{3cm}|p{3cm}| }{ +\textbf{``Reception Type''} & \textbf{Physical Channel(s)} & +\textbf{Monitored RNTI} & \textbf{Associated Transport Channel} & \textbf{Comment} \\ \hline +A & PBCH & N/A & BCH & \\ \hline +B & PDCCH+PDSCH & SI-RNTI & DL-SCH & Note 1 \\ \hline +C0 & PDCCH & P-RNTI & N/A & Note 1, Note 2 \\ \hline +C1 & PDCCH+PDSCH & P-RNTI & PCH & Note 1 \\ \hline +D0 & PDCCH+PDSCH & RA-RNTI or Temporary C-RNTI or MsgB-RNTI & DL-SCH & Note 3 \\ \hline +D1 & PDCCH+PDSCH & C-RNTI, CS-RNTI, MCS-C-RNTI & DL-SCH & \\ \hline +D2 & PDCCH & C-RNTI, CS-RNTI, MCS-C-RNTI & DL-SCH & \\ \hline +D3 & PDCCH+PDSCH & G-RNTI, G-CS-RNTI & DL-SCH & Note 6 \\ \hline +D4 & PDCCH & G-CS-RNTI & N/A & Note 7 \\ \hline +D5 & PDCCH+PDSCH & MCCH-RNTI & DL-SCH & Note 8 \\ \hline +D6 & PDCCH+PDSCH & G-RNTI & DL-SCH & Note 9 \\ \hline +D7 & PDCCH+PDSCH & C-RNTI & DL-SCH & Note 10 \\ \hline +D8 & PDCCH+PDSCH & Multicast MCCH-RNTI & DL-SCH & Note 11 \\ \hline +E & PDCCH & C-RNTI & N/A & Note 4 \\ \hline +F0 & PDCCH & Temporary C-RNTI & UL-SCH & Note 3 \\ \hline +F1 & PDCCH & C-RNTI, CS-RNTI, MCS-C-RNTI & UL-SCH & \\ \hline +F2 & PDCCH & C-RNTI, CS-RNTI & UL-SCH & Note 10 \\ \hline +G & PDCCH & SFI-RNTI & N/A & \\ \hline +H & PDCCH & INT-RNTI & N/A & \\ \hline +J0 & PDCCH & TPC-PUSCH-RNTI & N/A & \\ \hline +J1 & PDCCH & TPC-PUCCH-RNTI & N/A & \\ \hline +J2 & PDCCH & TPC-SRS-RNTI & N/A & \\ \hline +K & PDCCH & SP-CSI-RNTI & N/A & \\ \hline +L0 & PDCCH & SL-RNTI & SL-SCH & \\ \hline +L1 & PDCCH & SL-CS-RNTI & SL-SCH & \\ \hline +M & PDCCH & SL Semi-Persistent Scheduling V-RNTI & SL-SCH & Note 5 \\ \hline +N & PDCCH & PS-RNTI & N/A & \\ \hline +O & PDCCH & AI-RNTI & N/A & \\ \hline +P & PDCCH & CI-RNTI & N/A & \\ \hline +Q & PDCCH & PEI-RNTI & N/A & Note 1 \\ \hline +\multicolumn{5}{|p{16cm}|}{ + Note 1: These are received from PCell only. + + Note 2: In some cases UE is only required to monitor the short message within the DCI for P-RNTI. + + Note 3: These are received from PCell or PSCell. + + Note 4: This corresponds to PDCCH-ordered PRACH. + + Note 5: This corresponds to PDCCH scheduling LTE PC5. + + Note 6: This is for multicast in RRC connected state. + + Note 7: This corresponds to DL Semi-Persistent Scheduling release for multicast in RRC connected state. + + Note 8: This is for broadcast MCCH. + + Note 9: This is for broadcast MTCH. UE is not required to decode more than one PDSCH for MTCH simultaneously. + + Note 10: This is for small data transmission in RRC inactive state. + + Note 11: This is for multicast MCCH in RRC inactive state. +} \\ +} + +\centertablecaption{6.2-2}{Downlink ``Reception Type'' combinations} +{ |p{4cm}|p{4cm}|p{4cm}|p{3cm}| }{ +\multicolumn{3}{|p{12cm}|}{\textbf{Supported Combinations}} & +\multirow{2}{=}{\textbf{Comment}} \\ \cline{1-3} +\textbf{PCell} & \textbf{PSCell} & \textbf{SCell} & \\ \hline +\multicolumn{4}{|p{16cm}|}{1. RRC\_IDLE} \\ \hline +\multicolumn{4}{|p{16cm}|}{1.1 All UEs} \\ \hline +A + (B and/or (C1 or Q) and/or D0) + F0 & & & Note 1 \\ \hline +\multicolumn{4}{|p{16cm}|}{1.2 UEs supporting MBS broadcast reception} \\ \hline +A+D5 & & & \\ \hline +\multicolumn{4}{|p{16cm}|}{2. RRC\_INACTIVE} \\ \hline +\multicolumn{4}{|p{16cm}|}{2.1 All UEs} \\ \hline +A + (B and/or (C0 or C1 or Q) and/or (D0 or D7)) + (F0 or F2) & & & Note 1 \\ \hline +\multicolumn{4}{|p{16cm}|}{2.2 UEs supporting MBS broadcast reception} \\ \hline +A+D5 & & & \\ \hline +\multicolumn{4}{|p{16cm}|}{2.3 UE supporting MBS multicast reception} \\ \hline +A+D8 & & & \\ \hline +\multicolumn{4}{|p{16cm}|}{3. RRC\_CONNECTED} \\ \hline +(A + ((C0 + (B and/or (D0 or (m1*D1 + m2*D2 + ((m3*D3+m4*D4) or m5*(D5 or D6))))) + E + F0 + n*F1 + G + H + J0 + J1 + J2 + K + O + L0 + L1 + M + N + P) or D5)) & +(A + (D0 or (m1*D1 + m2*D2)) + E + F0 + n*F1 + G + H + J0 + J1 + J2 + K + O + N + P) & +m1*D1 + m2*D2 + ((m3*D3 + m4*D4) or m5*(D5 or D6)) + E + n*F1 + G + H + J0 + J1 + J2 + K + O + L0 + L1 + M + P & +Note 2, Note 3, Note 4, Note 5, Note 6, Note 7, Note 8, Note 9, Note 10, Note 11, Note 12, Note13, Note 14 \\ \hline +\multicolumn{4}{|p{16cm}|}{ + Note 1: UE is not required to decode more than two PDSCH simultaneously, and decoding prioritization when more than two are received is up to UE implementation. + + Note 2: For PCell, UE is not required to decode SI-RNTI PDSCH simultaneously with C-RNTI PDSCH, unless in FR1. + + Note 3: Supported combinations are subject to UE capabilities for dual connectivity, carrier aggregation, receiving of group TPC commands, pre-emption indication and dynamic SFI monitoring. + + Note 4: The values of \( m2 \leq 0 \) and \( n \leq 0 \) in the supported combinations are subject to the UE capability. + + Note 5: Support of monitoring PDCCH with SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI are subject to UE capability. + + Note 6: The values of \( m1 \leq 1 \) in the supported combinations are subject to the UE capability. + + Note 7: In Active time, a UE is not expected to monitor the DCI format for the PDCCH scrambled by PS-RNTI. + + Note 8: The PDCCH scrambled by PS-RNTI can only be configured on the PCell and PSCell. + + Note 9: For a UE supporting MBS multicast reception, the values of \( 1 \leq m3 \leq 0 \) and \( m4 \leq 0 \) are subject to UE capability and applicable to RRC connected UEs. If \( m3 = 1 \), then \( m1 \geq 1 \). + + Note 10: For a UE supporting MBS multicast or broadcast reception, the UE is not expected to be configured simultaneously with more than one component carrier for multicast or broadcast reception. + + Note 11: For a UE supporting MBS broadcast reception, the values of \( 1 \leq m5 \leq 0 \) are subject to UE capability and applicable to RRC connected UEs. If \( m5 = 1 \), then \( m1 \geq 1 \). + + Note 12: For a UE supporting MBS broadcast reception in RRC\_CONNECTED state, it is required to support reception of FDMed MCCH PDSCH and PBCH in Pcell. + + Note 13: For a UE supporting MBS multicast or broadcast reception in RRC\_CONNECTED state, it is not required to support reception of FDMed MCCH PDSCH/broadcast MTCH PDSCH/multicast MTCH PDSCH and SIB PDSCH in PCell. + + Note 14: For a UE supporting MBS multicast or broadcast reception in RRC\_CONNECTED state, it is not required to support reception of FDMed broadcast MTCH PDSCH/multicast MTCH PDSCH and PBCH in PCell. +} \\ +} + +\subsection{Sidelink} + +The tables 6.3-1 and 6.3-2 describe the possible combinations of physical channels that can be sent simultaneously in the sidelink by a UE. +Table 6.3-1 introduces notation for a sidelink ``Transmission Type'' which represents a physical channel, and any associated transport channel. +Table 6.3-2 describes the combinations of these ``Transmission Types'' which are supported by the UE depending on capabilities {[}8, TS 38.306{]}, +and enumerates how many of each can be transmitted simultaneously. + +\centertablecaption{6.3-1}{Sidelink ``Transmission Types''} +{ |p{4cm}|p{4cm}|p{4cm}|p{3cm}| }{ +\textbf{``Transmission Type''} & \textbf{Physical Channel} & +\textbf{Associated Transport Channel} & \textbf{Comment} \\ \hline +A & PSBCH & SL-BCH & \\ \hline +B & PSSCH & SL-SCH & \\ \hline +C & PSCCH & SL-SCH & \\ \hline +D & PSFCH & N/A & \\ \hline +E & SL PRS & N/A & \\ +} + +\centertablecaption{6.3-2}{Sidelink ``Transmission Type'' combinations} +{ |p{11cm}|p{4cm}| }{ +\textbf{Supported Combinations} & \textbf{Comment} \\ \hline +A & Note 2 \\ \hline +B & Note 2 \\ \hline +C & Note 2 \\ \hline +E & Note 4 \\ \hline +E & Note 5 \\ \hline +N \( \times \) D & Note 2 \\ \hline +B+C & Note 2 \\ \hline +\multicolumn{2}{|p{16cm}|}{ + Note 1: Depending on the UE capability, the UE may be able to perform simultaneous Uplink and Sidelink transmissions. If the simultaneous transmission of Sidelink and Uplink is beyond the UE capability, the one not prioritized can be dropped according to {[}TS 38.321{]}. + + Note 2: Depending on the UE capability, the UE may be able to perform simultaneous sidelink communication transmissions of the same sidelink ``Transmission Type'' combinations across multiple SL carriers. + + Note 3: Simultaneous transmissions over multiple SL carriers with one or more UL carriers is left up to UE implementation. + + Note 4: Depending on the UE capability, the UE may be able to perform simultaneous SL PRS transmission and PSSCH transmission(s) for a shared SL PRS resource pool across multiple SL carriers. + + Note 5: Depending on the UE capability, applicable for a dedicated SL PRS resource pool across multiple SL carriers. +} \\ +} + + +The tables 6.3-3 and 6.3-4 describe the possible combinations of physical channels that can be received simultaneously in the sidelink by a UE. +Table 6.3-3 introduces notation for a sidelink "Reception Type" which represents a physical channel, and any associated transport channel. +Table 6.3-4 describes the combinations of these "Reception Types" which are supported by the UE depending on capabilities {[}8, TS 38.306{]}, +and enumerates how many of each can be received simultaneously. + + +\centertablecaption{6.3-3}{Sidelink ``Reception Types''} +{ |p{4cm}|p{4cm}|p{4cm}|p{3cm}| }{ +\textbf{``Reception Type''} & \textbf{Physical Channel} & +\textbf{Associated Transport Channel} & \textbf{Comment} \\ \hline +A & PSBCH & SL-BCH & \\ \hline +B & PSSCH & SL-SCH & \\ \hline +C & PSCCH & SL-SCH & \\ \hline +D & PSFCH & N/A & \\ \hline +E & SL PRS & N/A & \\ +} + +\centertablecaption{6.3-4}{Sidelink ``Reception Type'' combinations} +{ |p{11cm}|p{4cm}| }{ +\textbf{Supported Combinations} & \textbf{Comment} \\ \hline +A & \\ \hline +B & Note 1, Note 2 \\ \hline +C & Note 1, Note 2 \\ \hline +E & Note 3, Note 5 \\ \hline +\(M_1 \times\) E & Note 4 \\ \hline +M \(\times\) D & Note 2 \\ \hline +B+C & Note 1, Note 2 \\ \hline +\multicolumn{2}{|p{16cm}|}{ + Note 1: Corresponds to simultaneous reception within one sub-channel + + Note 2: Depending on the UE capability, the UE may be able to perform simultaneous sidelink communication receptions of the same sidelink ``Reception Type'' combinations across multiple SL carriers. + + Note 3: Applicable for a shared SL PRS resource pool. Corresponds to simultaneous reception within one sub-channel. + + Note 4: Applicable for a dedicated SL PRS resource pool with \( M_1 \leq 1 \). Corresponds to simultaneous reception within one dedicated SL PRS resource pool. + + Note 5: For a shared SL PRS resource pool, depending on the UE capability, the reception(s) of SL-PRS in a single SL carrier can be simultaneously received with PSSCH in other one or more SL + carrier(s). +} \\ +} + +\sectionnum{ Measurements provided by the physical layer} + +\subsection{UE measurements} + +The list and detailed definition of UE measurements is provided in {[}7, TS 38.215{]}. + +\newpage +\sectionnonum{Annex A (informative): Change history} + +\changehistorytable{ +2017-05 & RAN1\#89 & R1-1712013 & & & & +Draft skeleton & +0.0.0 \\ \hline +2017-07 & AH\_1706 & R1-1712013 & & & & +Update for agreements from +meetings up to RAN1 NR AH2 & +0.0.1 \\ \hline +2017-08 & RAN1\#90 & R1-1713371 & & & & +Update for agreements from +meetings up to RAN1 NR AH2 & +0.0.2 \\ \hline +2017-08 & RAN1\#90 & R1-1714655 & & & & +Update with change marks removed +for RAN1 \#90 endorsement & +0.1.0 \\ \hline +2017-09 & RAN1\#90 & R1-1715320 & & & & +Updated with minor editorial changes for review after RAN1 \#90 & +0.1.1 \\ \hline +2017-09 & RAN\#77 & RP-172006 & & & & +For information to plenary & +1.0.0 \\ \hline +2017-10 & RAN1\#90b & R1-1719229 & & & & +Updated for agreements from meetings up to RAN1 \#90b & +1.0.1 \\ \hline +2017-11 & RAN1\#91 & R1-1721047 & & & & +Updated after email discussion & +1.1.0 \\ \hline +2017-12 & RAN1\#91 & R1-1721340 & & & & +Updated to reflect agreements from RAN1 \#91 & +1.2.0 \\ \hline +2017-12 & RAN\#78 & RP-172630 & & & & +Endorsed version for approval by plenary & +2.0.0 \\ \hline +2017-12 & RAN\#78 & & & & & +Approved by plenary -- Rel-15 spec under change control & +15.0.0 \\ \hline +2018-03 & RAN\#79 & RP-180200 & 0001 & - & F & +CR capturing the Jan18 ad-hoc and RAN1\#92 meeting agreements & +15.1.0 \\ \hline +2018-06 & RAN\#80 & RP-181172 & 0002 & 1 & F & +CR to 38.202 capturing the RAN1\#92bis and RAN1\#93 meeting agreements & +15.2.0 \\ \hline +2018-06 & RAN\#80 & RP-181257 & 0003 & - & B & +CR to 38.202 capturing the RAN1\#92bis and RAN1\#93 meeting agreements related to URLLC & +15.2.0 \\ \hline +2018-09 & RAN\#81 & RP-181789 & 0004 & - & B & +CR to 38.202 capturing RAN1\#94 meeting agreements & +15.3.0 \\ \hline +2018-12 & RAN\#82 & RP-182523 & 0005 & - & F & +CR to 38.202 capturing RAN1\#95 meeting agreements & +15.4.0 \\ \hline +2019-06 & RAN\#84 & RP-191277 & 0006 & - & F & +Correction to simultaneous reception of DL Channels & +15.5.0 \\ \hline +2019-06 & RAN\#84 & RP-191277 & 0007 & - & F & +CR on inclusion of TC-RNTI for monitored RNTI for UL-SCH and inclusion of monitoring PDCCH +ordering PRACH on SCell & +15.5.0 \\ \hline +2019-12 & RAN\#86 & RP-192623 & 0008 & 1 & F & +CR on simultaneous transmission of UL channels & +15.6.0 \\ \hline +2019-12 & RAN\#86 & RP-192635 & 0009 & - & B & +Introduction of two-step RACH & +16.0.0 \\ \hline +2019-12 & RAN\#86 & RP-192637 & 0010 & - & B & +Introduction of integrated access and backhaul for NR & +16.0.0 \\ \hline +2019-12 & RAN\#86 & RP-192638 & 0011 & - & B & +Introduction of V2X & +16.0.0 \\ \hline +2019-12 & RAN\#86 & RP-192639 & 0012 & - & B & +Introduction of Physical Layer Enhancements for URLLC & +16.0.0 \\ \hline +2019-12 & RAN\#86 & RP-192641 & 0013 & - & B & +Introduction of MIMO enhancements & +16.0.0 \\ \hline +2019-12 & RAN\#86 & RP-192642 & 0014 & - & B & +Introduction of UE Power Savings & +16.0.0 \\ \hline +2020-06 & RAN\#88-e & RP-200692 & 0015 & - & F & +Corrections to MIMO enhancements & +16.1.0 \\ \hline +2020-09 & RAN\#89-e & RP-201810 & 0017 & - & F & +DL Channel Combination associated with DCI format 2\_6 monitoring & +16.2.0 \\ \hline +2020-09 & RAN\#89-e & RP-201807 & 0018 & - & F & +Corrections on 5G V2X sidelink features & +16.2.0 \\ \hline +2021-12 & RAN\#94-e & RP-212960 & 0019 & - & F & +Alignment CR for TS 38.202 & +16.3.0 \\ \hline +2021-12 & RAN\#94-e & RP-212968 & 0020 & - & B & +Introduction of IIoT/URLLC enhancements in NR & +17.0.0 \\ \hline +2021-12 & RAN\#94-e & RP-212979 & 0021 & - & B & +Introduction of multicast and broadcast services & +17.0.0 \\ \hline +2022-03 & RAN\#95-e & RP-220263 & 0022 & - & F & +Corrections to NR support of multicast and broadcast services & +17.1.0 \\ \hline +2022-03 & RAN\#95-e & RP-220256 & 0023 & - & F & +Corrections on NR UE Power Saving Enhancements & +17.1.0 \\ \hline +2022-06 & RAN\#96 & RP-221612 & 0024 & - & F & +Corrections to NR support of multicast and broadcast services & +17.2.0 \\ \hline +2022-12 & RAN\#98-e & RP-222864 & 0025 & - & F & +CR on the MBS reception type combinations to TS 38.202 & +17.3.0 \\ \hline +2023-09 & RAN\#101 & RP-232450 & 0026 & - & F & +Correction on simultaneous reception of SDT and other channels in TS 38.202 & +17.4.0 \\ \hline +2023-09 & RAN\#101 & RP-232458 & 0027 & - & B & +Release 18 TS38.202 Editor CR for MIMO & +18.0.0 \\ \hline +2023-09 & RAN\#101 & RP-232469 & 0028 & - & B & +Release 18 TS38.202 Editor CR for NR sidelink evolution & +18.0.0 \\ \hline +2023-12 & RAN\#102 & RP-233723 & 0031 & 1 & A & +Correction on NR Sidelink & +18.1.0 \\ \hline +2023-12 & RAN\#102 & RP-233733 & 0032 & - & B & +Release 18 TS38.202 Editor CR for multicast in RRC\_INACTIVE state & +18.1.0 \\ \hline +2023-12 & RAN\#102 & RP-233719 & 0033 & - & F & +Release 18 TS38.202 Editor CR for SL-PRS transmission and Reception & +18.1.0 \\ \hline +2024-03 & RAN\#103 & RP-240528 & 0034 & - & F & +Release 18 TS38.202 Editor CR for simultaneous SL-PRS transmission and Reception & +18.2.0 \\ \hline +2024-06 & RAN\#104 & RP-241061 & 0035 & - & F & +Correction to 38.202 on support of combination of SL CA and SL positioning & +18.3.0 \\ \hline +2024-09 & RAN\#105 & RP-242204 & 0036 & - & F & +Rel-18 Editorial Corrections for TS 38.202 & = +18.4.0 \\ \hline +2025-09 & SA\#109 & - & - & - & - & +Update to Rel-19 version (MCC) & +19.0.0 \\ \hline +} + +\end{document} diff --git a/3gpp.sty b/3gpp.sty new file mode 100644 index 0000000000000000000000000000000000000000..5b47c54069f9134c50fe504f234ca276db7a9779 --- /dev/null +++ b/3gpp.sty @@ -0,0 +1,391 @@ +\usepackage{amsmath,amssymb} +\usepackage{graphicx} +\usepackage{geometry} +\usepackage{multirow} +\usepackage{longtable} +\usepackage{fancyhdr} +\usepackage{enumitem} +\usepackage{float} +\usepackage[labelfont=bf,font=sf]{caption} +\usepackage[colorlinks,linkcolor=black]{hyperref} % Recommended for clickable links +\usepackage{titlesec} +\usepackage{chngcntr} +\usepackage{xcolor} +\usepackage{listings} +\usepackage{iftex} + +\ifPDFTeX +\usepackage{tgheros} +\else +\usepackage[paper=portrait,pagesize]{typearea} +\usepackage{fontspec} +\setmainfont{Times New Roman} +\setsansfont{Arial} +\setmonofont{Courier New} +\fi + +\titleformat*{\section}{\LARGE\bfseries\sffamily} +\titleformat*{\subsection}{\Large\bfseries\sffamily} +\titleformat*{\subsubsection}{\large\bfseries\sffamily} + + + +\setcounter{secnumdepth}{6} +\makeatletter +\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}% + {-3.25ex\@plus -1ex \@minus -.2ex}% + {0.0001pt \@plus .2ex}% + {\sffamily\normalsize\bfseries}} +\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\z@}% + {-3.25ex\@plus -1ex \@minus -.2ex}% + {0.0001pt \@plus .2ex}% + {\sffamily\normalsize\bfseries}} +\counterwithin*{subparagraph}{paragraph} +\counterwithin*{paragraph}{subsubsection} +\makeatother + +\geometry{margin=1in} +\newcommand{\atright}[1]{% + \unskip % remove a possible space in front + \hfil % glue for centering + \makebox[0pt][r]{#1}% the tag at the right + \hfilneg % to countermand the \rightskip + \hspace{0pt}% \par removes a glob of glue + \par % ensure the line is ended +} +\renewcommand{\headrulewidth}{0pt} +\renewcommand{\footrulewidth}{0pt} +\setlength{\parindent}{0pt} + +\SetLabelAlign{myleft}{#1\hfill} +\newlist{abbrv}{itemize}{1} +\setlist[abbrv,1]{label=,labelwidth=1in,align=myleft,itemsep=0.1\baselineskip,leftmargin=!} + +\newlist{notes}{itemize}{1} +\setlist[notes]{label=,leftmargin=6em,itemsep=0.1\baselineskip,labelsep=1em} + +\newlist{ednotes}{itemize}{1} +\setlist[ednotes]{label=,leftmargin=4em,itemsep=0.1\baselineskip,labelsep=1em} + + +\newcommand{\sectionnum}[1]{ + \bigskip + \begin{minipage}{1\textwidth} + \rule{\linewidth}{0.4pt} + \vspace*{-24pt} % Negative vertical space + \section{#1} + \label{#1} + \end{minipage} +} + +\newcommand{\sectionnonum}[1]{ + \bigskip + \begin{minipage}{1\textwidth} + \rule{\linewidth}{0.4pt} + \vspace*{-24pt} % Negative vertical space + \section*{#1}\label{#1} + \addcontentsline{toc}{section}{#1} + \end{minipage} +} + +\newcommand{\asnone}[1]{ + \subparagraph*{-- \quad\quad \textit{#1}} +} + +\newcounter{insertcounter} +\newcounter{subinsertcounter} +\newcounter{subsubinsertcounter} + +\newcommand{\insertsection}[2]{ + \setcounter{insertcounter}{\value{section}} + \section*{#1~~#2} + \addcontentsline{toc}{section}{#1~~#2} + \setcounter{section}{\value{insertcounter}} +} + +\newcommand{\insertsubsection}[2]{ + \setcounter{subinsertcounter}{\value{subsection}} + \subsection*{#1~~#2} + \addcontentsline{toc}{subsection}{#1~~#2} + \setcounter{subsection}{\value{insertcounter}} +} + +\newcommand{\insertsubsubsection}[2]{ + \setcounter{subsubinsertcounter}{\value{subsubsection}} + \subsubsection*{#1~~#2} + \addcontentsline{toc}{subsubsection}{#1~~#2} + \setcounter{subsubsection}{\value{subsubinsertcounter}} +} + +\newcommand{\tableofcontentswbar}[0]{ + \rule{\linewidth}{0.4pt} + \vspace*{-24pt} % Negative vertical space + \tableofcontents +} + +\newcommand{\keywordpostalofficeinternet}[3]{ + \begin{center} + \small + \vspace*{2cm} + + Keywords + + \rule{0.3\linewidth}{0.4pt} + + {#1} + + \vspace{5cm} + + \textsf{\textbf{\textit{3GPP}}} + + \bigskip + \bigskip + + Postal address + + \rule{0.3\linewidth}{0.4pt} + + \textsf{#2} + + \bigskip + \bigskip + + 3GPP support office address + + \rule{0.3\linewidth}{0.4pt} + + \textsf{#3} + + \bigskip + \bigskip + + Internet + + \rule{0.3\linewidth}{0.4pt} + + \textsf{http://www.3gpp.org} + \end{center} +} + +\newcommand{\copyrightnotice}[0]{ + \begin{center} + \vfill + + \textsf{\textbf{\textit{Copyright Notification}}} + + \rule{\linewidth}{0.4pt} + + No part may be reproduced except as authorized by written permission.\\ + The copyright and the foregoing restriction extend to reproduction in + all media. + + \bigskip + + \textcopyright 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + + All rights reserved. + \end{center} +} + +\newcommand{\coverdisclaimner}[0]{ + {\rmfamily\scriptsize + The present document has been developed within the 3rd Generation Partnership + Project (3GPP\texttrademark) 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\texttrademark system should be obtained via the 3GPP Organizational Partners' Publications Offices. + } + + + \rule{\linewidth}{0.4pt} +} + +\newcommand{\configureheader}[4]{ + \newcommand{\specrelease}{#1} + \newcommand{\specnumber}{#2} + \newcommand{\specversion}{#3} + \newcommand{\publicationdate}{#4} + + \pagestyle{fancy} + % Clear all headers and footers (see also \fancyhf{}) + \fancyhead{}\fancyfoot{} + + \fancyhead[L]{\textsf{\textbf{#1}}} + \fancyhead[C]{\textsf{\thepage}} + \fancyhead[R]{\textsf{\textbf{3GPP #2 #3 (#4)}}} + \fancyfoot[C]{\textsf{\textbf{\textit{3GPP}}}} +} + +\newcommand{\tstitlepage}[3]{ + {\sffamily + \begin{center} + {\Huge\textbf{3GPP \specnumber}} + \atright{\Large \textbf{\specversion (\publicationdate)}} + \rule{\linewidth}{0.8pt} + \rightline{\textit{Technical Specification}}\\[40pt] + \end{center} + + \begin{flushright} + {\LARGE + \textbf{3rd Generation Partnership Project;}\\ + \textbf{#1;}\\ + \textbf{#2;}\\ + \textbf{#3}\\ + \textbf{(\specrelease)} + } + \end{flushright} + + \vspace{10mm} + + \rule{\linewidth}{0.8pt} + \includegraphics[width=0.2\linewidth]{media/image1.png} + \hfill + \includegraphics[width=0.2\linewidth]{media/image2.png} + \vfill + } +} + +\newcommand{\trtitlepage}[3]{ + {\sffamily + \begin{center} + {\Huge\textbf{3GPP \specnumber}} + \atright{\Large \textbf{\specversion (\publicationdate)}} + \rule{\linewidth}{0.8pt} + \rightline{\textit{Technical Report}}\\[40pt] + \end{center} + + \begin{flushright} + {\LARGE + \textbf{3rd Generation Partnership Project;}\\ + \textbf{#1;}\\ + \textbf{#2;}\\ + \textbf{#3}\\ + \textbf{(\specrelease)} + } + \end{flushright} + + \vspace{10mm} + + \rule{\linewidth}{0.8pt} + \includegraphics[width=0.2\linewidth]{media/image1.png} + \hfill + \includegraphics[width=0.2\linewidth]{media/image2.png} + \vfill + } +} + +\newcommand{\trademarkinfo}[0]{ + {\small + UMTS\texttrademark{} is a Trade Mark of ETSI registered for the benefit of its members + + 3GPP\texttrademark{} is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + + LTE\texttrademark{} is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + + GSM\textsuperscript{\tiny\textregistered} and the GSM logo are registered and owned by the GSM Association + } +} + + +\newcommand{\centertable}[2]{ + \begin{center} + \sffamily + \begin{longtable}{ #1 } + \hline + #2 + \hline + \end{longtable} + \end{center} +} + +\newcommand{\centertablecaption}[4]{ + \begin{center} + \sffamily + \textbf{Table #1:~~#2} + + \begin{longtable}{ #3 } + \hline + #4 + \hline + \end{longtable} + \end{center} +} + +\newcommand{\changehistorytable}[1]{ + \begin{center} + \sffamily + \footnotesize + \begin{longtable}{ |p{1.1cm}|p{1.5cm}|p{1.6cm}|p{0.6cm}|p{0.6cm}|p{0.6cm}|p{5.7cm}|p{1.4cm}| } + \hline + \multicolumn{8}{|c|}{\textbf{Change history}} \\ + \hline + \textbf{Date} & \textbf{Meeting} & \textbf{TDoc} & \textbf{CR} & \textbf{Rev} & \textbf{Cat} & + \textbf{Subject/Comment} & \textbf{New version} \\ + \hline + #1 + \hline + \end{longtable} + \end{center} +} + +\newcommand{\insertcenterfigure}[4]{ + \renewcommand{\thefigure}{#1} + \begin{figure}[H] + \centering + \includegraphics[width=#3\linewidth]{#4} + \caption{\textbf{\textsf{#2}}} + \end{figure} +} + +\newcommand{\insertreference}[1]{ + \begin{enumerate}[label={[\arabic*]}] + #1 + \end{enumerate} +} + +\newcommand{\editornote}[1]{ + \begin{ednotes} + \item[\textcolor{red}{-{}-}] \textcolor{red}{\large\textsf{Editor's Note: #1}} + \end{ednotes} +} + + +% Color palette +\definecolor{asnKeyword}{HTML}{8B0000} % maroon +\definecolor{asnComment}{HTML}{6A737D} % gray +\definecolor{asnString}{HTML}{032F62} % dark blue +\definecolor{asnBg}{HTML}{F6F8FA} % light gray background + +% Style for code blocks +\lstdefinelanguage{ASN1}{ + morekeywords={SEQUENCE,CHOICE,INTEGER,SIZE,OF}, + sensitive=true, + morecomment=[l]{--}, % ASN.1 line comments + morestring=[b]" +} + +\lstdefinestyle{asnStyle}{ + language=ASN1, + basicstyle=\ttfamily\footnotesize, + keywordstyle=\color{asnKeyword}\bfseries, + commentstyle=\color{asnComment}\itshape, + stringstyle=\color{asnString}, + backgroundcolor=\color{asnBg}, + numbers=left, + numberstyle=\scriptsize\color{asnComment}, + stepnumber=1, + numbersep=10pt, + showstringspaces=false, + tabsize=2, + frame=single, + rulecolor=\color{asnComment}, + breaklines=true, + breakatwhitespace=true, + keepspaces=true +} + +\newcommand{\asnonetitle}[1]{ + \begin{center} + \textsf{\textit{\textbf{#1}}} + \end{center} +} diff --git a/media/image1.png b/media/image1.png new file mode 100644 index 0000000000000000000000000000000000000000..c4ff1e266173bcc4b149a5030b8e25999d53be8c Binary files /dev/null and b/media/image1.png differ diff --git a/media/image2.png b/media/image2.png new file mode 100644 index 0000000000000000000000000000000000000000..d9390b6eacd4af8d94927bf992a5dafb3145c560 Binary files /dev/null and b/media/image2.png differ diff --git a/media/image3.png b/media/image3.png new file mode 100644 index 0000000000000000000000000000000000000000..1d691200eda2424f3bccfc02593b403dd8f19268 Binary files /dev/null and b/media/image3.png differ diff --git a/media/image4.png b/media/image4.png new file mode 100644 index 0000000000000000000000000000000000000000..4efbb595e22ce77fd7ad0c17bfb4999f083175f5 Binary files /dev/null and b/media/image4.png differ diff --git a/media/image5.png b/media/image5.png new file mode 100644 index 0000000000000000000000000000000000000000..39d0cbce6bf04d0e8cfc379bcba046cce14e69e3 Binary files /dev/null and b/media/image5.png differ diff --git a/media/image6.png b/media/image6.png new file mode 100644 index 0000000000000000000000000000000000000000..bab8ea692499ce9d9bfc8cece5cca32776f098ed Binary files /dev/null and b/media/image6.png differ diff --git a/media/image7.png b/media/image7.png new file mode 100644 index 0000000000000000000000000000000000000000..928728b4e5b3940a698281076ce3ae99a1b71674 Binary files /dev/null and b/media/image7.png differ diff --git a/media/image8.png b/media/image8.png new file mode 100644 index 0000000000000000000000000000000000000000..3b2a76ed0bce8fcae426bb0fe5bb023a2fdd350e Binary files /dev/null and b/media/image8.png differ