hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 3.2 Symbols | Void. |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: #CS Number of Crypto Sessions 3GPP 3rd Generation Partnership Project 5G 5th Generation AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard AES-GCM AES using GCM CS Crypto Sessions DoS Denial of Service ECCSI El... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 4 Overview | |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 4.1 Overview of Group Connections | The present document pre-supposes adoption of a Vendor Product which is based on MIKEY-SAKKE [12] and makes use of ETSI TS 103 816-2 [21]. Group voice communications based on MIKEY-SAKKE can be established using a group-keyed approach as described in ETSI TS 133 180 [23] However, that standard is for cases such as Push... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5 Criterion | |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5.1 Initialization | All the initialization requirements that shall be used for one-to-one communications as defined in ETSI TS 103 816-2 [21] shall also be used for the present document. This includes provisioning of all clients by a suitable Key Management Service (KMS) , and that clients are registered with a SIP server, both being conf... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5.2 Profiles | Use of SIP, Session Description Protocol (SDP) and SRTP shall follow the profiles described in ETSI TS 103 816-2 [21]. Use of SIP compared to that specification shall be extended by the use in the present document of SIP SUBSCRIBE and NOTIFY messages defined in IETF RFC 6665 [13]. The SIP INVITE message described in ET... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5.3 Initiating a Group Call | A client that initiates a group call, the group leader, shall do so as a sequence of separate one-to-one connections as described in ETSI TS 103 816-2 [21], modified as described below. Each connection proceeds as shown in Figure 3 of the present document (which is the same as Figure 2 of ETSI TS 103 816-2 [21]). ETSI ... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5.4 Modification of One-to-One Messages | Reporting that a required one-to-one connection is part of a group call shall be in the SIP INVITE message that initiates the connection, and this is done in the MIKEY-SAKKE I_MESSAGE that is included. That message shall include an additional IDentity with Role Indicator (IDR) payload that reports the group identity as... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 5.5 Group Membership Notification | The SIP SUBSCRIBE and NOTIFY messages required by the present document are for the SIP event type defined in clause A.4. The message formats shall be as defined in clause A.7. All group members, other than the group leader, shall send a SIP SUBSCRIBE message to the group leader after responding, with a SIP OK message, ... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 1 Scope | The present document is intended to specify the interface used for encrypted one-to-one text messages. It is intended for use in connecting products based on Multimedia Internet Keying Sakai-Kasahara Key Encryption (MIKEY-SAKKE) domains and to validate products. |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 2 References | |
9f104dd5892e79711302a15ac93b5e8d | 103 816-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... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-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... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 3 Definition of terms, symbols and abbreviations | |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 3.1 Terms | Void. |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 3.2 Symbols | Void. |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard AES-GCM AES using GCM ECCSI Elliptic Curve-based Certificateless Signatures for IBE NOTE: See IETF RFC 6507 [7]). GCM Galois Counter Mode IBE Identity Based En... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4 Background | |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.1 Messaging | The messaging standard that is assumed by the present document is eXtensible Messaging and Presence Protocol (XMPP) IETF RFC 6120 [5]. Using XMPP, text and other messages are usually sent from the source to the destination via one or more servers. While the message can be encrypted to and from the server, for example u... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.2 Identity-Based Encryption and MIKEY-SAKKE | The present document defines a messaging approach that can be used in such circumstances, using Identity-Based Encryption (IBE). The identity-based cryptography used, and the means by which its per-session public information is transferred, uses MIKEY-SAKKE [9]. Some cryptographic material is created by and distributed... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.3 One-to-One Messages | Messaging between endpoints can follow a number of patterns. The simplest of these, and the one defined by the present document, is a one-off message: endpoint A sends a message to endpoint B, and, apart from acknowledgement of the message, that is all. Any subsequent messages, whether sent immediately or after some de... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.4 Relationship to Voice Standard | A similar problem to that outlined in the previous clause has been addressed for one-to-one voice communication in ETSI TS 103 816-2 [12], which is based on MIKEY-SAKKE [9]. That is an IBE approach that offers additional advantages to those of auditability. Specifically, assuming two appropriately provisioned endpoints... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.5 XMPP Message Protocol | Most of IETF RFC 6120 [5] is concerned with the protocol aspects of XMPP, how it can use an eXtensible Markup Language (XML) stream to carry the required data, in the form of XML stanzas, from source to destination. That protocol is used unchanged by the present document, although since the present document only carrie... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.6 XMPP Message Structure | XMPP carries information in the form of stanzas. Three kinds of stanza are defined in clause 8 of IETF RFC 6120 [5], represented by three kinds of XML element: <message/>, <presence/> and </iq>. A message that is encrypted by the present document will always include the first of these (the message stanza) and may inclu... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.7 Message Content Encryption | The contents of a message are replaced when using the present document by an encryption of that message that only the recipient of that message (or its KMS) can decrypt, using the information in the included MIKEY-SAKKE message and the recipient's provisioned private key and certificates. The encryption is of a concate... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.8 Attachments | The present document allows a message to include attachments. An attachment is considered to be equivalent to a file. In order to keep message sizes limited, as required by XEP-0134 [13], and because file sizes are potentially unlimited, the approach used by the present document (as well as by other XMPP extensions) is... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.9 Presence and IQ | Presence information forms the second stanza of an XMPP message. The purpose of presence information is described in clause 1.3 of IETF RFC 6121 [6] as: The purpose of using such an application is to exchange relatively brief text messages with particular contacts in close to real time -- often relatively large numbers... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.10 Message Acknowledgement | A message may be acknowledged using the message delivery receipt mechanism defined in clause 5.9. The message receipt is encrypted using the same authenticated encryption, primarily to ensure its authentication in a whitespace safe manner. The encryption key used is the same as for the message, and thus the message rec... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 4.11 Other XMPP Specifications | For the present document a compliant implementation shall implement all relevant parts of the XMPP Standards Foundation (XSF) MPP Extension Protocol (XEP) [14] defining message receipts. The present document borrows and extends concepts and elements from the XEP-0234 [15] and XEP-0384 [16], but does not require the imp... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5 Definition | |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.1 Identities | XMPP identities (JIDs) shall be as defined in IETF RFC 7622 [10]. They are of the form localpart@domainpart/resourcepart. For the present document localpart is defined as a telephone number, in international format including the preceding + sign. This shall then be used, together with the current time, to create the mo... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.2 XML Namespace | All new XML elements defined in the present document use an xmlns attribute to specify a namespace specific to the present document. Note that this includes cases where an element has the same name but a different format to a similar element defined in another specification, for example the element <encrypted/>. A name... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.3 Provisioning | The provisioning of an endpoint is carried out by its KMS. This provides the endpoint, which has an identity agreed with the KMS, with its private key material and with a certificate for the domain it is in, and certificates for all domains that may include other endpoints with which it may communicate in either direct... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.4 MIKEY-SAKKE Message | A first endpoint that has a message to send to a second endpoint shall construct a MIKEY-SAKKE message as defined in ETSI TS 103 816-2 [12] including all payloads there defined, including a unique RAND payload and a timestamp. The cryptographic identities of the endpoints required are determined from the JIDs of the en... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.5 Symmetric Key | The SSV transferred using a MIKEY-SAKKE message is used at the source to create a symmetric key used for encryption of information that is included within that XMPP message and at the destination, after decryption, to recover that symmetric key and use it for decryption of that information. For greater commonality with... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.6 XMPP Message Format | The present document primarily considers the message stanza in an XMPP message, included as the XML element <message/>. A message encrypted using the present document shall include a message stanza. This stanza shall have five common attributes to, from, id, type and xml:lang that are specified in clause 8.1 of IETF RF... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.7 Message Encryption | Like the voice data encryption used by ETSI TS 103 816-2 [12], the message encryption used by the present document uses AES-GCM, an Authenticated Encryption with Associated Data (AEAD) algorithm. This algorithm is also used by XEP-0384 [16], and thus some of the latter's approach to message stanza encryption is followe... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.8 Message Decryption | A received message shall be decrypted and authenticated at its destination by: • Recovering the three pieces of binary data (the MIKEY-SAKKE message, the IV and the message ciphertext) by extracting the three base64 encoded fields and reversing the base64 encoding. Message decryption fails if all three cannot be extrac... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.9 Message Delivery Receipt | An endpoint that is compliant with the present document shall implement message delivery receipt as defined in XEP-0184 [14]. Message delivery receipt is requested by the inclusion of a <request/> element within the message stanza. If requested, then this shall be added to the unencrypted message stanza before encrypti... |
9f104dd5892e79711302a15ac93b5e8d | 103 816-3 | 5.10 Attached Content | For the purposes of the present document, an attachment to a message is a file that is encrypted and stored on a server that is accessible by the message recipient. A message may "contain" (i.e. provide a link to) one or more attachments. Such a file shall be encrypted using AES-GCM; AES-128 should be used, but AES-256... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 1 Scope | The present document has the objective: • to define minimum requirements for data and services usability on professional and general public IoT devices and platforms, whether they are critical or not; • to develop a horizontal cross-domain specification encompassing these requirements. |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 2 References | |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 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... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 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... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 3 Definition of terms, symbols and abbreviations | |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 778 [i.1] and the following apply: data consumer: AI, monitoring algorithm or human that uses the data provided by an IoT platform or device NOTE: After the data consumer has used the data, they remain available for further usage. ML algorithms: s... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 3.2 Symbols | Void. |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 4G/5G 4th/5th Generation (mobile networks) AI Artificial Intelligence AI/ML Artificial Intelligence/Machine Learning AIOTI Alliance for Internet of Things Innovation API Application Programming Interface CPU Central Processing Unit CSV Comma S... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 4 Recommendations for data usability | ETSI TR 103 778 [i.1] identifies and describes use cases where the IoT data and services require data usability for humans and for machines consuming data for AI (for example machine learning). The data that IoT devices and platforms provide should be easily accessed to all authorized users, understood and acted upon b... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.1 General considerations | This clause contains the essential requirements to follow for preserving the data usability. Here, an abstract conceptual model is provided for giving unambiguous definitions of each guideline and, at the same time, to pave the way for future developments. With respect to the content of Annex A, this clause provides th... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2 Service requirements | |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2.1 Requirements to be fulfilled by sensor/data sources | Requirement number Related recommendation Requirement REQ_SERV_1_001 Terminology. Data generated or provided by a sensor shall have a description of the data using a shared terminology defined within an ontology. REQ_SERV_1_002 Mitigation of data heterogeneity. A data mitigation procedure should have foreseen if sensor... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2.2 Requirements to be fulfilled by IoT platform | Requirement number Related recommendation Requirement REQ_SERV_2_001 Data format description and intelligibility. If historical data is available the IoT platform shall allow download of data in a bulk format such as CSV, Apache Parquet, or other formats. REQ_SERV_2_002 Terminology. IoT platform shall allow linking of ... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2.3 Requirements to be fulfilled by AI/ML or monitoring function | Requirement number Related recommendation Requirement REQ_SERV_3_001 Explainability. Used machine learning algorithms shall be transparent and to provide explanations about the output produced. An appropriate ontology or semantics should be used. REQ_SERV_3_002 Data format description and intelligibility. Used artifici... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2.4 Requirements to be fulfilled by operator of system | Requirement number Related recommendation Requirement REQ_SERV_4_001 Preservation of integrity, privacy and security. The operators shall verify that the system is compliant with the regulations related to data privacy. REQ_SERV_4_002 Preservation of integrity, privacy and security. The operators shall verify that the ... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.2.5 Requirements to be fulfilled by data users | Requirement number Related recommendation Requirement REQ_SERV_5_001 Output management. Users should have the knowledge to access the outcome of the artificial intelligence components. REQ_SERV_5_002 Data format description and intelligibility. Users shall be equipped with tools able to read properly the data format wi... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3 Operational requirements | |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3.1 Requirements to be fulfilled by sensor/data sources | Requirement number Related recommendation Requirement REQ_OPE_1_001 Data coordinates. The data measured by the sensors shall be time-stamped. This will allow to evaluate a potential repetition rate or data redundancy/duplication. REQ_OPE_1_002 Data quality. When relevant, the geolocation measurement/configuration of th... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3.2 Requirements to be fulfilled by IoT platform | Requirement number Related recommendation Requirement REQ_OPE_2_001 Output management. Key metrics (latency, throughput, memory usage, processor utilization, disk space, resource capabilities (CPU and memory speed), temperature) should be defined and provisioned. REQ_OPE_2_002 Data coordinates. All data handled by the ... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3.3 Requirements to be fulfilled by AI/ML or monitoring function | Requirement number Related recommendation Requirement REQ_OPE_3_001 Data quality. Used machine learning/monitoring algorithms shall verify the integrity of the data received as input. REQ_OPE_3_002 Mitigation of data heterogeneity. Used machine learning/monitoring algorithms shall verify the format of the data received... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3.4 Requirements to be fulfilled by operator of system | Requirement number Related recommendation Requirement REQ_OPE_4_001 IoT infrastructure/devices bootstrap. At the time of deployment, operators shall verify that the overall infrastructure works properly and that all components are able to communicate each other. REQ_OPE_4_002 IoT infrastructure/devices bootstrap. At th... |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 5.3.5 Requirements to be fulfilled by user of data | Requirement number Related recommendation Requirement REQ_OPE_5_001 Data access. Users shall possess the required authorization for accessing data. |
c02efec878b6c8dfde8dcc88395515ac | 103 779 | 6 Conclusion | The present document aimed to provide a comprehensive set of guidelines and recommendations to design and deploy an effective and efficient IoT-based system potentially integrating complex IoT infrastructure. Such guidelines and recommendations represent important insights the engineers should follow to make IoT-based ... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 1 Scope | The present document is intended to specify the Key Management Server (KMS) Certificate used for sharing security credentials between KMS domains. It is intended for use in connecting domains of products based on Multimedia Internet Keying Sakai-Kasahara Key Encryption (MIKEY-SAKKE) using separate KMSs. |
1ee513be2819270b317262bd0025154e | 103 816-1 | 2 References | |
1ee513be2819270b317262bd0025154e | 103 816-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... |
1ee513be2819270b317262bd0025154e | 103 816-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... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 3 Definition of terms, symbols and abbreviations | |
1ee513be2819270b317262bd0025154e | 103 816-1 | 3.1 Terms | Void. |
1ee513be2819270b317262bd0025154e | 103 816-1 | 3.2 Symbols | Void. |
1ee513be2819270b317262bd0025154e | 103 816-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ECCSI Elliptic Curve-based Certificateless Signatures for Identity-based encryption IETF Internet Engineering Task Force KMS Key Management Server KPAK KMS Public Authentication Key LTE Long-Term Evoluti... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 4 MIKEY-SAKKE KMS Certificate | |
1ee513be2819270b317262bd0025154e | 103 816-1 | 4.1 Description | A KMS Certificate is a certificate that applies to an entire domain of users. A Certificate consists of eXtensible Markup Language (XML) containing the information necessary to encrypt messages to a domain of users and verify signatures from the domain of users. It is assumed that the User Equipment (UE) is managed by ... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 4.2 Fields | The KMS Certificate shall be named a 'KmsCertificate' within the XML. This type shall have the following subfields: Name Description Version (Attribute) The version number of the certificate type (1.0.0). Role (Attribute) This indicates whether the certificate is a "Root" or "External" certificate. CertUri The URI of t... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 4.3 MIKEY-SAKKE User IDs | To secure communications with a specific user, the initiator shall compose the MIKEY-SAKKE User Identifier (UID) to which the message will be encrypted. Clients shall support MIKEY-SAKKE RFC [3] identifier format, denoted by the value '1'. ETSI TS 133 179 [5] defines an identifier format for URIs. Clients may support t... |
1ee513be2819270b317262bd0025154e | 103 816-1 | 4.4 XML Schema for KMS Certificate | <xsd:element name = "SignedKmsCertificate" type = "SignedKmsCertificateType"/> <xsd:complexType name = "SignedKmsCertificateType"> <xsd:sequence> <xsd:element name = "KmsCertificate" type = "KmsCertificateType"/> <xsd:element ref = "ds:Signature" minOccurs = "0"/> </xsd:sequence> <xsd:anyAttribute namespace = "##other"... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 1 Scope | The present document defines regional profiles for use by broadcasters and receiver manufacturers to create good text experiences for audiences in different markets. |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 2 References | |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 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... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 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... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 3 Definition of terms, symbols and abbreviations | |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 3.1 Terms | Void. |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 3.2 Symbols | Void. ETSI ETSI TS 103 771 V1.1.1 (2020-11) 6 |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AM Amplitude Modulation DAB Digital Audio Broadcasting DRM Digital Radio Mondiale EBU European Broadcasting Union LTR Left-To-Right RTL Right-To-Left SDC Service Description Channel |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 4 Introduction | The DRM Consortium maintains the present document to provide a central point for the definition of regional profiles. An attempt is made to keep these definitions in sync with the respective document maintained by WorldDAB for the DAB family of standards (see annex E, ETSI TS 101 756 [i.1]). |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5 Regional profiles | |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.1 Introduction | The text labels used in DRM consist of the SDC data entity type 1, providing identification of the service, and the text message feature, which provides additional information to accompany an audio service. Unicode is a huge standard, covering a vast breadth of situations, not all of which will be relevant in every mar... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.2 Broadcaster considerations | Regional profiles are a good way to align the features used by broadcasters and the implementations of receiver manufacturers for specific markets, typically served by local and regional transmissions. ETSI ETSI TS 103 771 V1.1.1 (2020-11) 7 The target areas of DRM transmissions, however, may not be covered by a single... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.3 Receiver considerations | DRM receivers - particularly if supporting reception of DRM services in the AM bands - will often be exposed to services originating from other regions, but may only support the functionality of the profile expected in the sales region of the receiver. Receivers designed for a particular regional profile shall provide ... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4 Regional profile definitions | |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4.1 Encoding and decoding requirements | Table 1: Encoding and decoding requirements Profile Service label text control field settings Text message text control field settings Glyph set EBU Latin - 0000b Complete EBU Latin-based repertoire (see ETSI TS 101 756 [i.1], annex C) All Europe - 0000b Complete EBU Latin-based repertoire (see ETSI TS 101 756 [i.1], a... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4.2 Additional information | |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4.2.1 Arab States Broadcasting Union profile | The basis of the profile is language coverage for the members of the ASBU. Arabic is the core requirement, but some countries in this region also provide services in European languages. Receivers shall provide either the Minimum RTL implementation (see ETSI ES 201 980 [1], clause 6.7.4.2), or the Unicode bidirectional ... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4.2.2 Indian Core profile | The basis of the profile is language coverage for the major scripts used in India and neighbouring countries. This includes as a minimum the English and Hindi scripts, along with writing support for languages such as Bodo, Dogri, Kashmiri, Konkani, Maithili, Marathi, Santali, Sindhi, Nepali, and Sanskrit (the Devanagar... |
70b8d25fb63a6a9b04811f6296083025 | 103 771 | 5.4.2.3 Thai profile | The basis of the profile is language coverage needed for Thailand, therefore Thai and Latin scripts are included. These scripts are LTR and so the base direction flag shall be set to 0 and the bidi flag shall be set to 0. In general, receivers will need to be able to combine glyphs and will have to be capable of reorde... |
b61a0bf651537071c0010f2ac77f17ba | 103 813 | 1 Scope | The present document covers the minimum characteristics which are considered necessary for the Serial Peripheral Interface (SPI) communication of an SSP in order to provide compliance to ETSI TS 103 713 [1]. The present document specifies the test cases for: • the physical layer (electrical characteristics); • the MAC ... |
b61a0bf651537071c0010f2ac77f17ba | 103 813 | 2 References | |
b61a0bf651537071c0010f2ac77f17ba | 103 813 | 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. • In the case of a reference... |
b61a0bf651537071c0010f2ac77f17ba | 103 813 | 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. • In the case of a reference... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.