hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.21.0 Definition | Sub-class of: s4envi:WasteProcessingTask Represents the task of treating waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.21.1 s4envi:Composting | Is instance of: s4envi:WasteTreatmentTask Aerobic process designed to produce compost [i.8], clause 3.2. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.21.2 s4envi:Methanisation | Is instance of: s4envi:WasteTreatmentTask Process of controlled decomposition of biodegradable materials under managed conditions where free oxygen is absent, at temperatures suitable for naturally occurring mesophilic or thermophilic anaerobic and facultative bacteria species, that convert the inputs to a methane rich... |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.22 Category of Function s4envi:WasteProcessingFunction | Sub-class of: saref:Function Represents the functionality of processing (pre-treating, treating, disposing of) waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.23 Category of Function s4envi:WasteDisposalFunction | |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.23.0 Definition | Sub-class of: s4envi:WasteProcessingFunction Represents the functionality of disposing of waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.23.1 s4envi:IncinerationFunction | Is instance of: s4envi:WasteDisposalFunction, s4envi:WasteTreatmentFunction Function of incinerating. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.23.2 s4envi:LandfillFunction | Is instance of: s4envi:WasteDisposalFunction Function of landfilling. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24 Category of Function s4envi:WastePreTreatmentFunction | |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.0 Definition | Sub-class of: s4envi:WasteProcessingFunction Represents the functionality of pre-treating waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.1 s4envi:DisassemblyFunction | Is instance of: s4envi:WastePreTreatmentFunction ETSI ETSI TS 103 410-2 V2.1.1 (2024-10) 41 Function of disassembling. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.2 s4envi:HumanSortingFunction | Is instance of: s4envi:WastePreTreatmentFunction Function of sorting carrired out by a human. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.3 s4envi:MechanicalSortingFunction | Is instance of: s4envi:WastePreTreatmentFunction Function of sorting carried out by using mechanical forces. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.4 s4envi:OpticalSortingFunction | Is instance of: s4envi:WastePreTreatmentFunction Function of sorting carried out by using optical sensors. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.24.5 s4envi:SortingFunction | Is instance of: s4envi:WastePreTreatmentFunction Function of sorting. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25 Category of Function s4envi:WasteTreatmentFunction | |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.0 Definition | Sub-class of: s4envi:WasteProcessingFunction Represents the functionality of treating waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.1 s4envi:ColdCompostingFunction | Is instance of: s4envi:WasteTreatmentFunction Function of cold composting. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.2 s4envi:CompostingFunction | Is instance of: s4envi:WasteTreatmentFunction Function of composting. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.3 s4envi:VermicompostingFunction | Is instance of: s4envi:WasteTreatmentFunction Function of vermicomposting. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.4 s4envi:WindrowCompostingFunction | Is instance of: s4envi:WasteTreatmentFunction Function of windrow composting. ETSI ETSI TS 103 410-2 V2.1.1 (2024-10) 42 |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.25.5 s4envi:MethanisationFunction | Is instance of: s4envi:WasteTreatmentFunction Function of methanising. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.26 Property s4envi:WasteProcessingCapacity | Maximal capacity of a waste processing site in terms of volume or mass of waste processed per unit of time. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.27 Property s4envi:Yield | Ratio of input waste to output resource. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.28 Property s4envi:becomes | Is a: owl:ObjectProperty Domain: s4envi:Waste Range is union of: s4envi:FinalWaste, s4envi:SecondaryRawResource Waste becomes either a secondary raw resource, or final waste. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.29 Property s4envi:isDepositedAt | Is a: owl:ObjectProperty Domain: s4envi:Waste Range: s4envi:WasteProcessingSite Waste is deposited at a waste processing site. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.30 Property s4envi:isProcessedBy | Is a: owl:ObjectProperty Domain: s4envi:Waste Range: s4envi:WasteProcessingDevice Waste is processed by at least one waste processing device. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.31 Property s4envi:processingBeginsOn | Is a: owl:DatatypeProperty Domain: s4envi:Waste Range: xsd:date Waste begins being processed on a given date. |
fb6699740f66902e433d532bcc39c2fd | 103 410-2 | 6.2.3.32 Property s4envi:processingEndsOn | Is a: owl:DatatypeProperty Domain: s4envi:Waste Range: xsd:date Waste ends beging processed on a given date. ETSI ETSI TS 103 410-2 V2.1.1 (2024-10) 43 Annex A (informative): Bibliography • ETSI TS 103 267: "SmartM2M; Smart Applications; Communication Framework". • ETSI TS 102 689: "Machine-to-Machine communications (M... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 1 Scope | The present document, which is part 2 of a multi-part document, specifies the TS-UNB protocol. It contains an implementable description of its physical and MAC/link protocol layers. The present document is structured as follows: • clause 2 provides references; • clause 3 provides definitions of terms, symbols and abbre... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 2 References | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-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... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-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... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 3 Definitions of terms, symbols, and abbreviations | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 3.1 Terms | For the purposes of the present document, the following terms and definitions apply: equivalent signal to noise ratio: signal to noise ratio (including interference) of the received message as if it was only distorted by additive noise NOTE: The eqSNR-I is calculated based on a mutual information estimate of all radio-... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ΔT actual symbol duration ΔTdn Time interval between blocks of an extension frame ΔTdu maximum time window for a high priority uplink response ΔTTSI Time interval between core frame and extension frame ΔTud Time interval between uplink frame and dow... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledge ADSI Application Data Size Indicator (used in fragmentation procedure) AES Advanced Encryption Standard BC Beacon Core BDU Block Data Unit BE Beacon Extension BRxC Beacon receive Cycle BS Base Station BSSH Base Station Specific... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4 TS-UNB protocol description | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.1 TS-UNB in the LTN protocol families | Telegram-Splitting Ultra- Narrow Band (TS-UNB) protocol is one of the radio protocols specified for the radio interface of an LTN system; the other radio protocols for LTN systems are Lfour and DD-UNB (see ETSI TS 103 357 [i.17]). The TS-UNB protocol is designed to operate effectively in sub-GHz frequency bands. The pr... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.2 TS-UNB overview | The TS-UNB family is a low power wide area network with star topology based on an UNB approach using Telegram Splitting Multiple Access (TSMA). TSMA is a random channel access method wherein the radio transmission of a packet is divided into several short radio-bursts, which are sent in a non-contiguous manner over the... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.3 Modes of operation | Transmission modes4 An LTN system using TS-UNB protocol shall support uplink-only transmission (ULZ) and may optionally also support uplink-triggered downlink transmission (DLA). In addition to ULZ and DLA transmission, an LTN system may also support scheduled downlink transmission (DLB) and event-triggered downlink tr... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.4 Drawing and writing conventions | In this clause on TS-UNB, the drawing conventions for figures of protocol data units are, as follows: • fields to be transmitted are drawn from left to right; • left field is transmitted first; • right field is transmitted last. The writing conventions for tables of protocol data units are, as follows: • top field is t... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5 Link Layer | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.1 Link Layer overview | The Link Layer handles control procedures required to establish and maintain a connection between an end-point and a base station (see Figure 4-6). The link layer formats, functions and procedures, as defined in the present clause, shall be applied to the fixed MAC mode. Their usage in case of variable MAC mode depends... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2 Link Layer formats | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.1 Link Layer Protocol Data Unit (LPDU) | The link layer protocol data unit shall be as specified in Table 4-4. Table 4-4: Link Layer Protocol Data Unit (LPDU) Format Field length (in bytes) 1 to 245 (in UL) 1 to 250 (in DL) 0 to 245 (in UL) 0 to 250 (in DL) Field name Control Payload Data Payload Comment Only present if MAC Header Control flag = 1 may be omit... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2 Control Segments | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.1 Overview | A control segment shall consist of a control header field and zero or several additional fields. The control header value and the size of the control segment shall be as detailed in Table 4-6. Control segments shall be used only in fixed MAC mode. Table 4-6: List of Control Segments Control Header Direction Control Seg... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.2 Attach Request | The attach request control segment shall be used to attach the end-point to the base station. The format, as described in Table 4-7, shall be used when an end-point does not support IPv6 addressing. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 25 Table 4-7: Attach Request Control Segment Format Field length (in bytes) 1 2 4... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.3 Attach Accept | The base station shall send a message with an attach accept control segment to answer the attach request received from the end-point. The attach accept control segment shall have the format according to Table 4-9. Table 4-9: Attach Accept Control Segment Format Field length (in bytes) 1 2 2 Field content Control Header... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.4 Detach Request | If an end-point needs to disconnect from the network, the end-point shall send a message with a detach request control segment according to Table 4-10 to the base station. A base station may also send a detach request to an end-point to disconnect the end-point from the network. Table 4-10: Detach Request Control Segme... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.5 Detach Accept | A detach request from an end-point shall be answered with a detach accept control segment by the base station. A detach request from a base station shall be answered with a detach accept control segment by the end-point. The detach accept control segment shall have the format according to Table 4-11. ETSI ETSI TS 103 3... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.6 DLRX Status Query | The DLRX Status Query control segment shall be formatted as specified in Table 4-12. It may be sent from the base station to an EP to request a DLRX Status Response from the EP. Table 4-12: DLRX Status Query Control Segment Format Field length (in bytes) 1 Field content Control Header (0x20) |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.7 DLRX Status Response | The DLRX Status Response control segment shall be sent by an EP after receiving a DLRX Status Query from the base station. It shall be formatted as specified in Table 4-13. Table 4-13: DLRX Status Response Control Segment Format Field length (in bytes) 1 1 1 Field content Control Header (0x21) RSSI SNR RSSI Received si... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.8 DLRX Extended Status Query | The DLRX Extended Status Query control segment may be sent by the base station to request information on radio link parameters in the reception of a downlink message of either Class A, Class B or Class C. The DLRX Extended Status Query control segment shall be formatted according to Table 4-14. The end-point shall eval... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.9 DLRX Extended Status Response | The DLRX Extended Status Response control segment shall be sent by the end-point after the reception of a DLRX Extended Status Query control segment, sent by the base station. The DLRX Extended Status Response control segment shall be formatted according to Table 4-15. Table 4-15: DLRX Extended Status Response Segment ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.10 Link Adaptation Request | If the base station needs to change the configuration of the connection with an end-point, it shall send a Link Adaptation Request control segment, formatted as specified in Table 4-16. The requested configuration shall conform to the end- point capabilities announced during the attachment procedure. Table 4-16: Link A... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.11 Link Adaptation Confirm | If an end-point receives a Link adaptation request control segment from a base station, it shall respond with a Link adaptation confirm control segment, formatted as specified in Table 4-17. Table 4-17: Link Adaptation Confirm Control Segment Format Field length (in bytes) 1 Field content Control Header (0x25) |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.12 Sync Request | The Sync Request control segment shall be used by the end-point to request synchronization for the DLB mode and to retrieve DLB session information. It shall consist of three fields, as detailed in Table 4-18. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 28 Table 4-18: Sync Request Control Segment Format Field length (in bi... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.13 Sync Info | The Sync Info control segment shall be used by the base station to provide an end-point with the information for the DLB and DLC mode. The Sync Info control segment shall consist of twelve fields, as detailed in Table 4-19. Table 4-19: Sync Info Control Segment Format Field length (in bits) 8 16 24 64 128 32 4 2 3 2 1 ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.14 Resync Request | The Resync Request control segment shall be used by the end-point to request resynchronization for the DLB frame, in case of a loss of synchronization (i.e. one or several beacons not received). The Resync Request control segment shall be formatted according to Table 4-22. Table 4-22: Resync Request Control Segment For... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.15 Resync Info | The Resync Info control segment shall be used by the base station as a response to a Resync Request from an end-point. It shall be sent in DLA transmission and shall be formatted according to in Table 4-23. The Base Station may respond to a Resync Request with a Sync Info control segment instead of a Resync Info contro... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.16 Desync Request | The Desync Request control segment might be used by the end-point to explicitly request desynchronization for the DLB frame. The Desync Request control segment shall be formatted according to Table 4-24. Table 4-24: Desync Request Control Segment Format Field length (in bits) 8 8 Field content Control Header (0x34) Res... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.17 Desync Accept | The Desync Accept control segment might be sent by the base station as a response to a preceding Desync Request from the end-point. The Desync Accept control segment shall be formatted according to Table 4-25. Table 4-25: Desync Accept Control Segment Format Field length (in bits) 8 8 Field content Control Header (0x35... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.18 Sync System Adaptation Notify | The Sync System Adaptation Notify control segment shall be used by the base station to notify all end-points in its coverage area about changes in the DLB structure. This control segment shall consist of four fields, as detailed in Table 4-26. End-points shall not acknowledge a Sync System Adaptation Notify. Table 4-26... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.19 Sync Request Trigger | The Sync Request Trigger control segment shall be sent by a base station to force EP(s) to send a Sync Request. This control segment shall consist of one field, as detailed in Table 4-27. NOTE: This control message helps EP(s) to synchronize to a different base station or to get new sync information. Table 4-27: Sync R... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.20 Sync Adaptation Request | The Sync Adaptation Request control segment shall be used by the base station to update EP(s) with new beacon reception alignment. This control segment shall consist of four fields, as detailed in Table 4-28. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 32 Table 4-28: Sync Adaptation Request control segment format Field len... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.21 Sync Adaptation Confirm | The Sync Adaptation Confirm control message shall be used by an end-point to confirm a Sync Adaptation Request. This control segment shall consist of one field, as detailed in Table 4-29. Table 4-29: Sync Adaptation Confirm control segment format Field length (in bits) 8 Field content Control Header (0x39) |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.22 DLB Data Ack | The DLB Data Ack control segment shall be sent by an EP to acknowledge a DLB_Data frame, that requests an acknowledgment. This control segment shall consist of three fields, as detailed in Table 4-30. Table 4-30: DLB Data Ack control segment format Field length (in bits) 8 8 8 Field content Control Header (0x3B) DLB_Ac... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.23 DLC Data Ack | The DLC Data Ack control segment shall be sent by an EP to acknowledge a DLC_Data frame, that requests an acknowledgment. This control segment shall consist of three fields, as detailed in Table 4-31. Table 4-31: DLC Data Ack control segment format Field length (in bits) 8 4 12 Field content Control Header (0x3C) DLC_A... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.24 Group Assign Request | The Group Assign Request control segment shall be used by the base station to assign an end-point to a Group EUI. Group assignment is optional and may be conducted by the base station at will. An end-point may be assigned to multiple groups. A class B or class C end-point shall support up to 8 group assignments. This c... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.25 Group Assign Confirm | The Group Assign Confirm control segment shall be used by the end-point to confirm a Group Assign Request. This control segment shall consist of two fields, as detailed in Table 4-33. Table 4-33: Group Assign Confirm control segment format Field length (in bytes) 1 1 Field content Control Header (0x41) Assignment Count... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.26 Group Dismiss Request | The Group Dismiss Request control segment shall be used by the base station to dismiss an end-point from a group. It shall be formatted according to Table 4-34. Table 4-34: Group Dismiss Request control segment format Field length (in bytes) 1 8 1 Field content Control Header (0x42) Group EUI Dismissal Counter The dism... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.27 Group Dismiss Confirm | The Group Dismiss Confirm control segment shall be used by the end-point to confirm a Group Dismiss Request. This control segment shall be formatted according to Table 4-35. Table 4-35: Group Dismiss Confirm control segment format Field length (in bytes) 1 1 Field content Control Header (0x43) Dismissal Counter ETSI ET... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.28 Fragment Info | The Fragment Info control segment shall be used to signal a transmission of a fragment of a fragmented application payload. All fragment transmissions of a payload shall include the 7 byte Fragment Info control segment, as specified in Table 4-36, and a data payload with the according fragment of the complete applicati... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.29 DLRX Certification Status Query | The DLRX Certification Status Query control segment may be sent by the base station to request information on radio link parameters for the reception of the downlink message of either Class A, Class B or Class C. The DLRX Certification Status Query control segment shall be formatted according to Table 4-37. Table 4-37:... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.30 DLRX Certification Status Response | The DLRX Certification Status Response control segment shall be sent by the end-point after the reception of a DLRX Certification Status Query by the base station. The DLRX Certification Status Query control segment shall be formatted according to Table 4-38. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 35 Table 4-38: DLRX ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.31 DLRX Class A Statistic Query | The DLRX Class A Statistic Query control segment may be sent by the base station to request information on reception parameter statistics in the end-point of the corresponding and previous class A downlink messages. The DLRX Class A Statistic Query control segment shall be formatted according to Table 4-39. Table 4-39:... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.32 DLRX Class A Statistic Response | The DLRX Class A Statistic Response control segment shall be sent by the end-point after the reception of a DLRX Class A Statistic Query by the base station. The DLRX Class A Statistic Response control segment shall be formatted according to Table 4-40. Table 4-40: DLRX Statistic Class A Segment Format Field length (in... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.33 DLRX Class B Statistic Query | The DLRX Class B Statistic Query control segment may be sent by the base station to request information on reception parameter statistics in the end-point of the corresponding and previous class B downlink messages. The DLRX Class B Statistic Query control segment shall be formatted according to Table 4-41. Table 4-41:... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.34 DLRX Class B Statistic Response | The DLRX Class B Statistic Response control segment shall be sent by the end-point after the reception of a DLRX Class B Statistic Query by the base station. The DLRX Class B Statistic Response control segment shall be formatted according to Table 4-42. Table 4-42: DLRX Statistic Class B Segment Format Field length (in... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.35 DLRX Class C Statistic Query | The DLRX Class C Statistic Query control segment may be sent by the base station to request information on reception parameter statistics in the end-point of the corresponding and previous class C downlink messages. The DLRX Class C Statistic Query control segment shall be formatted according to Table 4-43. Table 4-43:... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.2.36 DLRX Class C Statistic Response | The DLRX Class C Statistic Response control segment shall be sent by the end-point after the reception of a DLRX Class C Statistic Query by the base station. The DLRX Class C Statistic Response control segment shall be formatted according to Table 4-44. Table 4-44: DLRX Statistic Class C Segment Format Field length (in... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.2.3 End-point Info Field | The end-point info field is used to negotiate TS-UNB protocol settings between end-point and base station. In the attach request control segment, this field shall indicate the end-point capabilities to the base station. In the attach accept control segment the base station shall announce the configuration of the connec... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3 Link Layer procedures | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.1 End-point attachment procedure | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.1.1 Introduction | Before an end-point and a base station exchange data, the end-point shall be attached to the base station. The end-point attachment procedure provides a base station with information about an end-point required for servicing the end-point and provides the end-point with a short address. Bidirectional end-points may ini... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.1.2 End-point configuration | The end-point capabilities are advertised to the base station during the attachment procedure. The base station can then select the operational mode to be used from the advertised capabilities. For class Z devices the configuration is static, class A devices can negotiate the configuration during an over-the-air attach... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.1.3 Class Z end-point attachment | Class Z devices are unidirectional devices and shall be pre-attached to a LTN System during manufacturing of the device. In the pre-attachment procedure the network key, the short address and the end-point info field shall be programmed in the end-point and stored in the service centre. Figure 4-8: Service centre based... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.1.4 Class A end-point attachment | Class A devices may be attached over-the air to allow dynamic configuration by the base station (see Figure 4-9). Figure 4-9: Over-the-air attachment procedure for class A devices The over-the-air attachment procedure shall start with a message from the end-point to the base station containing an attach request control... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.2 End-point detachment procedure | The over-the-air end-point detachment procedure allows an end-point to detach from a base station in a controlled manner. It allows the base station to remove end-points from the address resolution and to inform the service centre about the end-point detachment (see Figure 4-10). ETSI ETSI TS 103 357-2 V2.1.1 (2024-06)... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.3 End-point synchronization procedure | An end-point that is attached to a base station and supports class A and class B may be synchronized to a scheduled downlink transmission (DLB) by the following synchronization procedure (see Figure 4-12). ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 43 Figure 4-12: End-point synchronization procedure A sync info control se... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.4 End-point desynchronization procedure | A base station can terminate the class B mode with an end-point by the desynchronization procedure. For a desynchronization the base station shall send a link adaptation request with the DLB_mode bit set to 0. The end-point shall then confirm with a link adaptation confirm control segment. The end-point is then only op... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.5 Assisted resynchronization procedure | If an end-point loses synchronization to the base station, it may transmit a Resync Request control segment (see clause 4.5.2.2.14). The base station shall response with a Resync Info (see clause 4.5.2.2.15) or Sync Info control segment (see clause 4.5.2.2.13) sent in a DLA transmission. The base station may opt for th... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.6 Sync System Adaptation procedure | The Sync System Adaptation procedure is used to change DLB structure parameters during runtime. Synchronized end-points shall be informed before the DLB structure parameters are changed by sending a Sync System Adaptation Notify control segment in a broadcast message. If end-points are present with different beacon rx ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.7 Sync Adaptation procedure | The Sync Adaptation procedure is used to change Beacon RX cycle mode and Beacon RX cycle offset. The base station shall send a Sync Adapt Request control segment to the end-point. The end-point shall response with a Sync Adapt Confirm control segment. The end-point shall be assumed desychronized until the Sync Adapt Co... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.8 DLB acknowledgement procedure | Class B unicast and multicast transmissions may request an acknowledgement by setting the "response" MAC header flags (see Table 4-51). The acknowledgement for a Class B unicast or multicast shall be done via an uplink transmission comprising the DLB Data Ack control segment. NOTE: For multicasts, the number of address... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.9 DLC acknowledgement procedure | Class C unicast and multicast transmissions may request an acknowledgement by setting the "response" MAC header flags (see Table 4-51). The acknowledgement for a Class C unicast or multicast shall be done via an uplink transmission comprising the DLC Data Ack control segment. NOTE: For multicasts, the number of address... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.10 Grouping procedure | In class B, messages can be sent to multiple end-points at the same time (multicast). The end-points to be addressed are put together in a group. A group shall be identified by an EUI64 called group EUI and a network encryption key shall be assigned to the group called group key. An end-point may be assigned to a group... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.11 Simple end-point handover procedure | A simple handover procedure shall be initiated by a Sync Request Trigger control segment, sent by the base station. The end-point shall respond with a Sync Request control segment, which will be confirmed with a Sync Info control segment, sent by the new base station (see Figure 4-13). Figure 4-13: Simple handover proc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.