hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.15 Support of multimedia services | One of the most important requirements for UMTS is the capability of supporting multimedia services.
The following principles should guide and apply to the support of multimedia services in UMTS:
• Multimedia services in relation to UMTS should be standardised and handled according to emerging multimedia standards. SMG... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.16 Support of services requiring variable bit rate | • If a number of applications use VBR data flows then packet transfer mode on the radio and network side has to be considered in order to make efficient use of resources.
• If packet transfer is allowed on the radio side, a finer degree of location management is/may be needed for radio resource optimisation (if only t... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.18 GSM and UMTS cells in the same registration area | The concept of GSM and UMTS cells in the same registration area was introduced in order to minimize location update signaling when changing between GSM and UMTS systems. Especially, the lack of UMTS coverage, e.g. in-building coverage in urban or suburban areas, can lead mobiles frequently changing between GSM and UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.18.1 Open issues | The following open issues, opportunities and challenges have been identified concerning this concept:
a) Security.
In UMTS both MS authentication and network authentication is planned to be implemented. Some solutions have been proposed for MS authentication, ciphering and integrity check during change from GSM to UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.19.1 Introduction | Within release 99 it is a working assumption that existing and future multimedia protocols can be supported by the UMTS CC/SM as application layer protocols. Where terminals support voice over both CS and PS domains, MT calls currently would require separate MSISDNs. It is desirable to allow the use of a single MSISD... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6 Interoperability between GSM and UMTS | • Transparency [from a users perspective] of roaming and handover
• Re-use of existing subscription profiles
Note: This list is not exhaustive and is FFS.
This allows easier management and deployment of a new UMTS network.
UMTS is a system supporting handovers between GSM and UMTS in both directions. To support these h... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.1 Circuit Switched Handover and Roaming Principles | Introduction of a UMTS Core Network necessitates the inter-connection with legacy systems to allow inter-PLMN roaming and handover.
For ease of convergence with the existing networks and the introduction of dual mode handsets, roaming and handover to/from UMTS should be performed in the simplest manner that requires as... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2 Packet Switched Handover and Roaming Principles | The introduction of a UMTS core Network as described in section 11.1 illustrates the requirement for inter-connection with the legacy GSM system to allow inter-PLMN roaming and handover.
Even though there is no current GPRS deployment, the operator may decide to deploy a GPRS network prior to the deployment of a UMTS n... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2.1 Implications | The active PDP context resides in the same GGSN even after a handover between GSM and UMTS (both directions). This corresponds in principle to the anchor concept on the circuit switched side, but note that whereas packet sessions are long lived, the anchor MSC remains only for the duration of a CS call (typically much ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2.2 Signalling procedures | The signalling procedures shows how handover UMTS <-> GSM GPRS can be done. The parameters carried by each message is not complete and shall be seen as examples of important information carried be the messages.
The signalling sequences shows the case when the UMTS 3G_SGSN and the GPRS 2G_SGSN are located in separate “p... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 7 Network Migration And Evolution | The installed base of GSM networks will be very comprehensive at the time of the UMTS roll out. These GSM networks will co-operate very closely with and in many cases be partly integrated into the overall UMTS network. Thus network migration and evolution is a very fundamental aspect to consider when standardising UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 7.1 Network Migration Scenarios | A number of principally different network migration scenarios can be envisioned, e.g.:
• GSM to GSM release 99 (GSM operator with no UMTS licence and no UMTS roaming/handover agreements).
• GSM to GSM release 99 with support for dual mode ‘UMTS visitors’ (GSM operator with no UMTS licence but with UMTS roaming/handove... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8 Protocol Architecture | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1 IU Signalling Bearer Requirements for IP Domain | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.1 Connectionless and Connection Oriented Services | Connection-oriented and connection-less IU Signalling Bearers are required. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.2 Dynamic Bandwidth Allocation | The IU Signalling Bearer shall support rapid and flexible allocation and de-allocation of IU transport resources. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.3 Reliable Transfer | The IU Signalling Bearer shall provide reliable delivery of signalling data. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.4 Flow Control | The IU Signalling Bearer shall provide throttling mechanisms to adapt to intermittent congestion in the UTRAN or Core Network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.5 Redundancy and Load Sharing | To handle detected failures and signalling data congestion, the IU Signalling Bearer shall be capable of dynamically routing over alternate routes that minimise delay. If the delay metrics over alternative routes are identical, the IU Signalling Bearer shall be capable of spreading traffic over the identical paths, th... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.6 Large Pdu Size | To support large transactions, it is important for the IU Signalling Bearer to provide a Signalling Data Unit size, large enough to allow for all signalling messages to be transferred without fragmentation. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.7 Signalling Bearer Management | To support supervision of IU Signalling Bearers, mechanisms for managing IU Signalling Bearers shall be used to provide status information to the RANAP for individual UE(s). The signalling bearer shall also maintain a consistent UE Activation State in the access and the core network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.8 Transport Media Independence | The IU Signalling Bearer shall be independent of the underlying transport media (e.g. ATM). |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 9 History | Document history
V1.0.0
June 1999
Creation of document from 23.20, all sections except 7
V2.0.0
June 1999
Some editorial changes in order to prepare the document for the approval by the TSG SA, June 1999 meeting
V3.0.0
July 1999
Template changed, clauses and sub-clauses numbering corrected, administrative clauses added... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 1 Scope | The present document identifies the parameters of the access stratum part of the UE radio access capabilities. Furthermore, some reference configurations of these values are defined. The intention is that these configurations will be used for test specifications. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 2 References | [1] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) protocol". |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
UE User Equipment
UMTS Universal Mobile Telecommunication System
UTRAN UMTS Terrestrial Radio Access Network |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4 UE radio access capability parameters | In the following the UE radio capability parameters are defined. In addition the relevant RRC configuration parameters are shown when applicable. When using the RRC configuration parameters, UTRAN needs to respect the UE capabilities. Only parameters for which there is a need to set different values for different UEs a... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.1 PDCP parameters | Header compression algorithm supported
Defines whether header compression algorithms will be supported by the UE. If it will be supported it will be the RFC 2507 as specified in 3GPP TS 25.323. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.2 BMC parameters | No UE radio access capability parameters identified. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.3 RLC parameters | NOTE: It is FFS whether some of the RLC functions should be considered as UE capabilities.
Total RLC AM buffer size
The total buffer size across all RLC AM entities puts requirements on memory.
UTRAN controls that the UE capability can be fulfilled through the following parameters:
1. The number of RLC AM entities conf... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.4 MAC parameters | No capability parameters identified. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5 PHY parameters | |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.1 Transport channel parameters in downlink | Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant
NOTE: "Being received" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels received by the UE. "Arbitrary time instant" means that the time instant corresponding to the highest sum... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.2 Transport channel parameters in uplink | Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant
NOTE: "Being transmitted" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels transmitted by the UE. "Arbitrary time instant" means that the time instant corresponding to the hi... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.3 FDD Physical channel parameters in downlink | Maximum number of DPCH/PDSCH codes to be simultaneously received
Defines the number of codes the UE is capable of receiving in parallel. For DPCH in soft/softer handover, each DPCH is only calculated once in this capability. The capability does not include codes used for S-CCPCH.
Maximum number of physical channel bits... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.4 FDD physical channel parameters in uplink | Maximum number of DPDCH bits per 10 ms
This capability combines the 'Max number of DPDCH' and 'Minimum SF' capabilities into one capability. Note that no flexibility is lost due to this, as multiple DPDCH is only used for SF=4, i.e. when the number of DPDCH bits exceed a certain value.
The number of DPDCH channel bits ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.5 TDD physical channel parameters in downlink | Maximum number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can receive.
Maximum number of physical channels per frame
This parameter defines how many physical channels can be received during one frame. The distribution of the received physical channels on the received timeslots ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.6 TDD physical channel parameters in uplink | Maximum Number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can transmit.
Maximum number of physical channels per timeslot
Defines the maximum number physical channels transmitted in parallel during one timeslot.
Minimum SF
Defines the minimum SF supported by the UE.
Support of P... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.7 RF parameters | UE power class
The value is fixed per UE and is not related to any configuration parameter.
Radio frequency bands
Defines the uplink and downlink frequency bands supported by the UE.
Configuration parameters are UTRA RF Channel numbers for uplink and downlink, which are part of Frequency info.
Tx/Rx frequency separatio... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.6 Multi-mode related parameters | Support of UTRA FDD/TDD
Defines whether UTRA FDD and/or TDD are supported.
There is no explicit configuration parameter. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.7 Multi-RAT related parameters | Support of GSM
Defines whether GSM is supported or not.
There is no explicit configuration parameter.
Support of multi-carrier
Defines whether multi-carrier is supported or not.
There is no explicit configuration parameter. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.8 LCS related parameters | Standalone location method(s) supported
Defines if a UE can measure its location by some means unrelated to UTRAN (e.g. if the UE has access to a standalone GPS receiver).
OTDOA UE based method supported
Defines if a UE supports the OTDOA UE based schemes.
Network Assisted GPS support
Defines if a UE supports either of... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.9 Measurement related capabilities | Need for downlink compressed mode
Defines whether the UE needs compressed mode in the downlink in order to perform inter-frequency or inter-RAT measurements. There are separate parameters for measurements on each UTRA mode, on each RAT, and in each frequency band.
Need for uplink compressed mode
Defines whether the UE ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5 Possible UE radio access capability parameter settings | |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.1 Value ranges | Table 5.1: UE radio access capability parameter value ranges
UE radio access capability parameter
Value range
PDCP parameters
Header compression algorithm supported
Yes/No
RLC parameters
Total RLC AM buffer size
2,10,50,100,150,500,1000 kBytes
Maximum number of AM entities
3,4,5,6,8,16,32
PHY parameters
Transport chann... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2 Reference UE radio access capability combinations | Based on required UE radio access capabilities to support reference RABs as defined in clause 6, this clause lists reference UE Radio Access capability combinations. Subclause 5.2.1 defines reference combinations of UE radio access capability parameters common for UL and DL. Subclause 5.2.2 and 5.2.3 define reference c... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2.2 Combinations of UE Radio Access Parameters for DL | Table 5.2.2.1: UE radio access capability parameter combinations, DL parameters
Reference combination of UE Radio Access capability parameters in DL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
2048kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2.3 Combinations of UE Radio Access Parameters for UL | Table 5.2.3.1: UE radio access capability parameter combinations, UL parameters
Reference combination of UE Radio Access capability parameters in UL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being transmitted at... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 6 Usage of UE radio access capabilities | NOTE: The rationale for the parameter combination settings will be explained here. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 6.1 Examples of reference radio access bearers | In Table 6.1 reference RAB A-G are defined with some characteristics that impact the required UE Radio Access capabilities. These reference RABs shall be seen as example RABs covered by the reference UE radio access capability combinations defined in Subclause 5.2. Reference RABs for conformance testing are specified i... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 6.2 Example mappings between reference RABs and capability combinations | The following examples show how the reference RABs of Table 6.1 can be mapped to the reference UE radio access capability combinations that are listed in Clause 5.
Table 6.2: Example mappings between capability combinations and RAB combinations
Reference UE radio access capability combinations
Examples of supported ref... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 7 Mandatory UE radio access capabilities | NOTE: In this section features and requirements that are mandatory for UEs (capabilities that do not need to be signalled) will be listed for information. The normative descriptions are part of the respective specifications.
Annex A (informative):
Change history
Change history
TSG-RAN#
Version
CR
Tdoc RAN
New Version
S... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 1 Scope
| The present document investigates the current specification formats and working methods of 3GPP, and other alternative ways that are available for 3GPP to consider. It provides the following necessary considerations:
- Identification of:
- benefits of the existing ways;
- shortcomings and pain-points of the existing... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 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.
-... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 3 Definitions of terms, symbols and abbreviations
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 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].
Consumer: A person who reads the specification such as an Original Equipment Manufacturer (OEM), a ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
µ Average
σ Standard Deviation
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 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].
WYSIWYG What You See Is What You Get
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 4 Assessment of existing specification formats and working methods, and requirements for any improvements
| Editor's note: corresponds to objective 1.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 4.1 Benefits of current tools
| These benefits may in future be achieved by other means than the current tools and file formats used.
1. Familiarity
The current set of tools are well known to delegates. 3GPP TR 21.801 [2] captures all requirements and recommendations, accumulated since 1999. Further, there is institutional expertise in checking th... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 4.2 Shortcomings, pain-points and potential benefits
| Editor’s note: corresponds to objectives 1a/b
Table 4.2-1: Shortcomings, pain-points and potential benefits of current tools
#
Shortcoming / pain-point / potential benefit
Possible improvement approaches with current tools
Summary of feasibility of addressing the shortcoming / pain-point / potential benefit with c... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 4.3 Requirements Identification
| Editor's note: corresponds to Objective 1c. The clause may be further divided into different subclauses depending on the discussion.
Table 4.3-1
#
Requirement
Description
Applicable to objective 2
Applicable to objective 3
Evaluation Criteria
1
Global availability
There shall be no geographic limitations on... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5 Proposals for new formats for 3GPP specifications
| Editor's note: corresponds to objective 2.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.1 Proposal #1: OpenDocument
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.1.1 Description
| OpenDocument (ODF) is an open, XML-based file format family for office documents, established as an international standard (ISO/IEC 26300). It's free, transparent, and not controlled by any single vendor. Most importantly, it is a standardized format) which allows to develop tools to automate virtually any task. The IT... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.1.2 Figures, Diagrams and Embedded Objects
| OpenDocument supports basic shapes, as follows:
- Basic geometric shapes (Rectangles, Ellipses and Circles, Lines, etc)
- Polygons, and paths (Polylines, Polygons, Freeform Lines and curves, etc)
- Special-purpose shapes (Text boxes, Block arrows, Stars, Callouts, etc)
- And some others
However, the shapes support... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.1.3 Master Document
| An ODT master document is a special file type, with the extension .odm, used to organize and manage a large, multi-part document. The master document acts as a central container that links to separate .odt files, known as subdocuments.
The master document does not hold the content of the subdocuments directly. Instead... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.1.4 Flat XML format
| An OpenDocument flat XML file is a version of an OpenDocument Format (ODF) document that is saved as a single, uncompressed XML text file. It is an alternative to the standard ODF files (like .odt for text) which are typically saved as a compressed ZIP archive containing several XML and media files.
The "flat" version... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.2 Proposal #2: AsciiDoc
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.2.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.2.1.1 Overview
| References below provide extensive descriptions of AsciiDoc, which we don’t intent to fully copy here:
- https://asciidoc.org/
- https://asciidoc-wg.eclipse.org/
- https://gitlab.eclipse.org/eclipse/asciidoc-lang
- https://projects.eclipse.org/projects/asciidoc.asciidoc-lang
- https://docs.asciidoctor.org/asciidoc... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.2.1.2 Features of AsciiDoc
| A list of features supported by AsciiDoc is summarized in Table 5.2.1.2-1. The full list of features supported by AsciiDoc and more details on the summarized features can be found at https://docs.asciidoctor.org/asciidoc/latest/. Table 5.2.1.2-1 also provides the comparison with the language used in MarkDown.
Table 5.... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.2.1.3 Tools for AsciiDoc
| AsciiDoc syntax is plain text, so one can write an AsciiDoc document using any text editor. GitHub and GitLab support editing and previewing AsciiDoc files. The file must have a supported AsciiDoc extension (.adoc). When viewing an AsciiDoc file on these sites, one sees an HTML preview of the AsciiDoc content. In edit ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3 Proposal #3: Markdown
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.1 Introduction of Markdown
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.1.0 General
| Markdown was created by John Gruber in 2004 as an easy-to-read markup language. Popularity of Markdown eventually led to a number of implementations. The original Markdown language had ambiguities that did not get addressed and a group of people has made attempts to standardize the markup language in 2012. This is know... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.1.1 Comparison of common Markdown variants
| As stated in the previous section, there are many variants of Markdown with support for different sets of basic and extended features. Table 5.3.1.1.1-1 compares Commonmark, Gitlab-flavoured Markdown, and Pandoc Markdown, albeit not exhaustively. A cell containing an X indicates support, while an empty cell indicates l... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.2 Benefits of Markdown
| As described in the previous section, Markdown separates information from styles. A major pain point with the way specifications are written in 5G is that it is difficult to properly select styles and that time is wasted on non-technical work. Markdown has the potential to solve this challenge to writing the specificat... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.3 Base features of Markdown
| Markdown without extensions supports the following base features, described in Table 5.3.1.3-1. These features apply to the blocks named “Source” and “Images” in Figure 5.3.1.62-2. The table names each feature and demonstrates the Markdown and HTML syntax. Because the rendered output of Markdown is represented in an HT... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.4 Extended features of Markdown
| Markdown has been extended to add more features such as equation rendering, superscript and subscript, and grid tables, which enable tables with merged cells. Many popular extensions exist, including Pandoc-flavoured Markdown (https://pandoc.org/MANUAL.html) and GitLab-flavoured Markdown (https://docs.gitlab.com/user/m... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.5 3GPP extensions to Markdown with custom processing
| To support elements which are specific to 3GPP, some extensions to Markdown have been prototyped. These extensions are written in a language called Lua (https://www.lua.org/), for which an interpreter is built directly into Pandoc, the tool used to convert from Markdown to HTML. The benefit of using Lua over other lang... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.6 How to produce a specification using Markdown
| Markdown source is not presentable on its own as it is a language intended to be converted to HTML, using a simple syntax and a subset of the features of HTML. Many tools are available for converting Markdown to HTML, but the one which will be used in this solution is called Pandoc, which can be found at https://pandoc... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.7 Handling of bitmap or bit pattern elements in specifications (e.g. MAC, RLC, PDCP)
| The bitmap or bit pattern representations are used in e.g. MAC specification to describe PDU formats and control element structures using figures (created using e.g. Visio). These can be represented either via figures or via textual representations using ASCII text or ASN.1 as exemplified below.
Table 5.3.1.7-1: Examp... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.3.1.8 Front Matter
| In Markdown documents, the YAML front matter refers to a block of metadata placed at the very top of a file, typically enclosed between triple dashes (---). This section is widely supported by many Markdown parsers and tools. The front matter allows declaring structured metadata about the document—including titles, ver... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.4 Proposal #4: Multiple formats for single specification with Markdown as baseline
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.4.1 Description
| A single specification can be represented or stored in multiple file formats, where each format may contain either specific parts or elements (as shown in the table below) or a complete, self-contained version of the specification (e.g., docx or pdf etc.).
In the table below it is described how the various specificati... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5 Proposal #5: LaTeX
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5.1 Description
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5.1.1 Introduction of LaTeX
| LaTeX is high-quality typesetting system, intended for production of technical and scientific documentation [4]. LaTeX has a stable specification and uses widely in academic publications for high-quality literature prints. As the file format and typeset-ting system is intended for technical and scientific documentation... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5.1.2 Benefits of LaTeX
| The following are some formatting features that are distinct from Microsoft Word which may be of interest for 3GPP specifications.
- Separation of typesetting configuration & actual literature content
- LaTeX is consists of two aspects. Typesetting configuration and literature content. It is possible to separate the ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5.1.3 Examples of LaTeX drafting
| In this section, some examples of how LaTeX is drafted and rendered is provided. Additionally, comparison with another popular markup language, Markdown, is provided to provide context of LaTeX as a markup language and to show case how LaTeX handles different use cases of 3GPP specification drafting. The example shows ... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.5.1.4 Example implementation of LaTeX based Specification on 3GPP Forge
| As part of the Specification modernation study, three example LaTeX implementation of RAN specification was created in 3GPP Forge. The example LaTeX implementations are:
- TS38.201 V19.0.0 in https://forge.3gpp.org/rep/fs_6gspecs_new/interdigital_latex_38201.
- TS38.202 V19.0.0 in https://forge.3gpp.org/rep/fs_6gspec... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.6 Proposal #6: DOCX with restrictions
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.6.1 Description
| This proposal focuses on what can be done to make DOCX and use of MS Word compliant with the requirements.
DOCX format needs no introduction, and so we will omit the description of the format itself for brevity.
To address requirement 4 "Cross Platform", тthe following restrictions shall be introduced and enforced to... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.6.2 Evaluation against requirements of section 4.3
| Due to similarities and substantial overlap of the "Proposal #6: DOCX with restriction" and "Proposal #7: Multiple formats for single specification with Word as baseline", and considering that these proposals are not mutually exclusive, these proposals are evaluated together. For details see clause 5.7.2.
|
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.7 Proposal #7: Multiple formats for single specification with Word as baseline
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.7.1 Description
| In the table below it is described how the various specification elements of a single specification could be stored, i.e. which file format they could be stored, where the main document of the specification is written with Word.
It should be noted that some specification elements can be captured in different formats d... |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8 Proposal #8: Standalone ASN.1
| |
5c416a273356c09854424ee0fcfb397b | 21.802 | 5.8.1 Description
| ASN.1 is the language used to define signalling in the radio resource control (RRC) protocol. The language supports many built-in datatypes, e.g., bit strings, Booleans, enumerations, integers, and octet strings, and data structures, e.g., choices and sequences. Every IE is named, and every field within an IE is named ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.