hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.1.3 Challenge response based systems | A challenge-response method should be used at initialization and for key establishment, key refresh, events. If used the provisions in the present document apply. Only cryptographically relevant challenge response schemes shall be used (i.e. the present document does not support challenge response based on non-cryptogr... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.2 Asymmetric keyed systems (digital signature) | |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.2.1 Self attestation of identity | A device should only be able to perform a self-attestation of its identity at initialization. The self-attestation shall be provided in the form of a digital signature and include a signed public key. EXAMPLE: Digital self-attestation is done by creating a document, hashing it and encrypting the hash with the self-gene... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.2.2 3rd party attestation of identity | The identity (canonical) and identifying attributes (see clauses 5.2.2.3 and 5.2.2.4) of a device should be attested to by an appropriate independent 3rd party. NOTE: This is consistent with the Attribute Authority Tree framework described in ETSI TS 103 486 (see bibliography). Proofs of identity shall be made availabl... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.2.3 Self attestation of capability | A device should only be able to perform a self-attestation of its capability at initialization. The self-attestation shall be provided in the form of a digital signature and include a self-signed public key. NOTE 1: In ETSI TS 103 486 each capability is identified as an attribute that is nominally independent of the ro... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.2.4 3rd party attestation of capability | Identifying attributes of a device should be attested to by an independent 3rd party. The public key of the relevant attribute authority should be installed locally to the device. NOTE: This is consistent with the Attribute Authority Tree framework described in ETSI TS 103 486 (see bibliography). Proofs of identity sha... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 6.1 General provisions - integrity | The general principle is that all exchanged discrete messages shall have their integrity verified on reception at the device. The integrity check function shall be cryptographically strong and may be included in a MAC for symmetric keyed associations, or in a digital signature for asymmetric keyed associations. Any mes... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 6.2 General provisions - confidentiality | The details of the cryptographic algorithm used to protect the confidentiality of data are not defined in the present document, although the boundary conditions and core requirements are stated. NOTE: If the device supports XGS-PON the provision of XGEN payload encryption as defined in Annex C.15.4 of Recommendation IT... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 7.1 General provisions | For protection of management and configuration data the provisions of ETSI TS 103 961 [3] apply (see also clause 4.3 of the present document). Every access device shall have a Root of trust for Storage (RtS) (see for example [i.1] and [i.2]). The present document defines, in this clause, the specific data to be maintai... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 7.2 Access control in OAN devices | The provisions identified in ETSI TS 103 924. Clause 7.2 [1] apply with the additional detailed provisions identified in the present document (see also Annex B). All data in OAN devices shall be made available to authorized entities using the principle of least privilege (see NIST SP 800-160 Vol.1 Rev.1 [i.5], ISO/IEC ... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 7.3 Access Control rules for OAN devices | The following rules shall be implemented in OAN devices. NOTE 1: Access control rules are atomic and identify only one condition per rule. Rule CFG-AC Descriptive format: Only a device administrator shall be allowed to update, or delete, an entry in the configuration data object: • P ∃!{S∪A∪O∪C} shall be true only when... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 7.4 Access control policy in OAN devices | An access control policy combines rules into an overall access control condition. As above the overall policy should be defined in such a way that all rules of a policy have to pass in order to permit access. A policy shall only set access control permission to True where all rules of any policy pass (i.e. the only com... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 1 Scope | The present document defines security measures for the management of Optical Network devices and services as defined in ETSI TS 103 962 [4] and ETSI TS 103 963 [5]. The present document extends the provisions identified in the Catalogue of Requirements for Optical Network and Device Security from ETSI TS 103 924 [1]. |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 2 References | |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 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... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 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... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 3 Definition of terms, symbols and abbreviations | |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 3.1 Terms | For the purposes of the present document, the following terms apply: canonical identifier: structured identifier that is globally unique crypto-agile: able to change or replace the existing suite of cryptographic algorithms or parameters with ease and without the rest of the infrastructure being significantly affected ... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 3.2 Symbols | Void. |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAT Authority Attribute Tree AES Advanced Encryption System CTR CounTeR NOTE: Mode of operation of a cryptographic algorithm. ECDSA Elliptic Curve Digital Signature Algorithm EMS Element Management System FALCON Fast Fourier Lattice-based Comp... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 4.1 General | As stated in ETSI TS 103 924 [1] the provisions for securing the management of the optical network should follow existing best practice for securing management data and protocols. The present document defines an abstract profile of existing best practice with specific mappings in informative annexes. ETSI ETSI TS 103 9... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 4.2 Network management functional model | The optical network manager shall support the following functions: • discovery and update of the network topology in real time; • configuration of devices and services; • FCAPS management (Fault Configuration Accounting Performance Security or Fault management, Configuration management, Accounting management, Performan... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 4.3 Network management specificities | The specificities of managing network configuration and performance (e.g. Grade of Service, routing information to indicate where to address/send data, allocation of bandwidth to individual end-points) shall be managed through the configuration data elements. EXAMPLE: The specificities include the management of network... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 4.4 Service control specificities | An ON may support multiple services (see Annex D of ETSI TS 103 962 [4]). Each service shall be managed as a discrete managed object (i.e. the service is the managed object). |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 4.5 Network analysis specificities | For the purposes of allowing the manager to make decisions the managed entity shall gather relevant metrics for each of fault management, security breach management, and performance management. NOTE 1: The gather of metrics as defined above is distinct from the configuration of security attributes of any managed entity... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 7 Secure storage of management data | |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 7.1 General provisions | The managed object shall have means to ensure that data in the secure storage area is stored in a form that maintains confidentiality. ETSI ETSI TS 103 961 V1.1.1 (2023-12) 12 EXAMPLE: A TPM [i.6] may provide means to give a guarantee of tamper resistance that assures the confidentiality of data without requiring the d... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 7.2 Access control | In like manner to ETSI TS 103 962 [4] and ETSI TS 103 963 [5] the management system shall implement an access control policy in which the right to access any protected element (referred to as objects) shall be made by evaluation of the rules contained in the policy (see also ETSI TS 102 165-2 [i.5]). The principles of ... |
304dcd25d8134986ddac3d85fb583734 | 103 961 | 7.3 Logging requirements | As stated in clause 7.1 any change in configuration shall be recorded and the record of changes shall be maintained and stored in a secure storage area (where the key for the secure storage area is managed by an RtS). The present clause provides additional requirements for the content of such records. NOTE 1: The gener... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 1 Scope | The present document specifies the access profile requirements and recommendations of smart metering, city and buildings as well as any other similarly applicable use case for the DECT-2020 New Radio (NR). |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 2 References | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 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... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 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... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 3 Definition of terms, symbols, and abbreviations | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 3.1 Terms | Void. ETSI ETSI TS 103 874-2 V2.1.1 (2026-03) 9 Release 2 |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 3.2 Symbols | Void. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 636-1 [1] and the following apply. NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TS 103 636-1 [1]. CVG Convergence (layer) DLC Data Link Control (layer)... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4 Use Case Descriptions | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.1 General | The present document defines a generic access profile that can be used in multiple different use cases with a basic assumption of large number of devices and need for multi-hop mesh networking topology. The following clauses define a set of use cases recognized by TC DECT [i.1] but the use of this access profile is not... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.2 Examples of use cases | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.2.1 Smart Electricity Metering | Electricity metering refers to electronic devices installed in buildings to record the consumption of electricity and report it to a backed system for monitoring and billing purposes. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.2.2 Smart City Applications/Smart Street Lighting | Smart city applications are about collecting environmental sensor data and controlling some of the infrastructure devices, from which streetlights are considered. ETSI ETSI TS 103 874-2 V2.1.1 (2026-03) 10 Release 2 Smart Street lighting is about controlling the use of the lights in efficient manner. The control may be... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.2.3 Smart Building Applications | Smart building is a concept of various applications that consider energy efficiency, space optimization, environment quality and functionality. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.2.4 Smart Emergency Lighting | Smart emergency lighting is about features for supporting the set up and maintenance of the emergency lighting. For example, the backup battery's (which is used in case mains power is cut) charging status and whether the light bulb/LED is broken is reported to a monitoring system, removing the need for site audits and ... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3 Characteristics of the use cases | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.1 Physical location | The smart building and emergency lighting are mostly confined on premises of larger buildings, where the radio signals often face high path loss and strong fading caused by the concrete walls and floors. Further, buildings with modern selective glass windows and concrete and steel structure wall have very significant s... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.2 Topology | The topology assumption of each use case supported by this profile is assumed to be based on mesh, as the number of devices for a network may be relatively high and the traffic characteristics allow multi-hop networking. Most of the use cases are at least partly confined to buildings causing strong fading conditions. M... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.3 Roles | Each device within a use case can have similar role in terms of producing measurement results or e.g. switching the lights on/off and routing data. However, one or some of the devices need to be connected to a gateway which has further connection (e.g. cellular, LAN) to deliver the measurement results to the monitoring... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.4 Power sources | Electricity meters, streetlights and emergency lights are typically mains powered devices. Emergency lights need to deal with electricity cut-down situations, so despite of the normal use of the mains power, they are equipped with batteries. A typical regulation requires 90 minutes operation with batteries. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.5 Traffic characteristics | This profile is agnostic on used application data formats. However, the applications may require support of up to 1 500 Bytes of length due to use of IPv6. The traffic is mostly uplink, while configuration and some control may require downlink messaging. Local routing between RDs is seen lighting use case. Examples of ... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 4.3.6 Security | The integrity of the measurement data is highly important in each use case. The measurement, configuration and control data are generally considered private within the wireless communication, although e.g. some smart city data is likely published elsewhere. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 5 Radio Reception and Transmission | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 5.1 Supported bands | Selection of frequency band, operating channel bandwidth and absolute channel numbers may differ between different regions. At least one band shall be chosen. When operating at band 1 an RD shall follow the values presented in Table 5.1-1 and follow definitions given in ETSI TS 103 636-2 [2]. Table 5.1-1: Band, bandwid... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 5.2 Maximum output power | RD may support any of the maximum transmitter outpower class I, class II, class III or class IV. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 5.3 RX Gain value | As defined in ETSI TS 103 636-2 [2], clause B.2.2. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 6 Physical layer | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 6.1 Radio device capabilities | RD shall support following physical layer configuration: • Maximum number of spatial streams: 1; • Reception for transmit diversity: 1; • Subcarrier width scaling - μ: 1; • Fourier transform scaling - β: 1; • Supported modulation and coding scheme: as defined clause 6.2; • Number of HARQ processes: 1 per communication ... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 6.2 Supported MCS and Transport Block Sizes | The RD shall support MCS-0 for one subslot transmissions and MCS-1 for 1 to 8 subslot transmissions, with granularity of one subslot granularity. The transmission length and used modulation shall be selected so that used transport block size does not exceed 2 088 bits. Table 6.2-1 presents an example transport block si... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7 MAC layer | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.1 MAC Configuration Overview | The RD shall support mesh network architecture and indicate its capabilities in the RD capability IE field as defined in clause 7.3.4.3.5. The RD shall support MAC procedures and data units as depicted in Table 7.1-1 and as defined in clauses 7.2 to 7.4. Use of other MAC procedures and data units may be possible in the... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2 MAC Procedures Configuration | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1 Spectrum Management Procedures | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.1 General | For Further Study. ETSI ETSI TS 103 874-2 V2.1.1 (2026-03) 15 Release 2 |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.2 Operating Channel(s) and Subslot(s) selection | Operating Channel(s) and Subslot(s) selection Procedure is supported as described in clause 5.1.2 in ETSI TS 103 636-4 [4]. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.3 Last Minute Scan | Last Minute Scan Procedure is supported as described in clause 5.1.3 in ETSI TS 103 636-4 [4]. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.4 Selecting RD for Association | Selecting RD for Association Procedure is supported as described in clause 5.1.4 in ETSI TS 103 636-4 [4], with the following addition: • An RD shall calculate its own route cost for each association target candidate and select the RD with the lowest calculated route cost. In case of selecting RD to start Secure Joinin... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.5 Beacon Transmission | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.5.1 General | In addition to Operating Channel(s) and Subslot(s) selection and Beaconing Transmissions defined in clauses 5.1.2 and 5.1.5 in ETSI TS 103 636-4 [4], the following clauses 7.2.1.5.2 and 7.2.1.5.3 apply to Beacon transmission timings. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.5.2 Network Beacon Transmissions | RD in FT mode shall send Network Beacons by applying the structure defined in clause 11.2.1 and the parameter values defined in clause 7.3. For Network Beacons sent for Secure Joining procedure, see clause 10.3. To improve Network Beacon detection probability by other RDs, the RD in FT mode may randomize the transmissi... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.5.3 Cluster Beacon Transmissions | When RD in FT mode detects other RD's Cluster Beacons and their transmission timings, the RD should: • prioritize channels that have a lower number of Cluster Beacons; • transmit its own Cluster Beacon equally spaced with other Cluster Beacons; • synchronize its own Cluster Beacon transmission with other beacons being ... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.5.4 Joining Beacon Transmissions | If Joining Beacons within Secure Joining procedure, as defined in clause 10.3, are enabled the RD in FT mode shall send Joining Beacons by applying the structure defined in clause 11.2.3 and the parameter values defined in clause 7.3 in the present document. The recommended interval to transmit Joining Beacons is 500 m... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.1.6 Power Control | Power Control Procedure is supported as described in clause 5.1.6 in ETSI TS 103 636-4 [4]. The transmitter should adjust the TX power for an initial transmission with its peer using MCS1 so that received power at the intended receiver is as follows: RX_Power ≥ TX_Power - PathlossEstimate Where: • RX_Power = -88 dBm. •... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.2 Broadcast Procedure | Broadcast Procedure is supported as described in ETSI TS 103 636-4 [4], clause 5.2. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.3 Random Access Procedure | Random Access Procedure is supported as described in ETSI TS 103 636-4 [4], clause 5.3. 3 3 2 2 2 2 1 1 1 1 1 1 Time Cluster Beacon from RD-a Cluster Beacon from RD-c Cluster Beacon from RD-x Cluster Beacon Period 1 Possible Cluster Beacon position with priority to other positions Cluster Beacon Period ETSI ETSI TS 103... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.4 Scheduled Access Data Procedure | Not applied in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.5 HARQ Operation | HARQ Operation is supported as described in ETSI TS 103 636-4 [4], clause 5.5. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.6 Multiplexing and Assembly | Multiplexing and Assembly Procedure is supported as described in ETSI TS 103 636-4 [4], clause 5.6. Transmitter shall concatenate multiple Information Elements in a MAC PDU but should only include one DLC PDU per MAC PDU, as defined in clause 11 of the present document. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.7 Mobility Procedures | Mobility Procedure is supported as described in ETSI TS 103 636-4 [4], clause 5.7, with following addition: • An RD shall calculate its own route cost for each association target candidate for mobility, including the RD in FT mode it is currently associated, and select the RD with the lowest calculated route cost. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.8 Association Procedure | Association Procedure is supported as described in ETSI TS 103 636-4 [4], clause 5.8, with the following additions: • When associating, an RD shall use Association Request MAC PDU structure defined in clause 11.3.1 and the parameter values defined in clause 7.3. • An RD shall respond to Association Request MAC PDU by a... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.9 Security Procedures | Security Procedure of Security Mode 1 with Security IV type set to One-time HPC is supported as described in ETSI TS 103 636-4 [4], clause 5.9. NOTE: To avoid compromising security, care should be taken to make sure the same initialization vector value is never repeated, e.g. in restarting situations. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.10 Reconfiguration Procedure | Not applied in this version of the profile. ETSI ETSI TS 103 874-2 V2.1.1 (2026-03) 18 Release 2 |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.11 Group Assignment Procedure | Not applied in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.12 Paging Procedure | Not applied in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.2.13 Selective Source Routing Procedure | Not applied in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3 MAC Protocol Data Units Configuration | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.1 General | For Further Study. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.2 Physical Header Field | Physical Header Field configuration for header type 1 is depicted in Table 7.3.2-1. Table 7.3.2-1: Physical Layer Control Field for header type 1 Field Recommended values Normative action/comment Header Format 0b000 Header type 1 selected. Packet length type 0b0 The length type is set in subslots. Packet length 0b0000 ... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3 MAC PDU | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.1 General | For Further Study. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.2 MAC Header Type | MAC header type for Beacon header is depicted in Table 7.3.3.2-1. Table 7.3.3.2-1: MAC header type for Beacon header Field Recommended values Normative action/comment Version 0b00 PDUs with higher Version number are not applied in this version of the profile. MAC security 0b00, 0b10 Value 0b00 (no MAC security) is used... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.3 MAC Common header | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.3.1 Data MAC PDU header | Data MAC PDU header is depicted in Table 7.3.3.3-1. Table 7.3.3.3-1: Data MAC PDU header Field Recommended values Normative action/comment Reserved 0b000 As defined in ETSI TS 103 636-4 [4]. Reset 0b1 Reset for every PDU, i.e. no re-ordering function is in use. Sequence number Any As defined in ETSI TS 103 636-4 [4]. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.3.2 Beacon Header | Beacon Header configuration for Beacon messages is depicted in Table 7.3.3.3.2-1. Table 7.3.3.3.2-1: Beacon header for Beacon messages Field Recommended values Normative action/comment Network ID Any As defined in ETSI TS 103 636-4 [4]. Transmitter address Any As defined in ETSI TS 103 636-4 [4]. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.3.3 Unicast Header | Unicast Header configuration is depicted in Table 7.3.3.3.3-1. Table 7.3.3.3.3-1: Unicast header Field Recommended values Normative action/comment Reset 0b0 No MAC re-ordering function expected. Sequence number Any As defined in ETSI TS 103 636-4 [4]. Receiver Address Any As defined in ETSI TS 103 636-4 [4]. Transmitte... |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.3.4 RD Broadcasting Header | Not applied in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.3.4 MAC Multiplexing headers | MAC Mux header options A, B, C and D shall be supported in this version of the profile. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.4 MAC Messages and Information Elements | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.4.1 General | For Further Study. |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.4.2 MAC Messages | |
2b247f429fc1a284ed3457befe0efafe | 103 874-2 | 7.3.4.2.1 General | For Further Study. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.