hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.1 Data PDU | The data PDU structure for DLC Service Type 1, 2 and 3 is presented in Figure 5.3.3.1-1 for a complete SDU. A data PDU for service type 1 and 3 with a segmentation offset field is presented in Figure 5.3.3.1-2. When the IE Type is set to 0010 the DLC SDU contains a routing header as defined in clause 5.3.4. When the IE... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.2 DLC Timers configuration Control IE | The DLC Timers configuration Control IE structure for configuring a DLC entity operating in DLC Service Types 1, 2 or 3 is presented in Figure 5.3.3.2-1. The field coding of the IE is presented in Table 5.3.3.2-2. DLC_SDU_lifetime_timer 0 1 2 3 4 5 6 7 IE Type Reserved Figure 5.3.3.2-1: DLC Timer configuration PDU Tabl... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.3 DLC Extension Header | The DLC Extension Header structure is presented in Figure 5.3.3.3-1. The DLC Ext field coding is presented in Table 5.3.3.3-1 and the Extension IE Type field coding in Table 5.3.3.3-2. The Data field contents depends on the Extension IE type coding. 0 1 2 3 4 5 6 7 Extension IE Type Length Data DLC Ext Figure 5.3.3.3-1... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.4 Next Hop address IE | The Next Hop address IE contains the Long RD ID of the next RD as presented in Figure 5.3.3.4-1. Next hop address 0 1 2 3 4 5 6 7 Next hop address Next hop address Next hop address Figure 5.3.3.4-1: Next hop address Next Hop Address IEs are set in front of the Routing Header, each preceded by the DLC Extension Header a... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.5 Route Register IE | Route Register IE is used by RD to inform its location in cluster tree topology. Route Register IE contains the Source Routing ID, as depicted in Figure 5.3.3.5-1. An RD determines the Source Routing ID value based on Source Routing IE received from an RD in FT mode that the RD is associated with. Source Routing ID 0 1... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.3.6 Route Error IE | Route Error IE is used to indicate routing error. Route Error fields are depicted in Figure 5.3.3.6-1 and the fields are described in Table 5.3.3.6-1. Error Reason 0 1 2 3 4 5 6 7 Invalid Next Hop Address Invalid Next Hop Address Invalid Next Hop Address Invalid Next Hop Address Figure 5.3.3.6-1: DLC Route error contro... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 5.3.4 Routing header | An optional routing header is added at the beginning of each SDU when routing is used. The routing header format is depicted in Figure 5.3.4-1. The first two octets are a routing bitmap field where each bit has a specific meaning as defined in Table 5.3.4-1. After the bit map field, a 32-bit source and destination addr... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6 Convergence Layer Procedures and Data Units | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.1 General | A Convergence layer entity needs to be created for each peer CVG entity. Each CVG entity handles one or more parallel running flows, following the CVG procedures and using the CVG data units. ETSI ETSI TS 103 636-5 V2.2.1 (2026-01) 34 Release 2 |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2 CVG Procedures | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.1 General | The Convergence layer specifies a Transparent procedure, see clause 6.2.3, an Endpoint multiplexing procedure, see clause 6.2.4, a set of transmission procedures, see clauses 6.2.5 to 6.2.12 and clause 6.2.14, and security procedures, see clause 6.2.13. The transmission procedures are arranged as CVG service types, see... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2 CVG Service types | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.1 General | The CVG layer's service types are related to the CVG procedures as defined in Table 6.2.2.1-1. The use of CVG Security, Multiplexing, Duplicate removal and Delivery order procedures are independent of the CVG service type. For service type 0, the SDU is transported using the Data Transparent IE, see clause 6.3.6. For s... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.2 CVG Service type 0 procedures (transparent) | Service type 0 applies only the transparent procedure as defined in clause 6.2.3. |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.3 CVG Service type 1 procedures (sequence numbering) | Service type 1 applies the CVG layer sequence numbering only. When transmitting, i.e. the CVG entity receives an SDU from a higher entity, the CVG entity shall: • Use the transmission and segmentation procedure as defined in clause 6.2.7. NOTE: As the transmitting CVG does not use segmentation, the procedure is used on... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.4 CVG Service type 2 procedures (segmentation & reassembly) | Service type 2 applies the CVG layer segmentation and reassembly procedure. When transmitting, i.e. the CVG entity receives an SDU from a higher entity, the CVG entity shall: • Use the transmission and segmentation procedure as defined in clause 6.2.7. When the CVG entity receives a CVG PDU from a lower entity, the CVG... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.5 CVG Service type 3 procedures (FC) | Service type 3 applies the CVG layer segmentation and reassembly, flow control and lifetime procedures. In addition, it uses the ARQ procedure in a limited manner to support the flow control. The service type 3 is based on a transmission window with a selectable maximum window size (WMAX) controlled by ACK only message... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.2.6 CVG Service type 4 procedures (FC and ARQ) | Service type 4 applies segmentation & reassembly, flow control, lifetime control and ARQ. Service type 4 is based on a transmission window with a selectable maximum window size (WMAX) controlled by ACK and NACK messages (ARQ Feedback IE) combined with a lifetime timer. It is able to provide reliable transmissions and e... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.3 Transparent procedure | The Transparent procedure does not apply CVG services, but only carries SDUs using the Data Transparent IE, see clause 6.3.6. The transmitting CVG shall: • set the CVG header fields using format 1 coding for the IEs, see clause 6.3.2: - set the CVG Ext field: if more than one Data Transparent IEs are included within ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.4 Multiplexing procedures | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.4.1 General | The Convergence layer provides identification and multiplexing of the flows of higher layer frameworks using different CVG level multiplexing procedures: Endpoint multiplexing and Mux tag multiplexing. ETSI ETSI TS 103 636-5 V2.2.1 (2026-01) 37 Release 2 |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.4.2 Endpoint Multiplexing procedure | Endpoint multiplexing is based on assigning values of 2-octet EP mux field, for the flows see clause A.1, and is indicated using the EP mux IE or the EP mux field of the Data EP IE. The transmitting CVG entity shall: • set the CVG header fields using format 1 coding for the IEs, see clause 6.3.2: - set the CVG Ext fiel... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.4.3 Mux Tag multiplexing procedure | The Mux tag multiplexing procedure is based on the usage of a 3-bit Mux Tag field. The transmitting CVG entity shall: • set the CVG header fields using format 2 coding for the IEs, see clause 6.3.2: - set the CVG Ext field: if more than one Data IE is included within a CVG PDU, the 8 or 16-bit length field shall be u... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.5 Duplicate Removal procedure | The receiving CVG entity examines the Data IE, see clause 6.3.4, or Data EP IE, see clause 6.3.5, and: • If the Sequence number of a complete SDU, or in case of a segment the Sequence number and Segmentation offset fields, indicate that it was already received within the current cycle of the sequence number, the CVG en... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.6 Delivery Order procedures | Delivery order procedures mean the arrangement of SDUs at the receiving CVG, before forwarding them to the next higher entity. In case segmentation is in use, only the completely reassembled SDUs are delivered. Within the default procedure "as received delivery", the receiving CVG shall: • Deliver the complete SDUs in ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.7 Transmission and Segmentation procedure | When the CVG considers an SDU for transmission, it shall use either the Data IE or Data EP IE as following: • if CVG security is in use: - follow clause 6.2.13 and the selected security mode procedure; NOTE 1: Security mode 1 ciphering and the Transmission and Segmentation procedures use the same CVG sequence number fo... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.8 Reception and Reassembly procedure | The receiving CVG entity shall examine the Data IE, see clause 6.3.4 or the Data EP IE, see clause 6.3.5: • if it contains a complete SDU (SI = 00): - pass the SDU to the next higher entity; • else if it contains a segment (SI = 01, 10 or 11): - reassemble the complete SDU or if one or more segments are still missing, ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.9 Flow control procedures | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.9.1 General | Flow Control is used for mitigating the transmission of SDUs at a CVG flow. Both the transmitting and receiving CVG maintain a Flow Control window. The maximum size (WMAX) of the window is set within the TX Services configuration, see clause 6.2.12 or as a system configuration. The transmitter does not move the window ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.9.2 FC transmitting procedures | The transmitting CVG maintains book-keeping for the transmitted, non-expired sequence numbers of the SDUs within the Flow Control window. When a transmitting CVG has not reached the maximum FC window size for a flow, i.e. the marker B - marker A < WMAX, the Flow Control does not affect the transmissions. Marker B is ad... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.9.3 FC receiving procedures | The receiving CVG maintains book-keeping for the non-expired complete SDUs and segments for each CVG flow that uses Flow Control to estimate the progress at the transmitting CVG. The receiving CVG sorts the received SDUs or segments in order by sequence number or by sequence number and segment offset, identifies the em... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.10 Retransmission (ARQ) procedure | The automatic request for repetition (ARQ) function is to verify the reception of transmitted SDUs by the receiving CVG. Upon the feedback from the receiving CVG, the missing SDUs are retransmitted by the transmitting CVG. When the ARQ Feedback IE indicates successful reception of a transmitted SDU, the transmitting CV... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.11 Lifetime control procedure | When a transmitting CVG entity receives a complete SDU or the first segment of an SDU from a higher entity, the CVG entity shall start the CVG_TX_discard_timer for the SDU. If the CVG_TX_discard_timer expires before the SDU is removed due to successful delivery, see clause 6.2.5, the transmitting CVG entity shall remov... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.12 TX Services configuration procedure | The CVG entity sends the TX Services Config IE, see clause 6.3.8, to its peer to request the TX services configuration, i.e. setting the Service Type, Lifetime and Max window size for a new or an existing CVG flow, or to respond to such a configuration request from a peer CVG entity. When using the TX Services Config I... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13 Security procedures | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13.1 General | The CVG layer security is defined in different Security Modes. The procedures for Security mode 1 are defined in clause 6.2.13.2. |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13.2 Security Mode 1 procedures | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13.2.1 General | Security Mode 1 shall use AES-128 for ciphering with integrity protection to provide confidentiality and message authentication as defined in FIPS PUB 197 [3]. One key is used for integrity protection and another key for encryption. Security is handled per CVG flow, i.e. a security entity is established for each flow a... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13.2.2 Integrity protection | The Mode 1 integrity protection of the messages is obtained by using the Message Integrity Code (MIC) that is added to the end of the SDU as shown in Figure 6.2.13.2.2-1. The MIC shall be calculated by using the CMAC (OMAC-1) message authentication algorithm as defined in NIST SP 800-38B [4]. SDU MIC ciphered data unit... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.13.2.3 Ciphering | For Mode 1, the ciphering shall use AES-128 counter mode (CTR) for encryption as defined in FIPS PUB 197 [3]. The Initialization Vector (IV) for the counter is defined in Table 6.2.13.2.3-1. The ciphering uses the CVG sequence number carried in the Data IE or the Data EP IE, see the sequence number usage in clause 6.2.... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.2.14 Flow Status procedures | The receiving CVG may inform the transmitting CVG about possible issues of a flow by sending a Flow Status IE, see clause 6.3.11, the CVG entity shall: • set the Reason field; • pass the Flow Status IE to be transmitted. NOTE: The Flow Status IE may be directed for a CVG flow identified by an Endpoint or Mux Tag, see c... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3 CVG Protocol Data Units | |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.1 General | The CVG specifies a common CVG Header, see clause 6.3.2, and a set of Information Elements (IEs). Multiple IEs may be concatenated within the same CVG PDU. |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.2 CVG Header | The Convergence layer header, either format 1 or format 2 is always present in the beginning of each CVG Information Element (IE). The CVG header begins with the CVG Ext and the MT (Mux Tag) field. The 2-bit CVG Ext indicates the presence of an 8 or 16-bit length field right after the CVG header octet, or no length fie... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.3 EP Mux IE | The EP Mux IE is defined as in Figure 6.3.3-1. Endpoint mux 0 1 2 3 4 5 6 7 CVG header Endpoint mux Figure 6.3.3-1: EP Mux IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not included. The 16-bit Endpoint mux field value allocation is described in Annex A. |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.4 Data IE | The Data IE is defined as in Figure 6.3.4-1. 0 1 2 3 4 5 6 7 CVG Header SI Sequence number SDU length SDU length Sequence number Resv. Payload SLI Segmentation offset Segmentation offset Figure 6.3.4-1: Data IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not inclu... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.5 Data EP IE | The Data EP (EndPoint) IE is defined as in Figure 6.3.5-1. 0 1 2 3 4 5 6 7 CVG header SI Sequence number SDU length SDU length Sequence number Resv. Payload SLI Segmentation offset Segmentation offset Endpoint mux Endpoint mux Figure 6.3.5-1: Data EP IE The CVG header is as defined in clause 6.3.2. The Data EP IE is of... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.6 Data Transparent IE | The Data Transparent IE is defined as in Figure 6.3.6-1. 0 1 2 3 4 5 6 7 CVG Header Data payload Figure 6.3.6-1: Data Transparent IE The CVG header is as defined in clause 6.3.2. The Data Transparent IE is of variable length and the CVG header's length field may be used. ETSI ETSI TS 103 636-5 V2.2.1 (2026-01) 50 Relea... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.7 Security IE | The Security IE is defined as in Figure 6.3.7-1. Key Index Security IV Type 0 1 2 3 4 5 6 7 HPC HPC HPC Resv. HPC CVG header Figure 6.3.7-1: Security IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not included. The 3-bit Key index field indicates the key which is ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.8 TX Services Config IE | The TX Services Config IE is defined as in Figure 6.3.8-1. Service Type Reserved 0 1 2 3 4 5 6 7 CVG header Rq/Rs Max window size Reserved Lifetime Max window size Figure 6.3.8-1: TX Services Config IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not included. The ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.9 ARQ Feedback IE | The ARQ Feedback IE has a default format as in Figure 6.3.9-1, using the CVG Ext field value 00 (no length field) as in Table 6.3.2-1. In case of the other formats, see Figure 6.3.9-2, 6.3.9-3 or 6.3.9-4, a combination of feedback elements is used and the CVG Ext field is set to the value 01, indicating the use of the ... |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.10 ARQ Poll IE | The ARQ Poll IE is as in Figure 6.3.10-1. 0 1 2 3 4 5 6 7 Sequence number Reserved CVG header Sequence number Figure 6.3.10-1: ARQ Poll IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not included. The Sequence number points to the last sent SDU. |
79b1c73c7e4f3f63d8a57e19fffee782 | 103 636-5 | 6.3.11 Flow Status IE | The Flow Status IE is as in Figure 6.3.11-1. 0 1 2 3 4 5 6 7 CVG header Reason Reserved Figure 6.3.11-1: Flow Status IE The CVG header is as defined in clause 6.3.2. The IE size is fixed and CVG header's length field is not included. The Reason field coding is described in Table 6.3.11-1. Table 6.3.11-1: Reason coding ... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 1 Scope | The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Medium Access Control (MAC) layer and interactions between the MAC layer and physical layer and higher layers. |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 2 References | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 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... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 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... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 3 Definition of terms, symbols and abbreviations | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 3.1 Terms | For the purposes of the present document, the following terms apply: Fixed Termination point (FT): operational mode of an RD where the RD initiates, coordinates local radio resources, and provides information on how other RDs may connect and communicate with it operating channel: single continuous part of the radio spe... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: 0x Value in hexadecimals β Fourier transform scaling factor NOTE: As defined in ETSI TS 103 636-3 [3]. μ Subcarrier scaling factor NOTE: As defined in ETSI TS 103 636-3 [3]. RSSI-1 RSSI-1 measurement NOTE: As defined in ETSI TS 103 636-2 [2]. RSSI-2... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 636-1 [i.3] 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 [i.3]. ACK ACKnowledgement BCC BroadCast Control BCCH Br... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4 General | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.1 Introduction | The objective of this clause is to describe the MAC protocol layer architecture, used identities, used transport channels and mapping MAC PDU into physical layer packet. |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2 MAC Architecture | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.1 General | This clause describes a model of the MAC i.e. it does not specify or restrict implementations. ETSI ETSI TS 103 636-4 V2.1.1 (2024-10) 11 Release 2 |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.2 MAC Structure | The overall MAC structure is depicted in Figure 4.2.2-1. MAC provides DTCH and MTCH logical channels for transferring higher layer data. The flow of the higher layer data and MAC internal messages to physical channels is depicted with black solid lines. The grey dashed line corresponds to MAC internal control interface... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.3 Identities | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.3.1 Network ID | The Network ID has a length of 32 bits, and the first 24 MSB bits are used to identify a DECT-2020 network uniquely from other DECT-2020 networks. The 8 LSB bits of the network are selected locally to minimize collision with other networks. The network ID is transmitted periodically in beacon messages as plain text ena... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.3.2 Long Radio Device ID (Long RD ID) | The Long radio device ID has a length of 32 bits, and it identifies a radio device uniquely in a single DECT-2020 network. The coding of the Long RD ID is defined in Table 4.2.3.2-1. An RD obtains the Long RD ID as part of the authentication process over the DECT-2020 NR system or via manual provision or by using other... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.2.3.3 Short Radio Device ID (Short RD ID) | The Short radio device ID has a length of 16 bits, and it identifies a radio device locally in the radio neighbourhood in a DECT-2020 NR network. The coding of the Short RD ID is defined in Table 4.2.3.3-1. The Short RD ID is used in the PHY control field as in transmitter or receiver fields to identify the transmitter... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.3 Service | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.3.1 Services provided to upper layers | The MAC layer provides the following services to upper layers: • data transfer; • radio resource allocation. |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.3.2 Services expected from physical layer | The MAC layer expects the following services from the physical layer: • data transfer services in physical layer packets; • measurements. |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.4 Functions | The MAC layer supports the following control functions in the MAC control entity: • Local Radio Control (LRC): This function is overall in charge of the radio resource in the local coordination area, when the RD coordinates local radio resources, i.e. operates as an FT. • Paging Transmission Control (PTC): This functio... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.5 Channel Structure | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.5.1 Logical and Transport Channels | The MAC layer provides data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels are defined i.e. each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred a... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.5.2 Mapping Physical layer packet | In packet transmissions transport channels are mapped to Physical Data Channels (PDC) carried in a physical layer packet. Additionally, the MAC provides the number of used spatial streams, and the content of the Physical Layer Control Field to the physical layer. The Physical Layer Control Field is mapped to a Physical... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 4.6 Order of transmission and figure numbering conventions | The transmission order is Big endian and left to right: • A list of octets is transmitted 1st octet first. • For each octet, bits are numbered 0 to 7 according to the transmission order. Bit 0 is transmitted first (ascending transmission order). • When bits are numbered in any other MAC structure, they are also numbere... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5 MAC Layer Procedures | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1 Spectrum Management Procedures | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.1 General | An RD shall support the set of cognitive radio spectrum management features, defined in clause 5.1. In each connection between two RDs, one RD is in FT mode and the other RD is in PT mode. The RD in FT mode coordinates local radio resources and provides information on how other RDs may connect and communicate with it, ... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.2 Operating Channel(s) and Subslot(s) selection | When an RD initiates FT mode operation, the RD shall initiate the background scan process for finding the operating channels and subslots, which are fulfilling the operating conditions. If during the background scan the RD detects the same Short RD ID value that it has generated is already used by another RD, the RD sh... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.3 Last Minute Scan | When the variable DECT_PROTECTED is true and the timer dectProTime is not running, the RD shall consider that subslot status is no longer valid for a given slot, which is not in use by the RD. ETSI ETSI TS 103 636-4 V2.1.1 (2024-10) 18 Release 2 The RD shall update the status of a subslot on a given carrier by performi... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.4 Selecting RD for association | When an RD desires to establish a connection with another RD or send data without association, it scans frequency channels to detect network, cluster beacon, and/or joining beacon messages containing desired network ID(s). When an RD desires to initiate a secure authentication procedure it searches Joining Beacon messa... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.5 Beaconing Transmissions | To enable other RDs to identify, measure and initiate association with the RD, an RD in FT mode initiates the transmission of the beacon messages. The identification of the RD and the network is done by the Network ID and the Long RD ID included in the MAC Common header of the MAC PDU carrying a beacon message. There e... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.1.6 Power control | When transmitting broadcast messages, the transmission power of the RD can be configured to the RD, or the RD can independently adjust the used TX power. When transmitting a unicast message, the used TX power shall be the minimum that provides the target BLER of the single transmission of the transmitted MAC PDU on the... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.2 Broadcast Procedure | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.2.1 General | The broadcast procedure provides means for an RD to broadcast messages for different purposes. These purposes are: • broadcasting beacon messages; • broadcasting signalling or application data for all other RDs of the network; or • broadcasting signalling or application data for a multicast group of the network. |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.2.2 Broadcast procedure initialization | An RD may start sending broadcast messages after it has selected operating channel(s) and the timer scanStatusValid is running or it has selected another RD for the association. For initiating broadcast a transmission the RD shall: • if DECT_PROTECTED is TRUE and dectProTime is not running: - take actions defined in cl... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.2.3 Broadcast transmission | The RD shall set the content of the broadcast transmission as follows: • if the message is a beacon message: - use Physical Layer Control Field: Type 1; • else: - use Physical Layer Control Field: Type 2 and set Receiver Identity to broadcast ID; ETSI ETSI TS 103 636-4 V2.1.1 (2024-10) 21 Release 2 • if MAC security is... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.3 Random Access procedure | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.3.1 General | Resources for random access transmissions per operating channel are broadcasted in beacons by RDs. Random access transmission and resources are defined by the following parameters: • RACH resources subslots: Indicates subslot index of the first and last subslot in a frame for RACH resources. • Repetition: Defines how o... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.3.2 Announcing Random access resources | An RD may start announcing random access resources with a beacon message or by using unicast signalling. By using unicast signalling, the RD in mesh system operation may indicate its random access resources to other RD which it has an association with. Before announcing resources, the RD should evaluate local interfere... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.3.3 Random Access transmission | Before transmitting to random access resources, the RD shall: • obtain random access parameters listed in clause 5.3.1 from Random Access Resource IE; • if timer dectRachResourceFailure is running and RD receives Random Access Resource IE: - stop timer dectRachResourceFailure; ETSI ETSI TS 103 636-4 V2.1.1 (2024-10) 23... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.3.4 Random Access response | After performing a random access transmission, the RD should receive a response within a time indicated as the random access response window. If the RD does not receive a response message as PHY control indicating either ACK, NACK, or logical MAC response PDU (e.g. Association Response to an Association Request) during... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.4 Scheduled access data transfer | |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.4.1 General | The scheduled access data transfer is performed by using pre-assigned resources between an RD in FT mode and an RD in PT mode. The FT part of the communication assigns the resources for the RD in PT mode to transmit and receive. Figure 5.4.1-1 depicts an example of resource allocation signalled with a single Resource a... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.4.2 Allocating resources for scheduled access | An RD in FT mode may allocate resources for scheduled access for communication after it has selected operating channel(s) and while timer scanStatusValid is running as defined in clause 5.1.2. To allocate resources for scheduled transmission the RD in FT mode shall: • if DECT_PROTECTED is TRUE and dectProTime is not ru... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.4.3 Scheduled access transmission and reception | The RD shall: • receive all resources configured as receive as follows: - perform HARQ operation as defined in clause 5.5; NOTE: The transmitter may decide not to request HARQ feedback and not to use HARQ re-transmission for a given transmission. • maintain reception of beacon messages, if the RD is not able to receive... |
d89507c76a6f42d05621a45afb477423 | 103 636-4 | 5.5 HARQ Operation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.