From f2324ba333176e8644c1f3a80f85339a84fe2223 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9CSasha?= Date: Sun, 23 Mar 2025 13:29:29 +0200 Subject: [PATCH] LaTeX --- specification/stage-3/38321-test.tex | 188 +++++++++++++++++++++++++++ 1 file changed, 188 insertions(+) create mode 100644 specification/stage-3/38321-test.tex diff --git a/specification/stage-3/38321-test.tex b/specification/stage-3/38321-test.tex new file mode 100644 index 0000000..673c97f --- /dev/null +++ b/specification/stage-3/38321-test.tex @@ -0,0 +1,188 @@ +\documentclass{article} +\usepackage{tikz} +\usepackage{bytefield} +\usepackage{multirow} +\usetikzlibrary{chains,arrows.meta} + +\begin{document} +\section*{Foreword} +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). +\section{Scope} +\section{References} +\section{Definitions, sumbols and abbreviations} +\subsection{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]. + +\begin{description} + \item[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. + \item[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. + \item[BWP for SRS for positioning Tx frequency hopping:] For SRS for positioning Tx frequency hopping, separate BWP + configuration outside BWP configuration for data transmission. +\end{description} + +\section{General} +\subsection{Introduction} +\subsection{MAC architecture} +\subsection{Services} +\subsection{Functions} + +The MAC sublayer supports the following functions: + +\begin{itemize} + \item mapping between logical channels and transport channels; + \item multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to + the physical layer on transport channels; + \item demultiplexing of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the + physical layer on transport channels; + \item scheduling information reporting; + \item error correction through HARQ; + \item logical channel prioritization; + \item priority handling between overlapping resources of one UE; + \item radio resource selection. +\end{itemize} + +The relevance of MAC functions for uplink, downlink, and sidelink is indicated in Table \ref{table:mac-functions-link-direction}. + +\begin{table}[ht!] +\begin{tabular}{|l|c|c|c|c|} + \hline + MAC function & Downlink & Uplink & Sidelink TX & Sidelink RX \\ + \hline + Mapping between logical channels and transport channels & X & X & X & X \\ + \hline + Multiplexing & & X & X & \\ + \hline + Demultiplexing & X & & & X \\ + \hline + Scheduling information reporting & & X & X & \\ + \hline + Error correction through HARQ & X & X & X & X \\ + \hline + Logical Channel prioritization & & X & X & \\ + \hline + Radio resource selection & & & X \\ + \hline +\end{tabular} +\caption{The link direction association of MAC functions} +\label{table:mac-functions-link-direction} +\end{table} + +\subsection{Channel structure} + +\section{MAC procedures} + +\subsubsection{Guard symbols for IAB} + +\begin{table}[ht!] + \begin{tabular}{|c|c|c|} + \hline + \multicolumn{2}{|c|}{Switching scenario} & Field for number of guard symbols in MAC CE\\ + \hline + \multirow{4}{10em}{IAB-MT operation to IAB-DU operation} & MT Rx to DU Tx & $NmbGS_1$ \\ + \cline{2-3}& MT Rx to DU Rx & $NmbGS_2$\\ + \cline{2-3}& MT Tx to DU Tx & $NmbGS_3$ \\ + \cline{2-3}& MT Tx to DU Rx & $NmbGS_4$ \\ + \hline + \multirow{4}{10em}{IAB-DU operation to IAB-MT operation} & DY Rx to MT Tx & $NmbGS_5$ \\ + \cline{2-3}& DU Rx to MR Rx & $NmbGS_6$\\ + \cline{2-3}& DU Tx to MT Tx & $NmbGS_7$ \\ + \cline{2-3}& DU Tx to MT Rx & $NmbGS_8$ \\ + \hline + \end{tabular} + \caption{Switching scenarios and relevant guard symbols for Case-1 timing mode} + \label{table:xyz1} +\end{table} + +\section{Protocol Data Units, formats and parameters} + +\subsection{Protocol Data Units} + +\subsubsection{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. + +\subsubsection{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: + +\begin{itemize} + \item A MAC subheader only (including padding); + \item A MAC subheader and a MAC SDU; + \item A MAC subheader and a MAC CE; + \item A MAC subheader and padding. +\end{itemize} + +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. + +\begin{figure}[ht!] +\centering +\begin{bytefield}[bitwidth=1.1em]{8} +\bitheader{0-7}\\ +\bitbox{1}{ R} & +\bitbox{1}{ F} & +\bitbox{6}{ LCID} \\ +\bitbox{8}{L} & +\end{bytefield} + +\caption{R/F/LCID/(eLCID)/L MAC subheader with 8-bit L field} +\end{figure} + +\subsection{BFR MAC CEs} + +\begin{figure}[ht!] + \centering + \begin{bytefield}[bitwidth=2em]{8} + \bitheader{0-7}\\ + \bitbox{1}{ $C_7$} & + \bitbox{1}{ $C_6$} & + \bitbox{1}{$C_5$} & + \bitbox{1}{ $C_4$} & + \bitbox{1}{ $C_3$} & + \bitbox{1}{ $C_2$} & + \bitbox{1}{ $C_1$} & + \bitbox{1}{ SP} \\ + \bitbox{1}{ AC} & + \bitbox{1}{ R } & + \bitbox{6}{Candidate RS ID or R bits} \\ + \wordbox[blr]{1}{$\cdots$} \\ + \bitbox{1}{ AC} & + \bitbox{1}{ R } & + \bitbox{6}{Candidate RS ID or R bits} \\ + \end{bytefield} + + \caption{BFR and Truncated BFR MAC CE with one octet Ci field} + \end{figure} + +\end{document} \ No newline at end of file -- GitLab