hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.5.3.12 Fragmentation procedure | The fragmentation procedure may be used to transmit application data that exceeds the maximum available MAC payload size in uplink or downlink. The application data size is indicated by the Application Data Size Indicator (ADSI). If fragmentation is used the fragmentation procedure shall cut the transmission data strea... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6 MAC Layer | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.1 Overview of MAC layer and MAC formats | 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 cryptography and authentication. Figure 4-14 (resp. Figure 4-15) illustrates the MAC layer exchanges with upper Link layer and lower PHY layer in a... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2 Fixed-MAC mode formats in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.1 Overview | Figure 4-14: MAC layer interfaces with adjacent layers on the Base Station In RX direction the MAC layer accepts the MPDU and associated meta information from the PHY layer. The meta information comprises the time of reception, signal quality information and a set of RX parameters. After address resolution and decrypti... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.2 UL-MPDU format description | If the LTN system using the TS-UNB protocol is operated in the fixed MAC mode, the uplink MPDU format according to Table 4-47 shall be used. Table 4-47: Uplink MPDU Format of fixed MAC mode Field length (in bytes) 1 2 or 8 3 0 or 1 0 to 245 4 Field content MAC Header Address MPDUCNT MPF MAC payload SIGN |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.3 MAC Header field in UL | The MAC header shall be a 1-byte wide field signalling different MAC options for the packet. It shall be formatted according to Table 4-48. Table 4-48: Uplink MAC Header Format Serialization order Function Description #0 MAC version 0: Initial Version 1: Reserved #1 MPF flag 0: No MPF field present 1: MPF field present... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.4 Address field in UL | 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. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.5 MPDUCNT field in UL | The MPDUCNT field shall contain a 24-bit counter value according to clause 4.6.5.2. If the attach flag bit in the header is set, the attachment counter according to clause 4.6.5.3 is used instead of the packet counter. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.6 MPF field in UL | The MPF field shall be present if the MPF flag of the MAC header is set to one. The MPF field may be used to indicate the format of the MAC Payload. The MPF values shall be used according to Table 4-49. Table 4-49: MAC Payload Formats MPF field value MPF name Description 0x00 Default No MAC payload format specified 0x0... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.7 MAC Payload field in UL | 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... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.2.8 SIGN field in UL | The SIGN field shall contain a 32-bit Cypher-based Message Authentication Code (CMAC) according to clause 4.6.5.5 cryptographically signing the content of the MAC data unit. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3 Fixed-MAC mode formats in DL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.1 DL_MPDU format description | If the LTN system using the TS-UNB protocol is operated in the fixed MAC mode, the downlink MPDU format according to Table 4-50 shall be used for data transmission. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 49 Table 4-50: Downlink MPDU Format of fixed MAC mode Field length (in bytes) 1 0 or 1 1 to 250 4 Field content MAC... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.2 MAC Header field in DL | The MAC Header shall be a 1-byte 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 4-51. Table 4-51: Downlink MAC Header Format Serialization order Function Description #0 MAC... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.3 MPF field in DL | The MPF field shall be present if the MPF Flag 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 4-49 in clause 4.6.2.6. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.4 MAC Payload field in DL | 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. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.5 SIGN field in DL | The SIGN field shall contain a 32-bit Cypher-based Message Authentication Code (CMAC) according to clause 4.6.6.6 cryptographically signing the content of the MAC data unit. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6 DLB mode MPDU formats | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.1 Introduction | At MAC level, the DLB transmission mode implements five types of PDUs: • A Sync frame format for standalone resynchronization. • A beacon core frame format in case of single-stage pre-addressing. • A beacon core frame format in case of two-stage pre-addressing. • A beacon extension frame format. ETSI ETSI TS 103 357-2 ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.2 Sync Frame MPDU format | The sync frame MPDU shall contain three fields, as detailed in Table 4-52. Table 4-52: Sync Frame MPDU format Field length (in bits) 16 24 8 Field content BS-EUI [48-63] BCCNT [0-23] Sync CMAC BS-EUI [48-63] 16 least significant bit of Base station EUI BCCNT [0-23] 24 most significant bits of Beacon Counter value Sync ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.3 Single-stage Beacon Core MPDU format | This beacon core MPDU format shall be used for signalling the transmission of one DLB_Data frame, in single-stage pre-addressing (i.e. with no beacon extension frame). It shall be formatted as in Table 4-53. Table 4-53: Single-stage beacon core MPDU format Field length (in bits) 24 2 Field content Pre-addressing Info S... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.4 Two-stage Beacon Core MPDU format | This beacon core MPDU format shall be used for signalling the transmission of DLB_Data frames, with two-stage pre- addressing (i.e. with beacon extensions). It shall be formatted according to Table 4-54. Table 4-54: Two-stage beacon core MPDU format Field length (in bits) 2 5 1 16 2 Field content BE_N Reserved IA Mask ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.5 Beacon Extension MPDU format | The Beacon Extension MPDU shall consist of eight fields. Each field shall contain, in order, the pre-addressing info for the eight DLB_Data frames, that may follow a Beacon Extension frame. Figure 4-16 illustrates the BE_MPDU format. A pre-addressing info in a BE_MPDU shall be formatted according to Table 4-62. Figure ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.6.6 DLB_Data frame MPDU format | The format of a DLB_Data frame MPDU shall be equivalent to the format of a DL_MPDU, in fixed MAC mode (see clause 4.6.3.1), but a different encryption and authentication procedures shall be used (see clauses 4.6.6.5.2 and 4.6.6.6.2). |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.7 DLC mode MPDU formats | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.3.7.1 DLC frame MPDU format | The format of a DLC frame MPDU shall be equivalent to the format of a DL_MPDU, in fixed MAC mode (see clause 4.6.3.1), but a different encryption and authentication procedures shall be used (see clauses 4.6.6.5.3 and 4.6.6.6.3). ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 52 |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4 Variable MAC mode formats | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.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 4.7.1.2.6. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.2 MPDU format in variable MAC mode | In the variable MAC mode, the MPDU format in uplink and downlink shall be formatted according to Table 4-56. Table 4-56: Uplink and downlink MPDU Format of variable MAC mode Field length (in bytes) 1 1 to 254 Field content MAC-TYPE U-MPDU (Variable MAC according to MAC-TYPE) A custom specific MAC Payload field U-MPDU s... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3 Details on Variable MAC-TYPE 0x00 (WMBUS) | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3.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 4.6 shall be used with adaptations according to the following clauses. As variable MAC-TYPE 0x00 is deprecated; it should not be used in new design. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3.2 MAC format in uplink (WMBUS) | The uplink U-MPDU format shall be formatted according to Table 4-58. Table 4-58: Uplink U-MPDU Format of variable MAC with MAC-TYPE WMBUS Field length (in bytes) 1 8 3 1 0 or 1 1 to 238 4 Field content MAC Header WMBUS Address MPDUCNT CI MPF MAC Payload SIGN An 8-Byte WMBUS Addressing shall be used instead of EUI64 as ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3.3 MAC format in downlink (WMBUS) | The same U-MPDU format as in fixed MAC mode downlink MPDU shall be used. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3.4 MAC functions (WMBUS) | The MAC functions according to clauses 4.6.4 and 4.6.6 shall be used. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.4.3.5 MAC procedures (WMBUS) | The MAC procedures according to clause 4.6.8 shall be used. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5 Fixed-MAC functions in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5.1 Addressing function in UL | 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 4.5.3.1. Packets using the full addressing mode shall explicitly include the EUI64 of the corresp... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5.2 Packet Counter function in UL | A 32-bit packet counter shall be used to track the number of transmitted uplink packets in the end-point and the base station. The packet counter shall be formatted as specified in Table 4-60. Table 4-60: Packet Counter Format Field length (in bytes) 8 24 Field Name Extended Counter MPDUCNT Comment 8 most significant b... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5.3 Attachment Counter function in UL | 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... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5.4 MAC Payload encryption function in UL | The MAC payload and the optional MPF field in uplink shall be encrypted according to clause 4.6.7.1. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.5.5 Authentication function in UL | Uplink MPDU is authenticated with a 32-bit SIGN field. The SIGN field shall be the four most significant bytes of the result of a CMAC algorithm (see clause 4.6.7.2). The CMAC algorithm shall be generated over the following fields (see Table 4-61): CMAC Initialization Vector (CIV), MAC Header, Address, MPDUCNT, the opt... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6 Fixed-MAC functions in DL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.1 Addressing function in a DLA transmission | In DLA mode, 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 4.6.8.1. The comparison of the containe... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.2 Addressing function in a DLB transmission | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.2.1 Pre-addressing Info for DLB_Data frame | In a DLB transmission, addressing is done via pre-addressing info, inserted either in the beacon core frame as single- stage addressing (see clause 4.6.3.6.3) or in the beacon extension frame(s) (see clause 4.6.3.6.5) with a preceding beacon core frame containing information about beacon extension frame(s) (see clause ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.2.2 Complete addressing for DLB_Data frames | The complete addressing shall use 32-bit implicit addressing via the CMAC. Hence DLB packets require the end-point identity to be derived from the short address in the beacon core or beacon extension pre-addressing info and the cryptographic signature contained in the CMAC of the DLB_Data frame MPDU. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.2.3 Implicit addressing for DLB_Data frames | In a DLB frame with two or more beacon extension frames (i.e. two or more data regions), the implicit addressing may be used to distribute DLB_Data frames between data regions. When IA flag is set (i.e. IA=1), DLB_Data frame shall be transmitted in the data region which number is, as follows: ℎ ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.3 Addressing function in a DLC transmission | In a DLC transmission, pre-addressing is done via the MAC Pre-Addressing Info Field (MPAI) inserted before the MPDU. The MPAI field shall be formatted according to Table 4-62 (pre-addressing in DLB). The complete addressing shall use 32-bit implicit addressing via the CMAC. Hence DLC packets require the end-point ident... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.4 Packet Counter function in DLA | 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 implicitly def... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.5 MAC payload encryption function in DL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.5.1 MAC Payload encryption function in DLA | The MAC payload and the optional MPF field in class A downlink shall be encrypted according to clause 4.6.7.1. The network key shall be used as cryptographic key for the generation of the encryption Initialization vector. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.5.2 MAC payload encryption function in DLB | The MAC payload and the optional MPF field in class B downlink shall be encrypted according to clause 4.6.7.1. The beacon counter BCCNT shall be used as encryption counter. For a data frame, the frame counter shall be the potential data frame number within the DLB frame, considering the 8 possible data packets in all t... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.5.3 MAC payload encryption function in DLC | The MAC payload and the optional MPF field in class C downlink shall be encrypted according to clause 4.6.7.1. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 57 |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.5.4 MPAI encryption function in DLC | The MPAI field of the DLC core frame shall be encrypted separately according to clause 4.6.7.1. For the encryption the data direction flag, DL mode flag, DLC mode flag and beacon flag are set in the initialization vector and the system key is used. The beacon counter BCCNT shall be used as encryption counter. Block cou... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.6 Authentication function in DL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.6.1 Authentication function in DLA | Downlink MPDU is authenticated with a 32-bit SIGN field. The SIGN field shall be the four most significant bytes of the result of a CMAC algorithm (see clause 4.6.7.2). The CMAC algorithm shall be generated over the following fields (see Table 4-64): CMAC Initialization Vector (CIV), MAC Header, the optional MPF field ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.6.2 Authentication function in DLB | MPDU in DLB transmission is authenticated with a 32-bit SIGN field. The SIGN field shall be the four most significant bytes of the result of a CMAC algorithm (see clause 4.6.7.2). The CMAC algorithm shall be generated over the same fields as in DLA (see Table 4-64). The CMAC initialization vector according to Table 4-6... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.6.3 Authentication function in DLC | MPDU in DLC transmission is authenticated with a 32-bit SIGN field. The SIGN field shall be the four most significant bytes of the result of a CMAC algorithm (see clause 4.6.7.2). The CMAC algorithm shall be generated over the same fields as in DLA (see Table 4-64). The CMAC initialization vector according to Table 4-6... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.6.6.4 Authentication function for Sync Frame | The sync frame MPDU (see clause 4.6.3.6.2) contains a CMAC to authenticate the class B parameters of the beacon which the sync frame belongs to. In this case, the authentication function shall use a CMAC computation based on the initialization vector as specified in Table 4-65 and the system key. The MSB of the CMAC re... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.7 Common Fixed-MAC functions | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.7.1 Network level encryption function | The MAC layer handles the network level encryption of the MAC payload. The network level encryption shall be used for all packets, except for the Attach_Request packet and the Attach_Request_IPv6 packet. Network level cryptography shall be based on the 128-bit network key provided through the attachment procedure descr... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.7.2 CMAC generation function | 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 4.5.3.1... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8 MAC procedures | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.1 Introduction to MAC procedure section | The MAC procedures, that are performed between an end-point and a base station, are, as follows: • EP-triggered downlink transmission (i.e. DLA). • Uplink message acknowledgement. • Downlink message acknowledgement. • EP synchronization to DLB frames of a base station, for DLB and DLC communication. NOTE: Procedures an... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.2 EP-triggered downlink transmission procedure (DLA) | Downlink data in DLA 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 tran... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.3 Uplink message acknowledgement procedure | 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 refuse the downlink transmission. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.4 Downlink message acknowledgment procedure (in DLA mode) | If a base station expects an acknowledgment of a message transmitted in DLA mode, the base station shall set the response flag of the MAC header field in downlink. The end-point shall then send a separate uplink transmission to acknowledge the reception of the preceding downlink transmission. NOTE 1: An EP may send a D... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.5.1 Introduction | For scheduled downlink transmission, an end-point is synchronized to a base station to receive data at a point in time and frequency, scheduled by the base station. The base station sends a periodic beacon signal to span a time window in between called beacon period divided into discrete time slots called physical reso... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.5.2 Time synchronization to DLB mode | Before switching to DLB mode, an end-point shall receive, via DLA mode from the base station, a Sync Info control segment with time synchronization parameters (see clause 4.5.2.2.13). The base station may send this Sync Info control segment either after an Attach Accept control segment, or in response to a Sync Request... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.5.3 Frequency offset correction procedure | The frequency offset correction procedure is used to compensate inaccuracies of local oscillators in base stations and end-points. It is performed before switching to DLB mode and uses signalling from the base station to the end-point. The frequency offset correction procedure shall be, as follows: • The EP may send a ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.6.8.5.4 Stand-alone Resynchronization procedure | For easier synchronization or for resynchronization after a beacon was not correctly received, an optional sync frame (staircase) may be transmitted by the base station prior to each beacon core frame (see Figure 4-21) with only three radio-bursts distributed over a subset of neighbouring carriers to limit the occupied... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7 PHY Layer | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1 PHY formats in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.1 Overview in uplink | In TS-UNB, the transmission of a message is split into several radio-bursts, which are distributed over time and frequency to form a radio frame. Figure 4-22 illustrates the various processing steps that are implemented in the PHY layer of an end-point, in order to get the radio-bursts out of a message MPDU. Figure 4-2... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2 PHY Payload format in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.1 Introduction | The PHY Payload in uplink shall consist of the five fields, as specified in Table 4-70. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 65 Table 4-70: PHY_Payload format in uplink Field length (in bits) 8 8 8 160 to 2040 2 Field content Header_CRC Payload_CRC PSI PSDU MMode NOTE: The three fields Header_CRC, Payload_CRC, and P... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.2 Header_CRC field in UL | The Header_CRC shall be 8 bits and calculated according to clause 4.7.3.4.1. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.3 Payload CRC field in UL | The Payload CRC shall be 8 bits and calculated according to clause 4.7.3.4.2. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.4 Packet Size Indicator (PSI) in UL | The Packet Size Indicator (PSI) field shall be 8-bit long and shall indicate the length in bytes of the MPDU (i.e. PSDU length without zero padding). Valid values range from 1 to 255 bytes. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.5 PHY Service Data Unit (PSDU) in UL | 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 up to 20 byte... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.2.6 MMode field in UL | 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 4-71. Table 4-71: MMODE field format MMode value Description 0b00 Fixed MAC Mode (see clause 4.6.2) 0b01 Variable MAC Mode (see clause 4.6.4) 0b10 Reserved 0b11 Reserved |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.3 Radio Frame formats in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.3.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. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.3.2 Core Frame format in UL | The uplink core frame shall consist of 24 radio-bursts, transmitting the minimum PHY payload length of 186 bits. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 66 |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.3.3 Extension Frame format in UL | The uplink extension frame structure shall be derived from the information of the core frame according to clause 4.7.6.1.7. For each additional byte in the PHY payload, the frame shall be extended by one radio-burst. |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.4 Radio-burst formats in UL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.4.1 Burst Data Unit (BDU) in UL | 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_A and DATA_B according to Table 4-72. Table 4-72: Uplink Burst Data Unit format Field length (in bits) 12 12 12 Field content DATA_A PS DA... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.1.4.2 Sync Burst Data Unit (SBDU) in UL | 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 4-73. Table 4-73: Uplink Sync-Burst Data Unit format Field length (in bits) 12 8 1 3 8 ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2 PHY formats in DL | |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.1 Overview in downlink | In TS-UNB, the transmission of a message in downlink is split into several radio-bursts, which are distributed over time and frequency. Radio-bursts are combined to a block, one or more blocks are combined to a radio frame. In the TS-UNB protocol stack, the downlink PHY layer contains two main steps: • The generation o... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.2 PHY Payload format in DL | The PHY Payload format in downlink shall consist of several fields, as illustrated in Figure 4-25: • a PHY header; • PSDU fields (one for DLA and DLC, one or several for DLB), each PSDU field containing a downlink MPDU to be transmitted. Figure 4-25: PHY_Payload format in downlink transmission The PHY header shall be b... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.3 DLA Core (DLAC) block format (no timing flexibility) | When timing flexibility is not used, the DLA core block format shall consist of seven fields, as detailed in Table 4-75 Table 4-75: DLA core block format (no timing flexibility) Field length (in bits) 48 1 8 14 2 1 4 Field content Sync EFI PSI TSI MMode FTM CRC NOTE: The five fields EFI, PSI, TSI, MMode, and FTM togeth... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.4 DLA Core (DLAC) block format (timing flexibility activated) | When timing flexibility is activated, the DLA core block format shall consist of ten fields, as detailed in Table 4-77. Table 4-77: DLA core block format (timing flexibility activated) Field length (in bits) 48 1 8 5 4 3 2 2 1 4 Field content Sync EFI PSI TSI_F TDN_F THB Reserved MMode FTM CRC NOTE: The eight fields EF... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.5 DLA Core (DLAC) block format for HDR burst structure | For HDR burst structure the DLA Core block format shall be formatted as detailed in Table 4-80. This block format shall be only used in fixed MAC mode. Table 4-80: DLA core block format for high data rate burst structure Field length (in bits) 48 1 8 14 2 1 20 8 Field content SYNC EFI PSI TSI MMode FTM Reserved CRC NOT... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.6 Data Extension block format for HDR burst structure | In the case of HDR burst structure, the Data Extension (DE) block format shall consist of four fields, as detailed in Table 4-81. Table 4-81: Format of a Data Extension block Field length (in bits) 40…160 4 2 8 Field content Block_SDU Custom Block Info Reserved Block_CRC Block_SDU A variable size field that shall conta... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.7 DLB Sync frame (staircase) format | For easier synchronization or resynchronization after a not-received beacon, an optional DLB Sync frame (staircase) may be transmitted prior to each beacon core frame. The DLB Sync frame shall consist of three radio-bursts, with no data (i.e. pure pilot sequences) followed by an optional DLB Sync data frame. Each radio... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.8 DLB Beacon Core (BC) block format | The Beacon core block format shall consist of three fields, as detailed in Table 4-83. Table 4-83: Beacon core block format Field length (in bits) 48 26 4 Field content BC_Sync BC_MPDU BC_CRC BC_Sync a 48-bit field that shall contain the 48 most significant bits of a CMAC computed according to clause 4.6.7.2 with the i... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.9 DLB Beacon Extension (BE) block format | The Beacon extension block format shall consist of three fields, as detailed in Table 4-84. Table 4-84: Beacon extension block format Field length (in bits) 192 2 8 Field content BE_MPDU Reserved BE_CRC BE_MPDU A 192-bit field that shall be loaded with a BE_MPDU (see clause 4.6.3.6.5) Reserved A 2-bit field that shall ... |
e0bec777474cb75ac0ad394ec0a20d10 | 103 357-2 | 4.7.2.10 Data Extension block format | When present in DLA, DLB, or DLC transmission mode, the Data extension block format shall consist of three fields, as detailed in Table 4-85. ETSI ETSI TS 103 357-2 V2.1.1 (2024-06) 74 Table 4-85: Format of a Data Extension block (DE_Block) Field length (in bits) 56…192 2 8 Field content Block_SDU Reserved Block_CRC Bl... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.