The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling interoperable implementations of the architecture and provides extension points to enable new communication mechanisms as they evolve.
The frequency bands used for broadcasting below 30 MHz are: •Low Frequency (LF) band: from 148,5 kHz to 283,5 kHz, in ITU Region 1 [1] only; •Medium Frequency (MF) band: from 526,5 kHz to 1 606,5 kHz, in ITU Regions 1 [1] and 3 [1] and from 525 kHz to 1 705 kHz in ITU Region 2 [1]; •High Frequency (HF) band: a set of individual broadcasting bands in the frequency range 2,3 MHz to 27 MHz, generally available on a Worldwide basis. These bands offer unique propagation capabilities that permit the achievement of: •large coverage areas, whose size and location may be dependent upon the time of day, season of the year or period in the (approximately) 11 year sunspot cycle; •portable and mobile reception with relatively little impairment caused by the environment surrounding the receiver. There is thus a desire to continue broadcasting in these bands, perhaps especially in the case of international broadcasting where the HF bands offer the only reception possibilities which do not also involve the use of local repeater stations.
The present document is a choice of Test Purposes Description Language (TPDL), with the intention to capture all of the information required by the Test Template and should be parseable using software.
The Testing Framework (document format) specifies a testing framework defining a methodology for the development of the test strategies, test systems and resulting test specifications. The present document identifies the implementation under test (scope of the testing), the format for the test specification, the test architecture, the points of control and observation, the naming conventions (e.g. for test case ID and test case grouping ID), etc. It also provides the Implementation Conformance Statement which is basically a checklist for a client-owner so they know what parts of the specification will be tested and if any is optional. The ICS will be published as a separate GS.
ISO/IEC TS 33052:2016 defines a process reference model (PRM) for the domain of information security management. The model architecture specifies a process architecture for the domain and comprises a set of processes, with each described in terms of process purpose and outcomes.
This recommendation provides an overview of the Internet of things (IoT). It clarifies the concept and scope of the IoT, identifies the fundamental characteristics and high-level requirements of the IoT and describes the IoT reference model. The ecosystem and business models are also provided in an informative appendix.
ISO/IEC 30163:2021 specifies the system requirements of an Internet of Things (IoT)/Sensor Network (SN) technology-based platform for chattel asset monitoring supporting financial services, including: - System infrastructure that describes functional components; - System and functional requirements during the entire chattel asset management process, including chattel assets in transition, in/out of warehouse, storage, mortgage, etc.; - Performance requirements and performance specifications of each functional component; - Interface definition of the integrated platform system. This document is applicable to the design and development of IoT/SN system for chattel asset monitoring supporting financial services.
Recommendation ITU-T X.1364 analyses potential deployment schemes and typical application scenarios for narrowband Internet of things (NB-IoT). It specifies security threats and requirements specific to the NB-IoT deployments and establishes a security framework for the operator to safeguard new NB-IoT technology applications. Current developments in telecommunication technology in the mobile communication domain, are leading to changes in communication patterns from person-to-person to person-to-thing and thing-to-thing, making inevitable the evolution to the Internet of things. Compared to short distance communication technologies such as Bluetooth, ZigBee and others, cellular mobile networks characterized by wide coverage, mobility and extensive connections that bring richer application scenarios will become the main interconnection technology of IoT. NB-IoT is based on cellular mobile network technology, using a bandwidth of approximately only 180 KHz. It may be deployed on global system for mobile communication (GSM) networks, universal mobile telecommunications system (UMTS) networks or long-term evolution (LTE) networks directly to reduce costs and achieve a smooth upgrade. Based on its low power dissipation, wide coverage, low cost and high capacity, NB-IoT is expected to be massively adopted by operators with wide application in multiple vertical industries. As a new technology, NB-IoT has its own characteristics that may bring new security issues. In order to ensure security of NB-IoT deployments and applications, security threats and relevant security requirements specific to NB-IoT need to be analysed and an overall security framework for NB-IoT needs to be established.
The present document would undertake compilation and review of activities taking place in the area of Smart City. It will analyse the relevance of Smart City applications, and possible underlying network architecture. The present document will describe use case descriptions for Smart City applications in context of but not limited to IoT communications.
The scope of the present document is to provide an overview of the IoT standards landscape: requirements, architecture, protocols, tests, etc. to provide the roadmaps of the IoT standards, when they are available
This European Standard gives general guidelines and recommendations to ensure interworking between HBES devices made by different manufacturers. It also contains design guidelines for the design of Functional Blocks and new datapoint types, the building blocks of HBES interworking. In this way, the standard can be used as a basis to design application specifications relative to an Application Domain. If designed and supported by a large group of manufacturers, such application specifications will ensure to end customers a high degree of interoperability between products based on the HBES Communication System of different manufacturers. This European Standard is used as a product family standard. It is not intended to be used as a stand alone standard.
This international standard establishes general principles for network- and device-management shared by and independent of the installation mode. The goal is to standardize the interaction, between a management client and a management server, that shall lead to the successful configuration of the devices. In this way, these management procedures thus specify the highest level communication requirements between a management client and a management server. These requirements specify: a) the sequence of messages that shall be exchanged between a management client and a management server, and b) the contents and interpretation of the transported data, and c) the action to take based on these data (setting internal resources, state machines, physical actions, …), and d) the error and exception handling. The management procedures base on the application layer services. Some management procedures solely base on the use of one or a sequence of dedicated application layer services to achieve the required goal. For these, the documents EN 50090-4-1 and EN 50090-4-2 provide sufficient information for the underlying mechanisms. Other management procedures additionally use the application layer services to access internal data in the management server to achieve the required goal. These data are laid down as objects as specified in EN 50090 3 2.
