hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11 Performance with DTMF tones
| |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11.1 Introduction
| In the fixed telephone system, DTMF (Dual Tone Multi Frequency) signals are transmitted in the speech channel for signalling. This has led to the use of DTMF tones for applications such as the control of answering machines and mail/messaging boxes. In the GSM system, the handling of these signalling tones is dependant ... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11.2 Test set-up
| 16 DTMF signals are defined representing the 10 numeric keys, the characters "A", "B", "C", "D", "*" and "#". Each digit consists of two sine signals of distinctive frequencies, one chosen out of 4 values from the low frequency group (or row frequency), and one out of the 4 values from the high frequency group (column ... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11.3 Results
| The results of the test with a standard DTMF detector are shown in table 7. Even at ideal conditions with nominal DTMF signal frequencies, no additional signals in the speech band, and error free transmission, the recognition is poor after processing. Only with a relatively high level of -12 dB and a tone length of 80 ... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11.4 Conclusions
| With the standard detector the recognition rate averaged over all experiments was 74 %. The tuning of the detector for the half rate channel characteristics could improve the detection rate to 92 %. As all experiments still had rather ideal conditions, in real application an even lower rate for detection has to be assu... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 11.5 Result tables of experiments with standard and modified DTMF detectors
| The tables below list the numbers of detected tones from 10 input signals at each tested condition. For twist conditions, the pair of level figures indicate the level of row frequencies and column frequencies respectively.
Table 7: Summary of DTMF tests with standard DTMF detector
Condition\Tone
1
2
3
A
4
5
6
... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 12 Performance with signalling tones
| The capability of the codec to transmit network information tones was assessed with 5 French signalling tones following the IUT-T recommendation: "Warn" tone, "Busy" tone, "Ring" tone, "Inf" tone and "Pay" tone (tones of length 200 ms to 1s and silences between tones of length 30 ms to 4 s).
All signalling tones are r... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 13 Delay
| [tbd]
|
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 14 Frequency response
| The frequency response of the GSM half rate codec, has been evaluated by computing the logarithmic gain.
The codec has been tested in error free condition only, without DTX associated, by independently processing 198 sine waves files spaced by 20 Hz and spanning the range between 50 to 3 990 Hz. Each file had a durati... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 15 Half Rate codec complexity
| The complexity of the half rate codec is characterized by the 3 following items:
- the number of cycles;
- the data memory size;
- the program memory size.
The values of these different figures depend on a specific DSP implementation. Nevertheless, the results obtained by the C description analysis can be used as r... |
fc902c14a58d85cbc46880929a1ebce4 | 46.008 | 16.3 Conclusion
| A subjective test methodology for the quality assessment of ETSI's half rate algorithm has been implemented, based on listening opinion tests.
The test methodology reflected international telephony assessment methods that are described extensively in the ITU-T Series P Recommendations, and that have shown to be suitab... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 1 Scope | The present document studies access control for management services produced by 3GPP management system.
The document investigates use cases related to access control, proposed requirements on 3GPP management system and possible solutions to support access control.
The document also provides recommendation for the norma... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 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.
- Fo... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 3 Definitions of terms, symbols and abbreviations | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 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].
Internal MnS consumer : It is a digital tool owned by the operator who provides the 3GPP management ... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 3.2 Symbols | Void. |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 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].
ANS Authentication Service
ARS Authorization Service
ANS Audit Service |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4 Concepts and overview | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4.1 Overview | Service based architecture of 3GPP management system enables a management service (MnS) consumer to access and utilize capabilities of a MnS producer to provision or monitor logical networks, services or resources allocated to the consumer. 3GPP management system is built on multiple management domains (see [3]). There... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4.2 Concept | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4.2.1 Access control | Access control in 3GPP management system represents the set of features and procedures that allow controlling how management service consumer and management service producer communicate and interact with each other, hence protect the 3GPP management system and managed services as well as resources from unauthorized acc... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4.2.2 Authentication | Authentication in 3GPP management system represents the set of security features and procedures that allow proving a management service consumer or producer is what it claims to be, based on its identity and one or more of the three factors: something a consumer/producer knows (e.g. password), something a consumer/prod... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 4.2.3 Authorization | Authorization in 3GPP management system represents the set of features and procedures that allow ensuring an authenticated management service consumer has the corresponding access rights to services/resources related to location, time and reasons. |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5 Use cases for access control for management service | 5.1 use case – MnS is accessed by a digital portal of the operator |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.1.1 Description | On behalf of an internal or external user of a 3GPP management system, a digital portal/store front of an operator could access MnSs produced by the 3GPP management system of the operator to provision and monitor the network of the operator. There are several example scenarios.
Scenario 1: An administrator of the opera... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.1.2 Issue and gaps | Potential security issues:
Without proper access control, the administrator of the operator or its customer could mis-operate on the network/network slice deliberately or accidently. e.g. an external customer of an operator could delete a network of the operator, which is serving multiple customers, that could cause ou... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.2 Use case – MnS is accessed by an external consumer of the 3GPP management system | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.2.1 Description | A vertical customer may utilize service provided by an operator to build their own E2E service, therefore a management tool of the vertical customer, which is in the data centre of the vertical, could access 3GPP management system of the operator to provision and monitor services offered by the operator. E.g. An applic... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.2.2 Issue and gaps | Potential security issues:
Without proper access control on the external tools/applications which access the MnS of 3GPP system, attacker could utilize fraudulent tool to perform attacks, e.g. man-in-the-middle, DDoS, etc., that could cause availability and confidentiality compromising. Further, the malicious entity ca... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.3 Use case – MnS is accessed by a consumer in the same domain of the 3GPP management system | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.3.1 Description | A digital tool, acting as a MnS consumer, could access MnSs produced by a MnS producer in the same management domain of an operator to perform different tasks. E.g. Decision entity in network slice management domain may access analytics entity in the same domain to get analytics report for better decision.
NOTE: The Mn... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.3.2 Issue and gaps | Potential security issues:
Without proper access control between tools in the same management domain, the management function with low sensitive level could access MnS labelled as sensitive that compromised confidentiality of the system, e.g. discovery management function accesses sensitive data exposed by data MnS wou... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.4 Use case – MnS is accessed by a consumer in the different domain of the 3GPP management system | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.4.1 Description | A digital tool in data centre of an operator, acting as a MnS consumer, could access MnSs produced by a MnS producer in another management domain of a same or different operator to provision and monitor network or resources. E.g. NSMF could create/delete/update RAN and/or network slice subnet through MnSs provided in R... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.4.2 Issue and gaps | Potential security issues:
Without proper access control between tools of 3GPP system, attacker could utilize fraudulent tool to perform attacks, e.g. man-in-the-middle, DDoS, etc., that could cause availability and confidentiality compromising. Further, the malicious entity cannot be identified without tracking and au... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.5 Use case – trust relationship between MnS producer and consumer | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.5.1 Description | Mutual Trust should be established between MnS consumer and producer inside a management domain or inter different management domains before they interact with each other, to ensure confidentially, integrity, availability and regulation compliance of the management systems.
To build trust relationship between different... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.5.2 Issue and gaps | Trust relationship and trust model for 3GPP management system have not been specified or studies in 3GPP or other SDOs. Applying same trust model and security control for different trust relationship could incur either undue control (e.g. apply strict access control everywhere that caused complexity and high cost) or l... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.6.1 Description | As described in use cases 5.3 and 5.4, There are different MnS consumers of 3GPP management system. According to operator's security policies, regulation and other conditions, the access permission assigned to different consumer could be different. E.g. based on operator security policies, modification of a network sli... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.6.2 Issue and gaps | Potential security issues:
Without granular access control, MnSs of 3GPP management system could be exposed to unauthorized consumers after the consumers being authenticated. e.g. an authenticated management function in CN domain could delete a RAN network slice subnet that may cause unavailability of the system, or an... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.7.1 Description | Generally, There are always huge number of heterogeneous management systems in big operator's data centre. Administrators of the operator access the systems for daily management and operation, while management functions of the systems could interact with each other for network and resource management. Access control, i... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 5.7.2 Issue and gaps | Requirements and solution of access control for 5G network management system, as well as integrating access control function of 5G network management system to centralized AAA platform of operator have not been specified in existing 3GPP and other SDOs. Currently, some management systems have its own vendor specific AA... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6 Potential requirements for access control for management service | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.1 Potential requirements related to identification | - REQ-MNSAC-101 The 3GPP management system may have the capability to identify a MnS producer.
- REQ-MNSAC-102 The 3GPP management system may have the capability to identify an internal MnS consumer in same or different management domain.
- REQ-MNSAC-103 The 3GPP management system may have the capability to identify th... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.2 Potential requirements related to authentication | - REQ-MNSAC-201 The 3GPP management system may have the capability to support mutual authentication between MnS producer and internal MnS consumer in same or different management domain.
- REQ-MNSAC-202 The 3GPP management system may have the capability to support mutual authentication between MnS producer and external... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.3 Potential requirements related to authorization | - REQ-MNSAC-301 The 3GPP management system may have the capability to support authorization of an internal user of the 3GPP management system of the operator based on operator's policies.
- REQ-MNSAC-302 The 3GPP management system may have the capability to support authorization of an external user of the 3GPP manageme... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.4 Potential requirements related to audit | - REQ-MNSAC-401 The 3GPP management system may have the capability to support tracking activities of an internal MnS consumer.
- REQ-MNSAC-402 The 3GPP management system may have the capability to support tracking activities of an internal/external user of the 3GPP management system.
- REQ-MNSAC-403 The 3GPP management... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.5 Potential requirements related to trust relationship of MnS producer and consumer | - REQ-MNSAC-501 The 3GPP management system may have the capability to support evaluating trust relationship (or trust level) between MnS producer and consumer.
- REQ-MNSAC-502 The 3GPP management system may have the capability to support creating trust model for MnS producer and consumer based on trust relationship bet... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 6.6 Potential requirements related to centralized AAA system integration | - REQ-MNSAC-601 The 5G network management system may have the capability to support integration with centralized AAA system automatically based on standardize interface.
- REQ-MNSAC-602 The 5G network management system may have the capability to support synchronization of security policies between 5G network management... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7 Possible solutions for access control for management service | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1 Possible solution to support access control on management service | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1.1 Enhance Service Based Management Architecture (SBMA) to support authentication capability (update clause 4 of TS 28.533 [3]) | Authentication service producer provides identity management capabilities. Identity management of MnS consumers and producers includes creating, reading, updating and deleting identities.
Authentication service producer provides credential management capabilities. Credential management of MnS consumers includes creatin... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1.2 Enhance Service Based Management Architecture (SBMA) to support authorization administrative/decision capabilities (update clause 4 of TS 28.533 [3]) | Authorization service producer provides capabilities to manage permission on MnSs for a MnS consumer or a group of MnS consumers, including create, read, update and delete managed objects.
Authorization service producer provides capabilities to grant permissions to a MnS consumer. Authorization service producer sends a... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1.3 Enhance Service Based Management Architecture (SBMA) to support audit capabilities (update clause 4 of TS 28.533 [3]) | Audit service producer provides capabilities to collect security logs from authentication service producer, authorization service producer and MnS producer. Similar to fault supervision management service, audit service producer could retrieve or receive security log from other components.
Audit service producer provid... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1.4 Enhance Request-response communication paradigm to support authentication and authorization (update clause 5 of TS 28.533[3]) | Figure 7.1.4-1: Request-response communication paradigm with access control
Precondition:
1. The MnS consumer and producer are configured in authentication and authorization service producer. The MnS consumer is always assigned for specific role in specific group.
2. The permissions for specific role or group are confi... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 7.1.5 Enhance NRM and operations to support authentication, authorization and audit capability | Note: What is the exact change in stage 2 and stage 3 will be decided in normative phase. |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 8 Conclusions and recommendations | |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 8.1 Conclusions | The following issues are identified in the present document:
- The service based management architecture specified in TS 28.533 [3] should be updated to support authentication, authorization and audit capabilities.
- The Network Resource Model defined in TS 28.622 [4] and TS 28.623 [5] should be updated to support auth... |
3d01b41fb9f4314a19309caa6d5502b6 | 28.817 | 8.2 Recommendations | The improvements to the Network Resource Model, Generic Management Service and Service Based Management Architecture (as described in clause 7) are not currently in the scope of any existing normative work. It is proposed to enhance the specification to support access control in future normative project.
Annex A:
Chan... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 1 Scope | The present document captures the findings of the study item "Study on NR positioning enhancements" [2]. The purpose of this technical report is to document the requirements, additional scenarios, evaluations and technical proposals treated during the study and provide a way forward toward enhancements to NR positionin... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 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.
- Fo... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 3 Definitions of terms, symbols and abbreviations | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 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].
Positioning Integrity: A measure of the trust in the accuracy of the position-related data provided ... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 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
AL Alert Limit
DL-AoD Downlink Angle-of-Departure
DL-P... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 4 General description of NR positioning enhancements | 3GPP NR radio-technology is uniquely positioned to provide added value in terms of enhanced location capabilities. The operation in low and high frequency bands (i.e. below and above 6GHz) and utilization of massive antenna arrays provides additional degrees of freedom to substantially improve the positioning accuracy.... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5 Target requirements for NR positioning enhancements in Rel-17 | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.1 Target requirements | In Rel-17 target positioning requirements for commercial use cases are defined as follows:
- Horizontal position accuracy (< 1 m) for 90% of UEs
- Vertical position accuracy (< 3 m) for 90% of UEs
- End-to-end latency for position estimation of UE (< 100 ms)
- Physical layer latency for position estimation of UE (< 10 ... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2 Performance evaluation metrics | For evaluating performance of NR positioning technologies, the following metrics apply. The following percentiles of positioning error are analyzed: 50%, 67%, 80%, 90%. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.1 Horizontal accuracy | Horizontal accuracy is the difference between the calculated horizontal position and the actual horizontal position of a UE. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.2 Vertical accuracy | Vertical accuracy is the difference between the calculated vertical position and the actual vertical position of a UE. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3 Other metrics | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3.1 Latency | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3.1.1 Physical layer Latency | Latency includes higher layer and physical layer latency. Physical layer latency for DL only, UL only, DL+UL positioning solutions for UE-based and UE-assisted approaches are separately studied
The physical layer latency start- and end-time are defined for each positioning method in table 5.2.3.1-1
Table 5.2.3.1-1: Def... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3.1.2 Higher layer Latency | Higher layer latencies include processing delays of the various involved nodes (UE, gNB, AMF, LMF, etc) and signalling delays between nodes.
The latency assumptions for the various components (UE, gNB, AMF and LMF) used in higher layer latency analysis are defined in table 5.2.3.1.2-1.
Table 5.2.3.1.2-1: Latency Compon... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3.2 Network efficiency | PRS/SRS resource utilization is the metric used to evaluate network efficiency. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 5.2.3.3 Device efficiency | The UE power consumption models developed in TR38.840 can be considered as the starting point for defining the UE power consumption model for the evaluation for NR positioning. For evaluations, it is up to each source to detail their methodology (including the power model) for evaluation. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 6 Additional scenarios and channel models for NR positioning enhancements | The scenario parameters common to all the scenarios in the study are detailed in table 6-1. Additionally, blockage model is not considered. For evaluations including UE mobility, the spatial consistency procedure defined in TR 38.901 is taken into consideration.
The evaluation methodology does not define any baseline r... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 6.1 IIoT use cases | For evaluating baseline performance, the following scenarios (with various options/configurations) are defined for RAT-dependent positioning techniques for the NR positioning enhancements study
- Scenario 1. InF-SH for FR1 and FR2
- Scenario 2. InF-DH for FR1 and FR2
In the evaluation of all scenarios, the absolute-tim... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 6.2 General commercial use cases | For general commercial use cases, Rel-16 scenarios and channel models in TR 38.855 are reused. For the absolute time of arrival modelling in IOO, UMa, Umi, sources may provide the details of their model, if any. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 7 Studied NR positioning enhancements | The following enhancements have been considered during this study:
- Partial staggering and non-staggering RE mapping of SRS for positioning with different combinations of comb-factors and symbol lengths, including the methods/signalling for addressing potential time-domain aliasing due to the partial/non-staggering RE... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8 Performance evaluations for Rel-17 targets | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1 Performance analysis of Rel-16 positioning solutions | This clause presents the observations made by sources regarding Rel-16 positioning solutions. Detailed results can be found in annex C.1. |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1 Positioning accuracy analysis | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.1 Observations from source [4] | Table 8.1.1.1-1 captures observations based on NR positioning evaluations results for horizontal location error for baseline scenarios.
Table 8.1.1.1-2 captures observations based on NR positioning evaluations results for horizontal location error for modified DH and 3D positioning.
Table 8.1.1.1-3 captures observation... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.2 Observations from source [7] | Table 8.1.1.2-1: Rel.16 NR positioning – horizontal accuracy performance summary [7]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
Case 1
0.603
Case 2
0.568
Case 3
0.704
Case 4
0.943
Case 5
1.479
Case 6
0.092
Case 7
0.090
Case 8
0.300
Case 9
0.615
Case 10
1.224
Case 11
12.433
Case 12
12.345
Case13
12.386
... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.3 Observations from source [8] | Table 8.1.1.3-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.3-1: Rel.16 NR positioning – horizontal accuracy performance summary [8]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
IIoT horizontal accuracy requirements of [0.2]m @[90]%are met ... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.4 Observations from source [13] | Table 8.1.1.4-1: Rel.16 NR positioning – horizontal accuracy performance summary [13]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
Case 1, [InF-SH, DL-TDOA, FR1]
4.35
Case 2, [InF-DH, DL-TDOA, FR1]
7.16
Case 3, [IOO, DL-TDOA, FR1]
4.31
Case 4, [IOO, DL-TDOA, FR1]
6.50
Case 5, [UMi, DL-TDOA, FR1]
23.81
Ca... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.5 Observations from source [5] | Table 8.1.1.5-1.1 to Table 8.1.1.5-1.3 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.5-1.1: Rel.16 NR positioning – horizontal accuracy performance summary for baseline with perfect synchronization [5]
Simulation case
(Horizontal Error)
Accuracy achieved @[... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.6 Observations from source [12] | Table 8.1.1.6-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.6-1: Rel.16 NR positioning – horizontal accuracy performance summary [12]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
IIoT horizontal accuracy requirements of [0.2]m @[90]%are met... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.7 Observations from source [10] | Table 8.1.1.7-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.7-1: Rel.16 NR positioning – horizontal accuracy performance summary [10]
Simulation case (Horizontal Error)
Accuracy achieved @[90]%
Case 1, InF-SH, FR1, DL-TDOA
0.85
Case 2, InF-DH, FR1, DL-TDO... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.8 Observations from source [14] | Table 8.1.1.8-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.8-1: Rel.16 NR positioning – horizontal accuracy performance summary [14]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
[Case 1], [InF-SH], [FR2], [400 MHz], [Comb-6], [6dB PB]
0.24... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.9 Observations from source [20] | Table 8.1.1.9-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.9-1: Rel.16 NR positioning – horizontal accuracy performance summary [20]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
[20], source1, UMa, FR1, DL-TDOA (50% UEs indoor)
11.97m (1 o... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.10 Observations from source [17] | Table 8.1.1.10-1 captures observations based on NR positioning evaluations results for horizontal location error.
Table 8.1.1.10-1: Rel.16 NR positioning – horizontal accuracy performance summary [17]
90%
Case 1, InF FR1 DH ISD20, 100MHz, Link Quality, DL TDOA
Convex UEs
46.647m
(Optional) All UEs
46.649m
Case 1, InF F... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.1.11 Observations from source [18] | Table 8.1.1.11-1: Rel.16 NR positioning – horizontal accuracy performance summary from [18]
Simulation case
(Horizontal Error)
Accuracy achieved @[90]%
Case 1- config ID 445
(FR1-InF DH)
≥10
Case 3- config ID 1112
(FR1-UMi)
3.24
Case 2- config ID 1011
(FR1-UMi with ATOA)
≥10 |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.2 Physical layer latency analysis for Rel-16 | |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.2.1 Observations from source [4] | Summary of latency performance analysis is provided in Table 8.1.2.1-1.
Table 8.1.2.1-1: NR Rel.16 positioning – latency performance summary [4]
Description
Evaluation Case
L1 Latency, ms
Commercial requirements [100]ms are met -Yes/No
- If no, provide performance gaps
IIoT requirements of [10ms] are met - Yes/No.
If n... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.2.2 Observations from source [7] | Summary of latency performance analysis is provided in Table 8.1.2.2-1.
Table 8.1.2.2-1: NR Rel.16 positioning – latency performance summary [7]
Description
Evaluation Case
L1 Latency, ms
Case PHY-L1, UE-A, DL-TDOA, FR1, FDD
106.23
Case PHY-L1, UE-A, DL-TDOA, FR2, FDD
667.87
Case PHY-L2, UE-B, DL-TDOA, FR1, FDD
106.30
... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.2.3 Observations from source [8] | Summary of latency performance analysis is provided in Table 8.1.2.3-1.
Table 8.1.2.3-1: NR Rel.16 positioning - latency performance summary [8]
Description
Evaluation Case
L1 Latency, ms
Commercial requirements [100]ms are met -Yes/No
- If No, provide performance gaps
IIoT requirements of [10ms] are met - Yes/No.
If N... |
9500dacfd2de439e4aa20a2d6e994f8f | 38.857 | 8.1.2.4 Observations from source [13] | Table 8.1.2.4-1: NR Rel.16 positioning - latency performance summary [13]
Description
Evaluation Case
L1 Latency, ms
Case 1, DL-TDOA/DL-AoD, FR1
[44.35 – 10500]
Case 2, DL-TDOA/DL-AoD, FR2
[35.08 – 2118.93]
Case 3, UL-TDOA/UL-AoA, FR1
[2.78 – 81928.5] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.