hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 3 Definitions and abbreviations | |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: base station: Piece of equipment providing simultaneous, bi-directional network access to mobile stations. block: Fixed-length sequence of bytes from a MAC PDU. contention-free: Physical layer access method in which there is no possibi... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledged ARQ Automatic Repeat Request BE Best-Effort BS Base Station CL Controlled-Load DAWS Digital Advanced Wireless Service DL Downlink DQOS Data Integrity Quality Of Service IP Internet Protocol LLC Logical Link Control MAC Medium ... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 4 Introduction | The DAWS protocol architecture is provided in TR 101 156 [1]. The Medium Access Control (MAC) provides services to the Logical Link Control (LLC) and requests services from the Physical layer (PHY). The present document describes the services the MAC shall provide to function within a DAWS network. The prefix MAC will ... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 5 Registration Services | The MAC registration service (MAC_REG) is responsible for interacting with the PHY layer to maintain the highest possible signal quality for the current serving cell, as well as performing adjacent cell scans when requested by LLC_REG. MAC_REG is also responsible for managing hand-over in sectorised cells. This clause ... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 6 Bandwidth Management Services | The MAC bandwidth management service (MAC_BWM) is responsible for allocating bandwidth over the physical medium for MS in full-power and power-saving modes of operation. The BS and MS share bandwidth allocation responsibility, and are thus jointly responsible for the timing quality of service (TQOS) delivered to flows. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 6.1 Base station bandwidth management | BS_MAC_BWM shall allocate bandwidth on a per-MS basis, not a per-flow basis. BS_MAC_BWM shall consider the current state of all input queues and QOS contracts for each registered MS, and then shall dynamically allocate a portion of available free bandwidth to each MS. During multiframe N, BS_MAC_BWM shall prepare and s... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 6.2 Mobile station bandwidth management | MS_MAC_BWM shall divide the bandwidth allocation dynamically granted by BS_MAC_BWM among its acknowledged protocol processes. During times of increasing system congestion, MS_MAC_BWM shall decrease the TQOS for the best-effort protocol processes before decreasing the TQOS for the controlled-load protocol processes. MS_... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 6.3 Power management | MAC-BWM shall support a power conservation strategy which allows the MS to remain in a low power consumption state for a considerable portion of the time. A power conserving MS shall resume normal operation before attempting an MPDU transfer. The QOS delivered to an MPDU from a power conserving MS shall be equivalent t... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7 Transport Services | The MAC transport service (MAC_TPT) is responsible for the transfer of MPDUs over the physical medium. This clause discusses the architecture of MAC_TPT, provides requirements for the protocols in the MAC_TPT protocol suite, and describes MAC_TPT error handling. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.1 Architecture | As shown in figures 2 and 3, MAC_TPT is composed of a suite of six separate protocols: • UNACK_DL: unacknowledged downlink; • UNACK_UL: unacknowledged uplink; • ACK_BE_DL: acknowledged downlink, best-effort traffic; • ACK_BE_UL: acknowledged uplink, best-effort traffic; ETSI TS 101 659 V1.1.1 (1999-04) 10 • ACK_CL_DL: ... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.1.1 Mobile station architecture | As shown in figure 2, MS_MAC shall create and maintain a pair of protocol processes, UNACK_DL and UNACK_UL, upon power-up. These processes handle the transfer of downlink and uplink PDUs using unacknowledged protocols. When MS_LLC registers with BS_LLC, the two LLCs co-operate to create a pair of protocol instances, AC... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.1.2 Base station architecture | As shown in figure 3, BS_MAC_TPT contains one pair of protocol processes, UNACK_BE_DL and UNACK_BE_UL, which handle all unacknowledged traffic within the serving cell. These protocol processes are created when the BS is powered up. BS_MAC_TPT shall contain one pair of protocol processes, ACK_BE_DL and ACK_BE_UL, for ea... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2 Transport protocol suite | This clause describes the six protocols in the MAC_TPT protocol suite in more detail. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.1 Unacknowledged downlink | UNACK_DL shall utilize a contention-free PHY access method available via PHY_SAP_A. A BS shall use UNACK_DL for system information and broadcast MPDUs. UNACK_DL PDUs may carry either a unicast or broadcast MSH as the destination address. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.2 Unacknowledged uplink | UNACK_UL shall utilize a contention-possible PHY access method available via PHY_SAP_A. UNACK_UL PDUs may carry either a MSI or a unicast MSH as the source address. The MSI is used by an unregistered MS; the unicast MSH is used by a registered MS. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.3 Acknowledged protocols | The ACK protocols shall implement a selective retransmission, ARQ strategy for MPDU transfer. The ACK protocols shall employ extensive error-recovery procedures to minimize transfer failures. PDUs transferred by an ACK protocol may only carry a unicast MSH as the source or destination address. The ACK protocols shall d... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.3.1 Acknowledged Downlink, Best-effort QOS | ACK_BE_DL shall perform a physical layer bandwidth reservation and release for each individual MPDU transferred. If there are multiple MPDUs queued for transfer, ACK_BE_DL may delay bandwidth release until all queued MPDUs are transferred. The ACK_BE_DL bandwidth reservation sub-protocol shall utilize a contention-free... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.3.2 Acknowledged Uplink, Best-effort QOS | ACK_BE_UL shall perform a physical layer bandwidth reservation and release for each individual MPDU transferred. If there are multiple MPDUs queued for transfer, ACK_BE_UL may delay bandwidth release until all queued MPDUs are transferred. The ACK_BE_UL bandwidth reservation sub-protocol shall utilize a contention-poss... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.3.3 Acknowledged Downlink, Controlled-load QOS | ACK_CL_DL shall perform a physical layer bandwidth reservation upon instantiation and a physical layer bandwidth release upon termination. The ACK_CL_DL bandwidth reservation sub-protocol shall utilize a contention-free PHY access method. The MPDU transfer and bandwidth release sub-protocols shall also utilize a conten... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.2.3.4 Acknowledged Uplink, Controlled-load QOS | ACK_CL_UL shall perform a physical layer bandwidth reservation upon instantiation and a physical layer bandwidth release upon termination. The ACK_CL_UL bandwidth reservation sub-protocol shall utilize a contention-reduced PHY access method. The MPDU transfer and bandwidth release sub-protocols shall utilize a contenti... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.3 Transport failure handling | This clause describes how MAC_TPT shall respond to transport protocol failures. For this clause, the term "MPDU source" means a source either internal to the MAC or an SPDU passed via a MAC service access point. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.3.1 Unacknowledged downlink failure | The failure of UNACK_DL to transfer an MPDU shall not be signalled to the MPDU source. MPDU transfer will continue with the next queued MPDU, if any. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.3.2 Unacknowledged uplink failure | The failure of UNACK_UL to transfer an MPDU shall not be signalled to the MPDU source. MPDU transfer will continue with the next queued MPDU, if any. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 7.3.3 Acknowledged failure | The failure of an ACK protocol to successfully transfer an MPDU shall be interpreted as a localized link failure between a BS and an MS. All MPDUs queued for the failed protocol instance shall be discarded, an error shall be returned to the MPDU source, and the instance shall be deleted. All other ACK protocol instance... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8 Service Primitives | |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1 Primitive Definitions | |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.1 MAC_unack_transfer_request | Table 1 MAC_unack_transfer_request Usage BS and MS Source LLC Layer Destination MAC Layer Service Access Point A Multiple Outstanding No SDU Parameters LPDU This primitive is used by the LLC layer to pass a LPDU to the MAC layer for transfer to one or more peer MAC SAP As. If this primitive is issued by the BS, the dow... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.5 MAC_ack_transfer_confirm | Table 5 MAC_ack_transfer_confirm Usage BS and MS Source MAC Layer Destination LLC Layer Service Access Point B SDU Parameters ack_transfer_receipt_ack This primitive acknowledges the receipt of the LPDU associated with a MAC_ack_transfer_request. It does not indicate that the LPDU has been transferred to one or more pe... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.6 MAC_ack_transfer_indication | Table 6 MAC_ack_transfer_indication Usage BS and MS Source MAC Layer Destination LLC Layer Service Access Point B SDU Parameters protocol_instance_ID ack_transfer_result LPDU This primitive passes a received LPDU to the LLC layer. The protocol instance ID of the protocol instance which performed the transfer is provide... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.7 MAC_create_protocol_request | Table 7 MAC_create_protocol_request Usage BS and MS Source LLC Layer Destination MAC Layer Service Access Point C Multiple Outstanding No SDU Parameters protocol_instance_ID MS_handle protocol_type protocol_parameters This primitive requests the allocation of resources for a new acknowledged protocol instance. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.8 MAC_create_protocol_confirm | Table 8 MAC_create_protocol_confirm Usage BS and MS Source MAC Layer Destination LLC Layer Service Access Point C SDU Parameters create_protocol_result This primitive confirms the creation of the requested protocol. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.9 MAC_delete_protocol_request | Table 9 MAC_delete_protocol_request Usage BS and MS Source LLC Layer Destination MAC Layer Service Access Point C Multiple Outstanding Yes SDU Parameters protocol_instance_ID This primitive requests the deletion of a protocol instance. Any PDUs queued for transmission will be discarded. ETSI TS 101 659 V1.1.1 (1999-04)... |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.11 MAC_hunt_request | Table 11 MAC_hunt_request Usage MS Source LLC Layer Destination MAC Layer Service Access Point C Multiple Outstanding No SDU Parameters --- This primitive tells the MAC to perform signal strength and signal quality measurements on the serving cell (if any) and all adjacent cells. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.12 MAC_hunt_confirm | Table 12 MAC_hunt_confirm Usage MS Source MAC Layer Destination LLC Layer Service Access Point C SDU Parameters hunt_result This primitive returns cell measurement results to MS_LLC. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.13 MAC_service_request | Table 13 MAC_service_request Usage MS Source LLC Layer Destination MAC Layer Service Access Point C Multiple Outstanding No SDU Parameters base_station_ID This primitive tells the MAC to camp on the BS specified by base_station_ID. ETSI TS 101 659 V1.1.1 (1999-04) 18 |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.14 MAC_service_confirm | Table 14 MAC_service_confirm Usage MS Source MAC Layer Destination LLC Layer Service Access Point C SDU Parameters service_result This primitive confirms a service request. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.1.15 MAC_service_indication | Table 15 MAC_service_indication Usage MS Source MAC Layer Destination LLC Layer Service Access Point C SDU Parameters service_status This primitive is used by the MAC to asynchronously provide the LLC with the latest service status. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2 Parameter Definitions | |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.1 base_station_ID | This parameter specifies a particular DAWS BS. ETSI TS 101 659 V1.1.1 (1999-04) 19 |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.2 ack_transfer_receipt_ack | Table 16 ack_transfer_receipt_ack 0 success: receipt acknowledged 1 failure: transfer request already pending |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.3 ack_transfer_result | Table 17 ack_transfer_result 0 success: transfer OK 1 failure: transfer failed or aborted |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.4 configure_scheduling_result | Table 18 configure_scheduling_result 0 success: scheduler configured as requested 1 failure: specified protocol instance does not exist |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.5 create_protocol_result | Table 19 create_protocol_result 0 success: requested protocol created 1 failure: create protocol request already pending 2 failure: requested resources unavailable |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.6 delete_protocol_result | Table 20 delete_protocol_result 0 success: requested protocol deleted 1 failure: protocol instance does not exist |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.7 hunt_result | This parameter consists of a list of available cells with associated signal strength and signal quality measurements. The parameter will be defined when the DAWS PHY is defined. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.8 LPDU | Definition of this parameter is beyond the scope of the present document. Most often, it will consist of a LLC layer header and an IP datagram. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.9 MS_handle | This parameter is an identifier used to identify a particular MS while it is registered with a BS. ETSI TS 101 659 V1.1.1 (1999-04) 20 |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.10 new_scheduling_state | Table 21 new_scheduling_state 0 scheduling disabled 1 scheduling enabled |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.11 new_service_state | Table 22 new_service_state 0 service now unavailable 1 service now available (new subnet) |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.12 protocol_instance_ID | This parameter uniquely identifies a protocol instance. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.13 protocol_parameters | This parameter contains information required by the MAC to properly manage the protocol instance. It will be further refined in a future version of the present document. |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.14 protocol_type | Table 23 protocol_type 0 Best-effort downlink 1 Best-effort uplink 2 Controlled-load downlink 3 Controlled-load uplink |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.15 queue_empty_result | Table 24 queue_empty_result 0 success: input queue of protocol instance is empty 1 failure: protocol instance does not exist |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.16 service_result | Table 25 service_result 0 success: requested service now available 1 failure: could not complete request |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.17 service_status | This parameter indicates whether service is currently provided, and if so, the base_station_ID, current signal strength, and quality of the service. This parameter will be further defined after the DAWS PHY is defined. ETSI TS 101 659 V1.1.1 (1999-04) 21 |
90fe9c396f1c298d558e84dc6c6cf369 | 101 659 | 8.2.18 unack_transfer_receipt_ack | Table 26 unack_transfer_receipt_ack 0 success: receipt acknowledged 1 failure: transfer request already pending ETSI TS 101 659 V1.1.1 (1999-04) 22 Bibliography The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information. - IET... |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 1 Scope | .........................................................................................................................................7 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 2 References | .................................................................................................................................7 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 3 Definitions, symbols and abbreviations | ....................................................................................7 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 3.1 Definitions | .........................................................................................................................................7 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 3.2 Symbols | .............................................................................................................................................7 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 3.3 Abbreviations | .....................................................................................................................................8 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 4 General | ....................................................................................................................................11 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 4.1 Measurement uncertainty | .................................................................................................................11 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 4.2 Power Classes | ..................................................................................................................................11 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5 Frequency bands and channel arrangement | .............................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.1 General | .............................................................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.2 Frequency bands | ..............................................................................................................................12 5.3 TX–RX frequency separation ..........................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.4 Channel arrangement | .......................................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.4.1 Channel spacing | .........................................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.4.2 Channel raster | .............................................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 5.4.3 Channel number | .........................................................................................................................12 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6 Transmitter characteristics | ......................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.1 General | .............................................................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.2 Transmit power | ................................................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.2.1 UE maximum output power | .......................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.3 Frequency stability | ...........................................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4 Output power dynamics | ...................................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.1 Open loop power control | ............................................................................................................14 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.2 Inner loop power control in the uplink | .......................................................................................15 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.4.3 Minimum transmit output power | ................................................................................................15 6.5 Transmit ON/OFF power.................................................................................................................16 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.1 Transmit OFF power | ..................................................................................................................16 6.5.2 Transmit ON/OFF Time mask....................................................................................................16 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.3 Change of TFC | ...........................................................................................................................16 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.5.4 Power setting in uplink compressed mode | .................................................................................17 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6 Output RF spectrum emissions | ........................................................................................................18 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.1 Occupied bandwidth | ...................................................................................................................18 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.2 Out of band emission | ..................................................................................................................18 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.6.3 Spurious emissions | .....................................................................................................................19 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.7 Transmit intermodulation | .................................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.7.1 Minimum requirement | ................................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8 Transmit modulation | ........................................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8.1 Transmit pulse shape filter | .........................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8.2 Modulation Accuracy | .................................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 6.8.3 Peak code domain error | ..............................................................................................................20 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.0 Receiver characteristics | ...........................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.1 General | .............................................................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.2 Diversity characteristics | ...................................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.3 Reference sensitivity level | ...............................................................................................................22 |
be78612ff8f67b9deea189a8b80762b8 | 125 101 | 7.3.1 Minimum requirement | ................................................................................................................22 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.