hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 1 Scope | The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the MQ Telemetry Transport (MQTT). It will be a reference base for both client-side test campaigns and server-side test campaigns addressing the conformance issues. |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 2 References | |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 3 Definition of terms, symbols and abbreviations | |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: conformance: extent to which an implementation of a standard satisfies the requirements expressed in that standard ETSI ETSI TS 103 597-1 V1.1.2 (2021-01) 6 conformance testing: process to verify to what extent the IUT conforms to the standard Impleme... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 3.2 Symbols | Void. |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: IUT Implementation Under Test MQTT MQ Telemetry Transport SUT System Under Test TDL Test Description Language TDL-TO Test Description Language - Test Objectives TSS Test Suite Structure |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4 Test Suite Structure | |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4.0 Introduction | The following two clauses describe the TSS. In the first one an MQTT server as SUT is considered and in the latter, an MQTT client as SUT is considered. The structure itself is partly derived from the MQTT specification [1] but changed due to overlapping functions that cannot be tested separately. |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4.1 Broker as SUT | 1) All mandatory message data fields a) CONNECT Control Packet i) Fixed Header 1) Header Flags ii) Variable Header 1) Protocol Name 2) Protocol Level 3) Reserved Flags 4) Last Will Testament Flags 5) Credentials Flags ETSI ETSI TS 103 597-1 V1.1.2 (2021-01) 7 iii) Payload 1) Client Identifier 2) Will Topic 3) Credentia... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4.2 Client as SUT | 1) All mandatory message data fields a) CONNECT Control Packet b) CONNACK Control Packet c) PUBLISH Control Packet d) PUBACK Control Packet e) PUBREC Control Packet ETSI ETSI TS 103 597-1 V1.1.2 (2021-01) 9 f) UNSUBACK Control Packet g) PUBREL Control Packet h) PUBCOMP Control Packet i) SUBSCRIBE Control Packet j) UNSU... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4.3 TP naming convention | TPs are numbered, starting at 001, within each main scope. The main scopes are organized according to the TSS. Some TPs may not have a second level scope. Table 1: TP identifier naming convention scheme Identifier: TP_<protocol>_<iut>_<scope>_<2nd_lvl_scope>*_<number>* TP = Test Purpose Fixed to TP <protocol> = Protoco... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 4.4 TP structure | Each TP has been written in TDL-TO and thus in a structured manner which is consistent with all other TPs. The intention of this is to make the TPs more formal. In addition, a more readable format is provided by generating tables out of the TDL-TO format. The defined structure, that has been used, is illustrated in tab... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 5 Test Purposes for MQTT Broker | TP Id TP_MQTT_BROKER_CONNECT_001 Test Objective Verify that the IUT closes the network connection if fixed header flags in CONNECT Control Packet are invalid. Reference [MQTT-2.2.2-1], [MQTT-2.2.2-2], [MQTT-3.1.4-1], [MQTT-3.2.2-6] PICS Selection PICS_BROKER_BASIC Initial Conditions Expected Behaviour ensure that { whe... |
5ea91ad48fb0df91c444f558d011e432 | 103 597-1 | 6 Test Purposes for MQTT Client | TP Id TP_MQTT_CLIENT_CONNECT_001 Test Objective Verify that the IUT is able to send CONNECT Control Packets with valid Header Flags. Reference [MQTT-2.2.2-1] PICS Selection PICS_CLIENT_BASIC Initial Conditions Expected Behaviour ensure that { when { the IUT is triggered to send a CONNECT message } then { the IUT sends ... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 1 Scope | The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the Constrained Application Protocol (CoAP) protocol. It will be a reference base for both client side test campaigns and server side test campaigns addressing the performance issues. |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 2 References | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 3 Definition of terms, symbols and abbreviations | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 3.1 Terms | For the purposes of the present document, the following terms apply: acknowledgement message: message which acknowledges that a specific Confirmable message arrived as defined in IETF RFC 7252 [1] NOTE: By itself, an Acknowledgement message does not indicate success or failure of any request encapsulated in the Confirm... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 3.2 Symbols | Void. |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CoAP Constrained Application Protocol CPU Central Processing Unit DOC Design Objective Capacity GTW Gateway HTTP Hyper Text Transfer Protocol IP Internet Protocol IUT Implementation Under Test KPI Key Performance Indicator LAN Local Area Netwo... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4 Performance metrics | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.0 Introduction | The performance metrics specified herein pertain to the specifics of a CoAP IUT. As such, the objective is to use these metrics in order to determine how well the CoAP component (be it client or server) is performing its functions. As CoAP is a transport protocol, the metrics will be focused on how fast, reliable and e... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.1 Concepts | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.1.1 Concepts introduction | For measuring performance of a given Test System (TS), a comprehensive description of the test environment is required. This includes but it is not limited to: • TS hardware infrastructure: resource specification, type, capacity and distribution. • Test environment type and resources (virtualisation technology, allocat... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.1.2 Measurement Preliminary Considerations | In order for the collected measurement data to be useful, special consideration needs to be given to the TS setup. Given that the performance evaluation is targeting one or several IUTs same TS setup characteristics are required in order for the evaluation results to allow valid comparisons between them. Some of the ch... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2 Measurement Methodology | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.0 Introduction | This clause presents the test methodology for CoAP performance evaluation. From the performance perspective, all measurable metrics related to the protocol should be considered. Although not exhaustive, these metrics can be categorized as follows: Powerfulness metrics as defined in ETSI TR 101 577 [i.2] include 3 sub c... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.1 Metric Post-processing | The collection of metric values from a SUT is performed by multiple agents and/or directly by the IUT. Often a better insight into the IUT performance is gained by post-processing these values in order to get more meaningful results. To this scope, the data samples can be aggregates over time intervals in the experimen... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.2 Message Types | Table 1 contains the set control packet messages specified by the CoAP standard [1]. Table 1: Message Types Control Packet Name Description Client -> Server Server -> Client Payload GET Retrieves a representation for the information that currently corresponds to the resource identified by the request URI. Required PO... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.3 Test parameters | The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in table 2. Table 2 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and ... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.4 Operation Message Flows | The IUT will be evaluated based on the metric values obtain as a result of the service operations using the messages described in clause 4.2.2. The set of messages exchanged triggered by the initial client message are further referred as operations. For the tests, the metrics use operations rather than specific message... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.2.5 Test Campaign Parameters | For test-campaign evaluations, a sequence of control packet exchanges is specified. This allows for defining multiple types of test benchmarks based on client-server interactions. This may address but not be limited to the following: • Duration • Control packet sending order • Number of control packets sent per session... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.3 Powerfulness metrics | The powerfulness category of performance characteristics contains indicators of speed and quantity of service production. The following metrics are derived from ETSI TR 101 577 [i.2]: • Capacity: ability to accept incoming service requests per time unit. For this metric set, the type of messages considered for evaluati... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.4 Reliability metrics | The reliability category of performance characteristics contains indicators of how predictable a system's service production is. The performance category has subcategories for Quality-of-Service, Stability, Availability, Robustness, Recovery, and Correctness. Stability - Stability characteristics are indicators of a sy... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 4.5 Efficiency metrics | The following metrics are derived from ETSI TR 101 577 [i.2]. The performance category efficiency contains different types of indicators of resource usage and resource utilization. These metrics can be recorded additional to the Powerfulness metrics during the specified tests. The scope of these are to determine system... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 5 Configurations | The performance test configurations are derived from the SUT access points and functional test configurations. ETSI ETSI TS 103 596-3 V1.1.1 (2021-05) 17 Figure 6: CoAP Server-Client test configurations Furthermore, there are consideration following possible performance specific load and measurement tools. |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6 Benchmarking | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.1 Generic adjustments | This clause specifies the CoAP protocol performance metrics. As a protocol evaluation rationale, the metrics presented herein are directly addressed to IUTs: systems and associated components implementing the protocol, namely clients and servers. No requirements will be expressed regarding specifics of such IUTs in ter... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.2 Benchmarking Methodology | This clause aims to describe a viable methodology for benchmarking the performance of an IUT. In the case of CoAP, an IUT may consist of one or several Servers or one or several Clients. The approach is inspired from the examples in IETF RFC 2544 [i.1] from the point of view of measurement preconditions, approach and s... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.3 Metric examples | This clause presents a series of benchmark metric examples: • GET delay: the time delay between GET message and server Content response. Value expressed in milliseconds (ms). • POST-delay: the time interval starts when a Post message is sent and ends when the corresponding Created/Changed message has been received back... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.4 Benchmark examples | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.4.0 Introduction | For evaluating the metrics described in clause 4, the benchmark tests can be grouped in 3 main categories. 1) Load Tests: These tests are used for determining or validating the IUT workload range. The workload consists of one or multiple message exchanges between the IUT and the Test System. The aim is to observe the P... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.4.1 KPI Determination | The KPI determination benchmark is an exploratory performance evaluation that aims to determine the operational performance of an IUT. The KPIs are specified as an input. The scope of this evaluation is to establish a reliable indication of how the SUT is expected to perform in production. The KPIs are determined accor... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 6.4.2 KPI Validation | The KPI validation benchmark is performance evaluation that aims to validate whether the IUT performs according to requirement specifications. The KPIs and their thresholds are specified as an input. The scope of this evaluation is to establish a reliable indication of how the SUT is expected to perform in production. ... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 7 Examples of tests | |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 7.0 Introduction | A test should be presentable as a document, with accompanying data files, that provides a full description of an execution of a performance test on a test system. Description of the test case and objective of the test case, e.g. the definition of the targeted metrics should be contained therein. The following sections ... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 7.1 Test Objectives | In this clause, 2 formalized test objective examples are presented. A set of test purposes are presented in Annex A. EXAMPLE 1: Server Post Load Test Determine if the IUT (server) can handle the given POST message load for a determined period of time without exceeding the delay threshold within a given acceptable messa... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 7.2 Test Purpose | In this clause, a formalized test purpose example is provided. A set of test purposes are presented in Annex A. Precondition: • The IUT is running and configured to accept client connections. • Client(s) send PUT messages. • Client(s) start sending POST messages at a specified rate (messages per second) totalling a spe... |
b36f44c04cf0410b4fdd7f3e8dd5c76e | 103 596-3 | 7.3 Test Report | The test report will include the test execution time, test parameters (e.g. number of messages, rate) and measurement/aggregated measurement results (e.g. the average POST/Updated message sequence latency was 3 ms end-to-end). ETSI ETSI TS 103 596-3 V1.1.1 (2021-05) 24 Table 4: Performance load test report for GET exam... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 1 Scope | The present document specifies an Application Programming Interface (API) for the Open Mobile Radio Interface (OMRI) which can be used by application developers to gain access to broadcast radio tuners in consumer electronic devices such as smartphones, tablets and/or other devices, and which allows the execution of pr... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 2 References | |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 3 Definition of terms and abbreviations | |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 3.1 Terms | For the purposes of the present document, the following terms apply: app: small software program providing a dedicated function typically found on a smart device |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding ADTS Audio Data Transport Stream API Application Programming Interface CRID Content Reference IDentifier DAB Digital Audio Broadcasting DL Dynamic Label DLS Dynamic Label Segment EPG Electronic Programme Guide FIC Fas... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4 API Architecture | |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.1 Introduction | In recent years, the class of so called smart devices has shown an impressive growth in market share. Initially designed primarily as mobile phones (cell phones) and for accessing internet services such as e-mail and the World Wide Web, the versatility of these devices has provided developers with the ability to implem... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.2 System overview | Normally mobile devices have the capability to connect to IP based networks either over integrated wifi or mobile communications systems. This connectivity, however, only allows for point-to-point connectivity. Access to broadcast services such as DAB or FM for radio is often not possible. Even if mobile devices are eq... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.3 API overview | |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.3.1 OMRI packages | The OMRI API currently consists of three main packages: org.omri.radio: The radio package acts as the entry point into the API for the developer. The main class in org.omri.radio is the Radio class which is designed as a singleton and provides a simple getInstance method for the app developer to obtain the Radio instan... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.3.2 OMRI Object diagram | Figure 2 shows an example OMRI instance diagram. Beginning with the singleton instance of the Radio class, Radio.getAvailableTuners returns a list of Tuner instances. Querying the TunerStatus reveals that one of the tuners in in TUNER_STATUS_INITIALIZED state and returns an instance of RadioServiceDab. Subscribed to th... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.3.3 Radio state model | Figure 3 depicts the state model of the Radio class. The Radio can have three different states: Figure 3: Radio class state model not initialized: This is the initial state of the Radio class. This means that when the OMRI app is started and a Radio instance is obtained through the getInstance() method the call to getR... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 4.3.4 Tuner state model | Figure 4 depicts the state model of the Tuner object. Figure 4: Tuner object state model not initialized: This is the initial state of the Tuner object. initialized: Calling the initializeTuner() or resumeTuner() methods brings the Tuner object into initialized status. When in the initialized state a service scans or s... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 5 Examples of use of OMRI API | |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 5.1 Developer experience | In order to gain a better understanding of the steps necessary to use the OMRI API for a minimal radio playing app, an example is provided. This example is an extraction of source code fragments from a real OMRI sample app's MainActivity. The full source code of this app is given in annex C. The example is quite basic ... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 5.3 Implementing a TunerListener | The TunerListener Interface is the central element for the app developer to get live data from the different available physical tuners known to the receiver device's OMRI implementation. Most important for the developer is the handling of the different tuner statuses during its life cycle. The app's sample here takes c... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 5.4 Implementing a VisualMetadataListener | When tuned to a service, an app shall provide a proper implementation of a VisualMetadataListener in order to get updates when new SlideShow [i.2] images are received. According to the interface definition for the VisualMetadataListener only one method (public void newVisualMetadata()) needs to be implemented. In the e... |
f3b605c7b2be7b5ec08ec6a94a470f27 | 103 632 | 5.5 Implementing a TextualMetadataListener | When tuned to a service, an app shall provide a proper implementation of a TextualMetadataListener in order to get updates when new textual labels (e.g. from dynamic label [i.1], DLPlus [i.5], RDS RadioText [i.6] or RadioDNS [i.4]) are received. According to the interface definition for the TextualMetadataListener only... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 1 Scope | The present document describes the content and the transport methods used for AML messages with handset derived location information and associated data. It also considers the future evolution of transport methods as PSAPs, networks and terminals become increasingly IP based. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 2 References | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 3 Definition of terms, symbols and abbreviations | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 3.1 Terms | Void. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 3.2 Symbols | Void. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3G (mobile) Partnership Project AGNSS Assisted Global Navigation Satellite System AML Advanced Mobile Location ASCII American Standard Code for Information Interchange DCS Data Coding Scheme GMLC Gateway Mobile Location Centre GNSS Global... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 4 Overview | AML functionality is triggered by an emergency communication (which is progressed normally by the handset and the network), and is designed to supplement the basic network location provided wherever possible, i.e. with some acknowledgement of limitations in GNSS or Wi-FiTM availability for the handset and the time requ... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 5 Handset Functionality | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 5.1 Positioning methods and time needed to precisely locate | GNSS, or Assisted GNSS, normally offers the best location information but is slower than other methods. At the other end of the spectrum cell based location is quick but typically returns a larger location area. The general rule is that PSAPs need the best data as long as it does not take too long to determine, so a 's... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 5.3 Availability of MSISDN | PSAPs need to be able to match the voice call with the AML data, and to do so they use the MSISDN (Mobile Station International Subscriber Directory Number). The MSISDN is included within an SMS message so this is straightforward if SMS is used for AML transport. In some instances, the MSISDN can be accessed by the han... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 5.4 Data connectivity | The mobile handset requires data connectivity to allow communication with servers operated by the providers of the phone's operating system that: a) provide assistance information to allow quick establishment of a GNSS position (AGNSS); and b) provide access to primarily crowd sourced databases for location information... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 5.5 Battery life | Before invoking the AML functionality, the handset should check there is sufficient battery life so that the caller can still make a short 5 minute voice call. The priority in the emergency situation is to allow voice connection to the PSAP. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6 Location data and data transport | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.1 General | In order for a PSAP to be able to process messages of a later version than the PSAP currently supports, the PSAP shall ignore all attributes that it cannot process. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.2 Location data provision by the handset | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.2.1 Data provided | The following attributes are those that are normative for implementation using transport methods described in clauses 6.3 and 6.4: • AML is required to communicate a location in the form of a circle. The location and size of the circle determined by the handset shall be communicated using the attributes of a WGS 84 lat... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3 SMS transport | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.1 SMS transport overview | When SMS transport is selected (see clause 8), the standard mobile network SMS service shall be used to send the AML message from the phone to the SMSC (SMS Centre) within each mobile network (using normal 3GPP network standards). The Short Message Peer-to-Peer (SMPP) open industry standard protocol for transfer of sho... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.2 SMS Formats | It is important to note that 2 types of SMS are used to provide the AML location information. Which type of SMS is used may depend on the options open to handset manufacturers or Operating System (OS) providers to suppress a record of a sent AML location message on the handset: a) Regular SMSs are used by handset manuf... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.3 Security of SMS transport | SMS access to the mobile network is authenticated and is also encrypted over the air between the handset and the base station. In terms of interception on the air interface there is a very low risk for individual users as AML SMS is only triggered when an emergency communication is made, which is a random event for ind... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.4 Roaming | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.4.1 International Roaming | For international roaming, there are challenges since an SMS is returned to the home country's SMS Centre for routing and the AML SMS is not received by the most appropriate PSAP, e.g. the PSAP receiving the voice call. The approach to support AML for foreign users is to change SMS home routing paradigm and to force AM... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.3.4.2 Limitation - Limited Service State/National Roaming | In case the citizen initiates an emergency communication but the handset has no coverage from the home MNO, the call is handled by another mobile network operator with signal coverage in that area, even if the handset is not be able to register on this network. In this limited service state it is currently not possible... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4 HTTPS | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.1 Overview of using HTTPS | When HTTPS transport is selected (see clause 8.1), HTTPS POST messages shall be used to transfer the emergency location information and associated data described in annex B. The HTTPS message includes additional fields that cannot be sent via SMS due to the restricted length of the SMS. Visited Network PSAP SMSC Emerge... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.