hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1 Radio Resource management principles | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.1 Allocation of resources for the GPRS | ETSI ETSI TS 101 350 V7.0.0 (1999-07) 14 (GSM 03.64 version 7.0.0 Release 1998) A cell supporting GPRS may allocate resources on one or several physical channels in order to support the GPRS traffic. Those physical channels (i.e. PDCHs), shared by the GPRS MSs, are taken from the common pool of physical channels availa... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.1.1 Master-Slave concept | At least one PDCH, acting as a master, accommodates packet common control channels that carry all the necessary control signalling for initiating packet transfer (i.e. PCCCH), whenever that signalling is not carried by the existing CCCH, as well as user data and dedicated signalling (i.e. PDTCH and PACCH). Other PDCHs,... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.1.2 Capacity on demand concept | The GPRS does not require permanently allocated PDCHs. The allocation of capacity for GPRS can be based on the needs for actual packet transfers which is here referred to as the "capacity on demand" principle. The operator can, as well, decide to dedicate permanently or temporarily some physical resources (i.e. PDCHs) ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.1.3 Procedures to support capacity on demand | The number of allocated PDCHs in a cell can be increased or decreased according to demand. The following principles can be used for the allocation: - Load supervision: A load supervision function may monitor the load of the PDCHs and the number of allocated PDCHs in a cell can be increased or decreased according to dem... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.1.4 Release of PDCH not carrying PCCCH | The fast release of PDCH is an important feature for possibility to dynamically share the same pool of radio resources for packet and circuit-switched services. There are following possibilities: ETSI ETSI TS 101 350 V7.0.0 (1999-07) 15 (GSM 03.64 version 7.0.0 Release 1998) - Wait for all the assignments to terminate ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.2 Multiframe structure for PDCH | NOTE: The text in this clause is informative. The normative text is in GSM 05.02. Where there is a conflict between these descriptions, the normative text has precedence. The mapping in time of the logical channels is defined by a multiframe structure. The multiframe structure for PDCH consists of 52 TDMA frames, divid... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.3 Scheduling of PBCCH information | An MS attached to GPRS shall not be required to monitor BCCH if a PBCCH exists. All system information relevant for GPRS and some information relevant for circuit switched services (e.g. the access classes) shall in this case be broadcast on PBCCH. In order to facilitate the MS operation, the network is required to tra... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.1.4 SMS cell broadcast | An MS attached to GPRS shall not be required to monitor the CBCH channel if a PCCCH exists. [EDITOR’S NOTE: Service is not specified] |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.2 Radio Resource operating modes | Radio Resource (RR) management procedures are characterised by two different RR operating modes. Each mode describes a certain amount of functionality and information allocated. RR procedures and RR operating modes are specified in GSM 04.07. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.2.1 Packet idle mode | In packet idle mode no Temporary Block Flow (see subclause 6.6.4.2) exists. Upper layers can require the transfer of a LLC PDU which, implicitly, may trigger the establishment of TBF and transition to packet transfer mode. In packet idle mode, the MS listens to the PBCCH and to the paging sub-channel for the paging gro... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.2.2 Packet transfer mode | In packet transfer mode, the mobile station is allocated radio resource providing a Temporary Block Flow on one or more physical channels. Continuous transfer of one or more LLC PDUs is possible. Concurrent TBFs may be established in opposite directions. Transfer of LLC PDUs in RLC acknowledged or RLC unacknowledged mo... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.3 Layered overview of radio interface | The GPRS radio interface can be modelled as a hierarchy of logical layers with specific functions. An example of such layering is shown in Figure 3. The various layers are briefly described in the following subclauses. The physical layer has been separated into two distinct sub-layers defined by their functions: - Phys... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.4 Physical RF Layer | The GSM Physical RF layer is defined in GSM 05 series recommendations, which specify among other things: - The carrier frequencies characteristics and GSM radio channel structures (GSM 05.02 [4]); - The modulation of the transmitted wave forms and the raw data rates of GSM channels (GSM 05.04 [6]); and - The transmitte... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5 Physical Link Layer | The Physical Link layer operates above the physical RF layer to provide a physical channel between the MS and the Network. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.1 Layer Services | The purpose of the Physical Link layer is to convey information across the GSM radio interface, including RLC/MAC information. The Physical Link layer supports multiple MSs sharing a single physical channel. The Physical Link layer provides communication between MSs and the Network. The Physical Link layer control func... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.2 Layer Functions | The Physical Link layer is responsible for: - Forward Error Correction (FEC) coding, allowing the detection and correction of transmitted code words and the indication of uncorrectable code words. The coding schemes are described in subclause 6.5.5. - Rectangular interleaving of one Radio Block over four bursts in cons... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.3 Service Primitives | Table 2 lists the service primitives provided by the Physical Link layer to RLC/MAC layer. More detailed description is given in GSM 04.04. ETSI ETSI TS 101 350 V7.0.0 (1999-07) 19 (GSM 03.64 version 7.0.0 Release 1998) Table 2: Service primitives provided by the Physical link layer Name Request indication response con... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.4 Radio Block Structure | Different Radio Block structures for data transfer and control message transfer purposes are defined. Radio Block consists of MAC Header, RLC Data Block or RLC/MAC Control Block. It is always carried by four normal bursts. For detailed definition of radio block structure, see GSM 04.60. MAC header RLC header RLC data M... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5 Channel Coding | NOTE: The text in this subclause is informative. The normative text is in GSM 05.03 [5]. Where there is a conflict between these descriptions, the normative text has precedence. Four coding schemes, CS-1 to CS-4, are defined for the packet data traffic channels. For all other packet control channels than Packet Random ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5.1 Channel coding for PDTCH | Four different coding schemes, CS-1 to CS-4, are defined for the Radio Blocks carrying RLC data blocks. The block structures of the coding schemes are shown Figure 5 and Figure 6. ETSI ETSI TS 101 350 V7.0.0 (1999-07) 21 (GSM 03.64 version 7.0.0 Release 1998) rate 1/2 convolutional coding puncturing 456 bits USF BCS Ra... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5.2 Channel coding for PACCH, PBCCH, PAGCH, PPCH,PNCH and PTCCH | The channel coding for the PACCH, PBCCH, PAGCH, PPCH,PNCH and downlink PTCCH is the same as the coding scheme CS-1 presented in subclause 6.5.5.1. The coding scheme used for uplink PTCCH is the same as for PRACH. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5.3 Channel Coding for the PRACH | Two types of packet access burst may be transmitted on the PRACH: an 8 information bits access burst or an 11 information bits access burst called the extended packet access burst. The mobile shall support both access bursts. The channel coding for both burst formats is indicated in the following subclauses. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5.3.1 Coding of the 8 data bit Packet Access Burst | The channel coding used for the burst carrying the 8 data bit packet access uplink message is identical to the coding of the access burst as defined for random access channel in GSM 05.03. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.5.3.2 Coding of the 11 data bit Packet Access Burst | The channel coding for 11 bit access burst is the punctured version of the same coding as used for 8 bit access burst. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.6 Cell Re-selection | NOTE: The text in this subclause is informative. The normative text is in GSM 03.22 and GSM 05.08. Where there is a conflict between these descriptions, the normative text has precedence. In GPRS Packet Idle and Packet Transfer modes, cell re-selection is performed by the MS, except for a class A MS (see GSM 02.60) whi... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.6.1 Measurements for Cell Re-selection | The MS shall measure the received RF signal strength on the BCCH frequencies of the serving cell and the neighbour cells as indicated in the BA-GPRS list, and calculate the received level average (RLA) for each frequency, as specified in GSM 05.08. In addition the MS shall verify the BSIC of the cells. Only channels wi... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.6.2 Broadcast Information | The PBCCH broadcasts GPRS specific cell re-selection parameters for serving and neighbour cells, including the BA (GPRS) list. A BA (GPRS) identifies the neighbour cells, including BSIC, that shall be considered for GPRS cell (re- selection (not necessary the same as for GSM in Idle or circuit switched mode)). |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.6.3 Optional measurement reports and network controlled cell re-selection | It shall be possible for the network to order the mobile stations to send measurement reports to the network and to suspend its normal cell re-selection, and instead to accept decisions from the network. This applies to both Packet idle mode and Packet transfer mode. The degree to which the mobile station shall resign ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.7 Timing Advance | NOTE: The text in this subclause is informative. The normative text is in GSM 04.60 and GSM 05.10. Where there is a conflict between these descriptions, the normative text has precedence. The timing advance procedure is used to derive the correct value for timing advance that the MS has to use for the uplink transmissi... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.7.1 Initial timing advance estimation | The initial timing advance estimation is based on the single access burst carrying the Packet Channel Request. The Packet Uplink Assignment or Packet Downlink Assignment then carries the estimated timing advance value to the MS. This value shall be used by the MS for the uplink transmissions until the continuous timing... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.7.2 Continuous timing advance update | MS in Packet transfer mode shall use the continuous timing advance update procedure. The continuous timing advance update procedure is carried on the PTCCH allocated to the MS. For uplink packet transfer, within the Packet Uplink Assignment, the MS is assigned Timing Advance Index (TAI) and the PTCCH. For downlink pack... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.7.2.1 Mapping on the multiframe structure | Figure 7 shows the mapping of the uplink access bursts and downlink TA-messages on groups of eight 52-multiframes: - the TAI value shows the position where a slot is reserved for a MS to send an access burst (e.g. T1 means 52- multiframe number n and idle slot number 2). TAI value defines the used PTCCH sub-channel. - ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8 Power control procedure | Power control shall be supported in order to improve the spectrum efficiency and to reduce the power consumption in the MS. For the uplink, the MS shall follow a flexible power control algorithm, which the network can optimise through a set of parameters. It can be used for both open loop and closed loop power control.... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.1 MS output power | The MS shall calculate the RF output power value, PCH, to be used on each individual uplink PDCH assigned to the MS: PCH = min((Γ0 - ΓCH - α * (C + 48), PMAX) where ΓCH is an MS and channel specific power control parameter. It is sent to the MS in any resource assigning message. Further, the network can, at any time du... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.2 BTS output power | The BTS shall use constant power on those PDCH radio blocks which contain PBCCH or which may contain PPCH. This power may be lower than the output power used on BCCH. The difference shall be broadcast on PBCCH. On the other PDCH radio blocks, downlink power control may be used. Thus, a procedure may be implemented in t... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.3 Measurements at MS side | A procedure shall be implemented in the MS to monitor periodically the downlink Rx signal level and quality from its serving cell. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.3.1 Deriving the C value | This subclause comprises information about how the MS shall derive the C value in the power control equation. The MS shall periodically measure the received signal strength. In packet idle mode, the MS shall measure the signal strength of the PCCCH or, if PCCCH is not existing, the BCCH. In packet transfer mode, the MS... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.3.2 Derivation of Channel Quality Report | The channel quality is measured as the interference signal level during the idle frames of the multiframe, when the serving cell is not transmitting. In packet transfer mode, the MS shall measure the interference signal strength of all eight channels (slots) on the same carrier as the assigned PDCHs. In packet idle mod... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.8.4 Measurements at BSS side | A procedure shall be implemented in the BSS to monitor the uplink Rx signal level and quality on each uplink PDCH, active as well as inactive. The BSS shall also measure the Rx signal level and the quality of a specific MS packet transfer. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.9 Scheduling the MS activities during the PTCCH and idle frames | The MS shall use the PTCCH and idle frames of the PDCH multiframe for the following tasks: - BSIC identification for cell re-selection (6.5.6.1) - Continuous timing advance procedures (6.5.7.2) - Interference measurements for power control (6.5.8.3.2) It is not necessary to exactly specify the scheduling of these tasks... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.5.10 Discontinuous Reception (DRX) | NOTE: The text in this subclause is informative. The normative text is in GSM 05.02. Where there is a conflict between these descriptions, the normative text has precedence. DRX (sleep mode) shall be supported when the MS is in Packet Idle mode. DRX is independent from MM states Ready and Standby. Negotiation of DRX pa... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6 Medium Access Control and Radio Link Control Layer | The Medium Access Control (MAC) and Radio Link Control (RLC) layer operates above the Physical Link layer in the reference architecture. MAC/RLC layer messages and signalling procedures are defined in GSM 04.60 and GSM 04.08. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.1 Layer Services | The MAC function defines the procedures that enable multiple MSs to share a common transmission medium, which may consist of several physical channels. The MAC function provides arbitration between multiple MSs attempting to transmit simultaneously and provides collision avoidance, detection and recovery procedures. Th... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.2 Layer Functions | The GPRS MAC function is responsible for: - Providing efficient multiplexing of data and control signalling on both uplink and downlink, the control of which resides on the Network side. On the downlink, multiplexing is controlled by a scheduling mechanism. On the uplink, multiplexing is controlled by medium allocation... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.3 Service Primitives | Table 5 lists the service primitives provided by the RLC/MAC layer to the upper layers: Table 5: Service primitives provided by the RLC/MAC layer to the upper layers Name request indication response confirm comments RLC/MAC-DATA x x used for the transfer of upper layer PDUs. Acknowledged mode of operation in RLC is use... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4 Model of Operation | Each PDCH is a shared medium between multiple MSs and the Network. Direct communication is possible only between an MS and the network. The GPRS radio interface consists of asymmetric and independent uplink and downlink channels. The downlink carries transmissions from the network to multiple MSs and does not require c... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.1 Uplink State Flag | The Uplink State Flag (USF) is used on PDCH to allow multiplexing of Radio blocks from a number of MSs. USF is used in dynamic and extended dynamic medium access modes. USF is used only in downlink direction. The USF comprises 3 bits at the beginning of each Radio Block that is sent on the downlink. It enables the codi... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.2 Temporary Block Flow | A Temporary Block Flow (TBF) is a physical connection used by the two RR entities to support the unidirectional transfer of LLC PDUs on packet data physical channels. The TBF is allocated radio resource on one or more PDCHs and comprise a number of RLC/MAC blocks carrying one or more LLC PDUs. A TBF is temporary and is... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.3 Temporary Flow Identity | Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The assigned TFI is unique among concurrent TBFs in each directions and is used instead of the MS identity in the RLC/MAC layer. The same TFI value may be used concurrently for TBFs in opposite directions. The TFI is assigned in a resource assignment ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.4 Medium Access modes | Three medium access modes are supported: - Dynamic allocation; - Extended Dynamic allocation; and - Fixed allocation The Dynamic allocation medium access mode or Fixed allocation medium access mode shall be supported by all networks that support GPRS. The support of Extended Dynamic allocation is optional. The Dynamic ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.5 Acknowledged mode for RLC/MAC operation | The transfer of RLC Data Blocks in the acknowledged RLC/MAC mode is controlled by a selective ARQ mechanism coupled with the numbering of the RLC Data Blocks within one Temporary Block Flow. The sending side (the MS or the network) transmits blocks within a window and the receiving side sends Packet Uplink Ack/Nack or ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.6 Unacknowledged mode for RLC/MAC operation | The transfer of RLC Data Blocks in the unacknowledged RLC/MAC mode is controlled by the numbering of the RLC Data Blocks within one Temporary Block Flow and does not include any retransmissions. The receiving side extracts user data from the received RLC Data Blocks and attempts to preserve the user information length ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7 Mobile Originated Packet Transfer | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.1 Uplink Access | Network Packet Channel Request Packet Uplink Assignment Packet Resource Request Packet Uplink Assignment PRACH (or RACH ) PAGCH (or AGCH ) PACCH PACCH (Optional) (Optional) Figure 9: Access and allocation for the one or two phase packet access, uplink packet transfer An MS initiates a packet transfer by making a Packet... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.2 Dynamic/Extended Dynamic allocation | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.2.1 Uplink Packet Transfer | The Packet Uplink Assignment message includes the list of PDCHs and the corresponding USF value per PDCH. A unique TFI is allocated and is thereafter included in each RLC Data and Control Block related to that Temporary Block Flow. The MS monitors the USFs on the allocated PDCHs and transmits Radio blocks on those whic... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.2.2 Release of the Resources | The release of the resources is normally initiated from the MS by counting down the last couple of blocks. For the normal release of resources for RLC connection carrying a mobile originated packet transfer, the mechanism based on acknowledged final Packet Uplink Ack/Nack combined with timers is used. After the MS has ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.3 Fixed Allocation | Fixed allocation uses the Packet Uplink Assignment message to communicate a detailed fixed uplink resource allocation to the MS. The fixed allocation consists of a start frame, slot assignment, and block assignment bitmap representing the assigned blocks per timeslot. The MS waits until the start frame indicated and th... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.7.4 Contention Resolution | Contention resolution is an important part of RLC/MAC protocol operation, especially because one channel allocation can be used to transfer a number of LLC frames. Contention resolution applies for both dynamic and fixed allocation medium access modes. There are two basic access possibilities, one phase and two phase a... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.8 Mobile Terminated Packet Transfer | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.8.1 Packet Paging | The network initiates packet transfer to an MS that is in Standby state by sending a Packet Paging Request on the downlink PPCH or PCH. The MS responds to the Packet Paging Request by initiating a procedure for page response. The RLC/MAC Packet Paging Response message contains TLLI, as well as a complete LLC frame incl... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.8.2 Downlink Packet Transfer | Transmission of a packet to an MS in the Ready state is initiated by the network using the Packet Downlink Assignment message. In case there is PCCCH allocated in the cell, the Packet Downlink Assignment is transmitted on PAGCH. In case there is no PCCCH allocated in the cell, the Immediate Assignment is transmitted on... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.8.3 Release of the Resources | The release of the resources is initiated by the network by terminating the downlink transfer and polling the MS for a final Packet Downlink Ack/Nack. It is possible for the network to change the current downlink assignment by using the Packet Downlink Assignment or Packet Timeslot Reconfigure message, which then has t... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.6.4.9 Simultaneous Uplink and Downlink Packet Transfer | During the ongoing uplink Temporary Block Flow, the MS continuously monitors one downlink PDCH for possible occurrences of Packet Downlink Assignment or Packet Timeslot Reconfigure messages on PACCH (see Figure 11). The MS is therefore reachable for downlink packet transfers that can then be conveyed simultaneously on ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.7 Abnormal cases in GPRS MS Ready State | The RLC/MAC error causes and procedures to handle these can be found in GSM 04.08, 04.60 and 05.08. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6.8 PTM-M Data Transfer | NOTE: The stage 3 specification for PTM-M data transfer is left for phase 2 of GPRS specification. PTM-M data, in the form of individual LLC frames, is mapped into RLC/MAC-PTM_DATA primitive and distributed from SGSN to the BSS representing the cells that are defined by a geographical area parameter. To the cells conce... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 1 Scope | The present document specifies the Network Service used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface). The protocol stack on the Gb interface is defined in the stage 2 Technical Specification GSM 03.60 [3]. The Network Service entity provides network services to the BSSGP... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 3 Definitions, symbols and abbreviations | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. For additional applicable definitions refer to GSM 02.60 [2]. BSSGP Virtual Connection (BVC): An end-to-end virtual communication path between remote Network Service user entities. BSSGP Virtual Connection Identifier (BVCI): The identi... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 3.2 Symbols | Refer to GSM 03.60 [3]. ETSI ETSI TS 101 299 V7.1.0 (1999-07) 8 (GSM 08.16 version 7.1.0 Release 1998) |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply. Additional applicable abbreviations can be found in GSM 01.04 [1]. When there is conflict between the present document and GSM 01.04 [1], the following list takes precedence. BECN Backward Explicit Congestion Notification BSSGP Base Station Sy... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4 Network Service general description | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.1 Overview | The position of the Network Service within the protocol stack of the Gb interface is shown in Figure 1/GSM 08.16. Gb BSS LLC BSSGP L1 SGSN NS L1 MAC BSSGP RLC RELAY NS NOTE: BSSGP, L1, LLC, MAC, RELAY, RLC are outside the scope of this Technical Specification, refer to TS GSM 03.60 [3] for further details. Figure 1/GSM... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.2 Addressing | The purpose of this clause is to describe the addressing principles on the Gb interface in a generic way, i.e. irrespective of the exact configuration of the Gb interface and of the exact nature of the intermediate transmission network, when present. Therefore, this clause provides an abstract description of the addres... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.2.1 Network Service Virtual Link (NS-VL) | An SGSN and a BSS may use different physical links for connecting to each other (e.g. because of intermediate equipment or transmission network). Each physical link is locally (i.e. at each side of the Gb interface) identified by means of a physical link identifier. The exact structure of the physical link identifier i... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.2.2 Network Service Virtual Connection (NS-VC) | In order to provide end-to-end communication between the BSS and SGSN irrespective of the exact configuration of the Gb interface, the concept of Network Service Virtual Connection (NS-VC) is used.The NS-VCs are end-to-end virtual connections between the BSS and SGSN. At each side of the Gb interface there is a one-to-... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.2.3 Network Service Virtual Connection Group | The Network Service Virtual Connection Group groups together all NS-VCs providing communication between the same peer NS entities. One NS-VC group is configured between two peer NS entities. This grouping is performed by administrative means. At each side of the Gb interface, there is a one-to-one correspondence betwee... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.2.4 BSSGP Virtual Connection (BVC) | The Network Service provides communication paths between remote NS user entities. These communication paths are called BSSGP Virtual Connections (BVCs). Each BVC is used to transport NS SDUs between NS users. A Network Service Entity provides one or more BVCs between peer NS user entities. Each BVC is supported by one ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.3 Sub-Network Service functions | The Sub-Network Service functions of the Network Service shall provide access to the intermediate network (or to the peer entity in case of direct point-to-point configuration) by means of NS-VLs and shall provide NS-VCs between NS peer entities. On each NS-VC, data are transferred in order by the Sub-Network Service. ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.4 Load sharing function | The load sharing function distributes the NS SDU traffic among the unblocked NS-VCs of the same group on the Gb interface. The use of load sharing also provides to the upper layer seamless service upon failure by re-organizing the NS SDU traffic between the unblocked NS-VCs of the same group. The re-organization may di... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.4.1 Requirements on load sharing function | All NS SDUs to be transmitted over the Gb interface are passed to the load sharing function along with the Link Selector Parameter (LSP) , the BVCI and the NSEI. LSP and BVCI are used by the NS entity to select amongst the unblocked NS-VCs within the group, addressed by means of the NSEI, where to send the NS SDU. The ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.5 NS-VC management function | The NS-VC management function is responsible for the blocking / unblocking, reset and test of NS-VCs. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.5.1 Blocking / unblocking of an NS-VC | When a condition making an NS-VC unavailable for NS user traffic is locally detected at the BSS or at the SGSN, the NS-VC shall be marked as blocked by the local NS entity and the remote NS peer entity shall be informed by means of a blocking procedure. The remote NS entity shall then mark the NS-VC as blocked and shal... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.5.2 Reset of an NS-VC | This procedure is used to reset one NS-VC to a determined state between remote entities. This procedure is performed: - when a new NS-VC is set-up; - after a processor re-start; - after a failure recovery when the state of an NS-VC must be set to blocked and alive; or - at any local event restoring an existing NS-VC in... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 4.5.3 Test of an NS-VC | The test procedure is used to check that end-to-end communication exists between peer NS entities on a given NS-VC. When end-to-end communication exists, the NS-VC is in the "alive" state, otherwise it is in the "dead" state. A dead NS- VC can not be in the "unblocked" state. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5 Elements for layer-to-layer communication | This chapter presents the Network Service in a generic way, no assumptions are made regarding the real protocols providing the network services. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.1 Service primitive model | The service primitive model shown in Figure 4/GSM 08.16 is applicable to both BSS and SGSN. Network Service Network Service user NS-SAP GSM 08.18 GSM 08.16 Figure 4/GSM 08.16: Network Service primitive model The network services are provided at the Network Service-Service Access Point (NS-SAP). ETSI ETSI TS 101 299 V7.... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2 Service primitives and parameters | The Network Service primitives are summarized in table 1/GSM 08.16. The general syntax of the Network Service primitives is: NS - Generic name - Type (Parameters) Table 1/GSM 08.16: Network Service primitives Generic name Type Parameters Request Indication Response Confirm UNITDATA X X - BVCI and NSEI - NS SDU - Link S... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.1 Primitives | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.1.1 NS-UNITDATA-Request | This primitive is used by the NS user entity to send a NS SDU to its peer entity via a BVC. The NS entity sends the NS SDU in unacknowledged mode. The Link Selector Parameter is used to identify the NS SDUs which must be sent in order relatively to each other. The NSEI is used by the NS entity to select the group of NS... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.1.2 NS-UNITDATA-Indication | This primitive is used by the NS entity to provide the NS user entity with a NS SDU received on a virtual connection. The NS SDU are received in unacknowledged mode. BVCI together with NSEI indicate which BVC the NS SDU was received on. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.1.3 NS-CONGESTION-Indication | The NS entity shall be able to detect when a congestion situation starts and ends on an NS-VC. This primitive is used by the NS entity to report to the NS user entity that congestion is detected or that the congestion situation has disappeared. The BVCI and NSEI of the affected BVC and the congestion cause are reported... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.1.4 NS-STATUS-Indication | There may be situations where an NS-VC becomes unavailable for NS user traffic. When this occurs, the NS user is informed of the degradation of the transfer capacity by means of this primitive including the "transfer capability" parameter. When an NS-VC previously unavailable for NS user traffic becomes available again... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2 Parameters | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.1 NS SDU | The NS SDUs are specified in GSM 08.18 [5]. They shall never be inspected by the Network Service entity. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.2 Link Selector Parameter | The Link Selector Parameter is included in the NS-UNITDATA-Request primitive for load sharing purposes as described in clause "Requirements on load sharing function". |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.3 BVCI I and NSEI | BVCI and NSEI parameters are included in the service primitives to identify the BVC for which the service is provided. These parameters are used by the NS entity to multiplex the NS SDUs over the NS-VCs. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.4 Congestion cause | The congestion cause shall indicate the affected direction of transmission and may be set to the following values: a) congestion detected, backward b) end of congestion, backward c) congestion detected, forward d) end of congestion, forward |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.