hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
baa46c383033a4406946797fe47211ae | 103 357 | 6.1 Overview | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.1.1 General description | 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 discontiguous over the radio channe... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.1.2 Modes of operation | The TS-UNB protocol offers several modes of operation in up- and downlink. If a LTN System is using TS-UNB protocol, it shall implement one subset of the different modes of operation according to Table 6-1. Some recommended sets of modes called profiles can be found in the annex A. The input data at the end-point for u... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2 Link Layer | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.1 Link Layer Overview | The Link Layer shall handle control procedures required to establish and maintain a connection between an end-point and a base station. The Link Layer definition shall be applied to the fixed MAC mode and can also be applied to the variable MAC mode of the present document. Figure 6-3: Link Layer interfaces with adjace... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2 Link Layer Format | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.1 Link Layer Protocol Data Unit (LPDU) | Table 6-2: Link Layer Protocol Data Unit (LPDU) Format Bytes: 1 1 Variable 1 Variable Variable (0 to 245) Control Length Control Segment 1 Control Segment n Data Payload Control Header 1 Control Body1 … Control Header n Control Body n Control Payload; Only present if MAC Header Control flag = 1 ETSI ETSI TS 103 357 V1.... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2 Control Segment | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.1 Overview | The control segments shall consist of the control header and the control body. The control header specifies the type and the size of the control segment. The control header values according to Table 6-3 shall be used for the fixed MAC mode of the TS-UNB protocol. Table 6-3: Link Layer Control Segments Control Header Di... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.2 Attach Request | The attach request control segment shall be used to attach the end-point to the base station. The following format shall be used, if an end-point does not support IPv6 addressing. Table 6-4: Attach Request Control Segment Format Bytes: 1 2 4 4 Control Header Control Body 0x10 End-point Info Nonce User Signature If the ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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 6-6. ETSI ETSI TS 103 357 V1.1.1 (2018-06) 40 Table 6-6: Attach Accept Control Segment Format Bytes: 1 2 2 Cont... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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 6-7 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 6-7: Detach Request Control Segment... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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 6-8. Table 6-8: Detach A... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.6 DLRX Status Query | The DLRX Status Query can be sent from the base station to an EP to request a DLRX Status Response from the EP. Table 6-9: DLRX Status Query Control Segment Format Bytes: 1 Control Header 0x20 |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.7 DLRX Status Response | The DLRX Status Response is sent by an EP after receiving a DLRX Status Query from the base station. Table 6-10: DLRX Status Response Control Segment Format Bytes: 1 1 1 Control Header Control Body 0x21 RSSI Signal to noise ratio ETSI ETSI TS 103 357 V1.1.1 (2018-06) 41 The RSSI is provided as unsigned fixed point with... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.8 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. The requested configuration shall conform to the end-point capabilities announced during the attachment procedure. Table 6-11: Link Adaptation Control Segment Format Bytes:... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.2.2.9 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. Table 6-12: Link Adaptation Confirm Control Segment Format Bytes: 1 Control Header 0x25 |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.3 Link Layer Procedures | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.3.1 End-point Attachment | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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 6-4: Service centre based... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.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. Figure 6-5: 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 segment accordin... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.2.3.2 End-point Detachment | The over-the-air end-point detachment procedure allows an end-point to deregister from a base station in a controlled manor. It allows the base station to remove end-points from the address resolution and to inform the service centre about the end-point detachment. Figure 6-6: Over-the-air detachment procedure for clas... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3 MAC Layer | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.1 Byte and Processing Order | Unless otherwise noted the byte order is most significant byte first and the processing of bit streams is most significant bit of most significant byte first. See Figure 6-8. Figure 6-8: Byte and processing order |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2 Fixed MAC Mode | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.1 Overview | The following MAC layer description applies to the fixed MAC mode, which is set by the MMODE field in the PHY layer (see clause 6.4.2.3.6). The MAC layer controls the timing of transmissions and keeps track of transmission windows. Furthermore it is responsible for address resolution and provides network level cryptogr... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2 MAC Formats in UL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.1 MAC Protocol Data Unit (MPDU) | If the LTN system using the TS-UNB protocol is operated in the fixed MAC mode, the uplink MPDU format according to Table 6-15 shall be used. Table 6-15: Uplink MPDU Format of fixed MAC mode Bytes: 1 2 or 8 3 0/1 Variable (1 to 245) 4 MAC Header Address MPDUCNT MPF MAC Payload SIGN ETSI ETSI TS 103 357 V1.1.1 (2018-06) ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.2 MAC Header | The MAC header shall be a one byte wide field signalling different MAC options for the packet. It shall be formatted according to Table 6-16. Table 6-16: Uplink MAC Header Format Bit Function Description 0 MAC version 0: Initial Version 1: Reserved 1 MPF flag 0: No MPF Field present 1: MPF Field present 2 Control flag ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.3 Address | The address field shall either contain a 16 bit short address or EUI64 of the end-point. The addressing mode bit in the MAC header determines which of these options is present in the packet. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.4 MPDUCNT | The MPDUCNT field shall contain a 24 bit counter value according to clause 6.3.2.4.2. If the attach flag bit in the header is set, the attachment counter according to clause 6.3.2.4.3 is used instead of the packet counter. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.5 MAC Payload Format (MPF) | The MPF field shall be present if the MPF flag of the MAC header is set to zero. The MPF field may be used to indicate the format of the MAC Payload. The MPF values shall be used according to Table 6-17. Table 6-17: MAC Payload Formats MPF Field value MPF Name Description 0x00-0xBF Reserved Reserved 0xC0-0xFF Custom Us... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.6 MAC Payload | The MAC payload shall contain the encrypted Link Layer Protocol Data Unit (LPDU). It may have a variable size between 1 and 245 bytes. The maximum variable size is reduced accordingly when the full addressing mode and/or MPF field is used or control segments are included in the transmission. If the attach flag bit in t... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.2.7 SIGN | The SIGN field shall contain a 32 bit Cypher-based Message Authentication Code (CMAC) according to clause 6.3.2.6.2 cryptographically signing the content of the MAC data unit. ETSI ETSI TS 103 357 V1.1.1 (2018-06) 47 |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3 MAC Formats in DL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3.1 MAC Protocol Data Unit (MPDU) | If the LTN system using the TS-UNB protocol is operated in the fixed MAC mode, the downlink MPDU format according to Table 6-18 shall be used. Table 6-18: Downlink MPDU Format of fixed MAC mode Bytes: 1 0/1 Variable (1 to 250) 4 MAC Header MPF MAC Payload SIGN |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3.2 MAC Header | The MAC Header shall be a one byte wide bit field signalling different MAC options for the packet. The MAC Header in downlink direction supports a subset of the uplink MAC Header flags. The MAC Header shall be formatted according to Table 6-19. Table 6-19: Downlink MAC Header Format Bit Function Description 0 MAC versi... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3.3 MAC Payload Format (MPF) | The MPF field shall be present if the MPF field of the MAC header is set to 1. The MPF field may be used to indicate the format of the MAC Payload according to Table 6-17 in clause 6.3.2.2.5. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3.4 MAC Payload | The MAC Payload shall contain the encrypted Link Layer Protocol Data Unit (LPDU). It shall have a variable size between 1 and 250 bytes. The maximum size is reduced accordingly when control segments are included in the packet. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.3.5 SIGN | The SIGN field shall contain a 32 bit Cypher-based Message Authentication Code (CMAC) according to clause 6.3.2.6.2 cryptographically signing the content of the MAC data unit. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4 MAC Functions in UL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4.1 Addressing | Every end-point shall uniquely be identified by a lifetime assigned IEEE EUI64 [6]. Additionally an end-point may be associated with a 16 bit, non-unique, short address via the attachment procedure, as described in clause 6.2.3.1. Packets using the full addressing mode shall explicitly include the EUI64 of the correspo... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4.2 Packet Counter | A 32 bit packet counter shall be used to the track the number of transmitted uplink packets in the end-point and the base station. Table 6-20: Packet Counter Format Bit 0 to 7 Bit 8 to 31 Extended Counter value MPDUCNT value (transmitted) Packet Counter (32 Bit) Every uplink packet except attachment packets shall conta... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4.3 Attachment Counter | A 24 bit attachment counter shall be used in the end-point and service centre to count the number of attachment procedures initiated by the end-point. The attach counter shall be incremented after each attach request message by the end-point. The MPDUCNT field of the MPDU shall be filled with the attach counter in atta... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4.4 Payload Encryption | The MAC payload and the optional MPF field in uplink shall be encrypted according to clause 6.3.2.6.1. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.4.5 Authentication | A CMAC according to clause 6.3.2.6.2 shall be used to authenticate the MAC payload in uplink. The CMAC shall be generated over the MPDU fields MAC Header, Address, MPDUCNT, the optional MPF field, if available and the MAC payload after encrypting the MAC payload as well as the optional MPF field (encrypt then MAC). It ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.5 MAC Functions in DL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.5.1 Addressing | Downlink addressing is done implicitly via the time of transmission and the CMAC included in the Sync field of the downlink core frame. The end-point shall only accept transmissions at the defined time offset ∆ after the previous uplink transmission, as described in clause 6.3.2.7.1. The comparison of the contained ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.5.2 Packet Counter | The packet counter of the associated uplink shall be implicitly used as packet counter in the downlink transmission. If the associated uplink uses the attach format and therefore includes the attach counter instead of the packet counter, the packet counter for encryption and signature generation shall be assumed 0. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.5.3 Payload Encryption | The MAC payload and the optional MPF field in downlink shall be encrypted according to clause 6.3.2.6.1. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.5.4 Authentication | A CMAC according to clause 6.3.2.6.2 shall be used to authenticate the MAC payload in downlink. The CMAC shall be generated over the MPDU fields MAC Header, the optional MPF field if available and the MAC payload after encrypting the MAC payload as well as the optional MPF field (encrypt then MAC) and shall be preceded... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.6 Common MAC function | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.6.1 Encryption | The MAC layer handles the network level encryption of the MAC payload. The network level encryption shall be used for all packets except the attach request packet. Network level cryptography shall be based on the 128 bit network key provided through the attachment procedure described in clause 6.2.3.1 and the AES128 al... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.6.2 CMAC generation | A cypher-based Message Authentication Code (CMAC) [3] and [i.6] shall be used to verify the integrity and authenticity of an uplink or downlink packet. AES128 shall be employed as the block cipher algorithm required within the CMAC procedure. The network key provided through the attachment procedure (see clause 6.2.3.1... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.7 MAC Procedures | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.7.1 Scheduling | In downlink data shall only be transmitted after the reception of an uplink transmission. Hence every downlink transmission needs to be preceded by an uplink transmission of an end-point. After sending an uplink packet to the base station, an end-point may open a downlink window for the reception of a downlink transmis... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.2.7.2 Transmission Acknowledgment | 6.3.2.7.2.1 Uplink Message ACK If an end-point requires a downlink response from the base station after its uplink communication, e.g. for acknowledgment of the uplink message, it shall set the response flag in the MAC header field. Due to the limited duty cycle in the base station transmission, the base station may re... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.3 Variable MAC mode | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.3.1 Overview | A LTN system using TS-UNB protocol can run user specific MAC/LINK layer, when operated in the variable MAC mode. If a LTN system using TS-UNB protocol is operated in variable MAC mode the MMODE field in the PHY layer shall be set according to clause 6.4.2.3.6. ETSI ETSI TS 103 357 V1.1.1 (2018-06) 52 |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.3.2 MPDU Format | In the variable MAC mode the MPDU format in uplink and downlink shall be formatted according to Table 6-26. Table 6-26: Uplink MPDU Format of variable MAC mode Bytes: 1 Variable (1 to 254) MAC-TYPE U-MPDU (Variable MAC according MAC Type) A custom specific MAC Payload field U-MPDU shall be preceded by a MAC-TYPE field ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4 MAC Types | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4.1 MAC type WMBUS | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4.1.1 Overview | If the variable MAC mode with MAC type WMBUS is used, the same MAC/LINK layer as for the fixed MAC mode described in clause 6.3 shall be used with adaptations according to the following clauses. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4.1.2 MAC Formats | 6.3.4.1.2.1 Uplink The uplink U-MPDU format shall be formatted according to Table 6-28. Table 6-28: Uplink U-MPDU Format of variable MAC with MAC type WMBUS Bytes: 1 8 3 1 0/1 Variable (1 to 238) 4 MAC Header WMBUS Address MPDUCNT CI MPF MAC Payload SIGN An 8-Byte WMBUS Addressing shall be used instead of EUI64 as show... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4.1.3 MAC functions | The MAC functions according to clauses 6.3.2.4 and 6.3.2.5 shall be used. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.3.4.1.4 MAC procedures | The MAC procedures according to clause 6.3.2.7 shall be used. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4 PHY Layer | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.1 PHY Overview | In TS-UNB, the radio transmission of a packet (=radio frame) is split into several radio-bursts, which are distributed over time and frequency within the radio frame. For generation of the physical layer output the following processing blocks according to Figure 6-12 are necessary in the end-point (uplink transmission)... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2 PHY Formats in UL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.1 Radio-burst | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.1.1 Burst Data Unit (BDU) | The uplink transmission consists of several radio-bursts. Each radio-burst shall consist of one 12 bit long pilot sequence PS field and two accompanying 12 bit long data fields DATA according to Table 6-30. Table 6-30: Uplink Burst Data Unit format Bits: 0-11 12-23 24-35 DATA PS DATA A 32 byte long synchronization sequ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.1.2 Sync-burst Data Unit (SBDU) | For easier synchronization in the receiver (e.g. for low complexity receivers) an optional synchronization radio-burst may be used before the core frame. The synchronization burst data unit shall consist of fields according to Table 6-31. ETSI ETSI TS 103 357 V1.1.1 (2018-06) 54 Table 6-31: Uplink Sync-Burst Data Unit ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.2 Radio Frame | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.2.1 Overview | The uplink transmission shall consist of a core frame and shall comprise an additional extension frame, if the PHY payload length exceeds 186 bits. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.2.2 Core frame | The uplink core frame shall consist of 24 radio-bursts. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.2.3 Extension frame | The uplink extension frame structure shall be derived from the information of the core frame according to clause 6.4.7.1.6.2. For each additional byte in the PHY payload, the frame shall be extended by one radio-burst. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3 PHY Payload | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.1 Introduction | The PHY Payload in uplink shall consist of the following fields. Table 6-33: UL-ULP PHY Payload Bits: 8 8 8 Variable (160 to 2 040) 2 Header CRC Payload CRC PSI PSDU MMode PHR ETSI ETSI TS 103 357 V1.1.1 (2018-06) 55 Header CRC, Payload CRC and PSI form the PHY Header (PHR) based on which the radio burst transmission t... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.2 Header CRC | The Header CRC shall be 8 Bit and calculated according to clause 6.4.4.4.1. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.3 Payload CRC | The Payload CRC shall be 8 Bit and calculated according to clause 6.4.4.4.2. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.4 Packet Size Indicator (PSI) | The Packet Size Indicator (PSI) field shall be 8 bit long and shall indicate the length of the PSDU before zero padding in byte. Valid values range from 1 to 245 bytes. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.5 PHY Service Data Unit (PSDU) | The physical layer service data unit (PSDU) may hold a variable length of up to 255 bytes of data. The minimum PSDU length shall be 20 bytes and shall be covered by the core frame. The PSDU shall be filled with the MAC Protocol Data Unit (MPDU). If the MPDU size is below 20 bytes the PSDU shall be filled to 20 bytes by... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.2.3.6 MMode | The 2 bit long field MMODE shall indicate if fixed MAC or variable MAC is used. The MMODE field shall be formatted according to Table 6-34. Table 6-34: MMODE field format Bit Function Description 0/1 MMode 00: Fixed MAC Mode (see clause 6.3) 01: Variable MAC (customer specific MAC/LINK layer see clause 6.3.3) Others: R... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3 PHY Formats in DL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.1 Radio-burst | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.1.1 DL-SB Mode | 6.4.3.1.1.1 Overview In DL-SB Mode, telegram splitting shall not be used. Therefore the PHY payload of one block shall be transmitted in one continuous radio-burst. The length of the radio-burst depends on the length of the PSDU of the PHY payload, which shall be a fixed length of 78 symbols for the core frame and vari... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.1.2 DL-TS Mode | 6.4.3.1.2.1 Burst Data Unit The burst data unit of the downlink transmission in DL-TS Mode shall be formatted according to Table 6-36. Table 6-36: Burst Data Unit format of DL-TS Mode Bits: 0 - 11 12 - 19 20 - 31 32 - 39 40 - 51 DATA_B PS_DA DATA_A PS_DB DATA_C The burst data unit in the downlink shall consist of at le... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.2 Radio frame | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.2.1 Core frame | The core frame is used as authenticated wakeup and acknowledgment of the previous end-point uplink transmission. Every downlink transmission shall consist of a core frame and may be followed by an optional extension frame. The succeeding extension frame shall be indicated in the core frame. The core frame shall consist... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.2.2 Extension frame | The extension frame is an optional transmission frame to transmit user data. The extension frame may contain a maximum of 250 bytes of PSDU data. The PSDU contains the MPDU data with additional zero padding if needed. The extension frame shall be split into blocks of at most 24 bytes of PSDU data per block. If the over... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.3 PHY Payload | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.3.1 Core frame | 6.4.3.3.1.1 Introduction The same core frame PHY Payload format shall be used for DL-SB and DL-TS Mode. The core frame PHY Payload shall have the format according to Table 6-39. Table 6-39: PHY Payload of the DL-TS Core frame Bits: 0-47 48 49-56 57-70 71-72 73 74-77 Sync EFI PSI TSI MMODE Reserved CRC 6.4.3.3.1.2 Sync ... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.3.3.2 Extension frame | The same extension frame PHY payload format shall be used for DL-SB mode and DL-TS mode. The extension frame is sliced in blocks. The PHY payload of a block shall have the format according to Table 6-42. Table 6-42: PHY payload of a DL-TS Extension frame Block Bits: 0-191 192-193 194-201 Block PSDU Reserved CRC The ove... |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.4 PHY Functions in UL | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.4.1 Modulation | A LTN system using TS-UNB protocol shall use MSK Modulation or GMSK Modulation with BT = 1.0 in the uplink. |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.4.2 Symbol mapping | |
baa46c383033a4406946797fe47211ae | 103 357 | 6.4.4.2.1 Overview | The bits of the Burst Data Unit and Sync-burst Data Unit shall be mapped according to the following symbol representation. ETSI ETSI TS 103 357 V1.1.1 (2018-06) 60 Figure 6-13: Symbol mapping for MSK/GMSK with absolute phase The representation shall be repeated after 4 symbols. is the start time of the PHY transmiss... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.