hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.3 Information Transfer | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.3.1 Information Data | Information is conveyed using UI or UIH frames. Support of UIH frames is mandatory and support of UI frames is optional. UI frames are used when it is important to know that data received is correct. An example of the use of UI frames is in carrying IP (Internet Protocol) traffic where error recovery procedures are per... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.3.2 Priority | Each data stream has a priority associated with it. The priority is a number in the range 0-63 with lower numbers having higher priority. The TE assigns a priority to each DLC and informs the MS of the priority by means of the multiplexer control channel (see subclause 5.4.6.3.1). In the absence of a message assigning ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.4 Frame Variables | The poll (P) bit set to 1 shall be used by a station to solicit (poll) a response or sequence of responses from the other station. The final (F) bit set to 1 shall be used by a station to indicate the response frame transmitted as the result of a soliciting (poll) command. The poll/final (P/F) bit shall serve a functio... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.4.1 Functions of the poll bit | The P bit set to 1 shall be used to solicit a response frame with the F bit set to 1 from the other station at the earliest opportunity. On a particular DLCI, only one frame with a P bit set to 1 shall be outstanding in a given direction at a given time. In the case where a SABM or DISC command with the P bit set to 0 ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.4.2 Functions of the final bit | A response frame with the F bit set to 1 shall be used by a station to acknowledge the receipt of a command frame with the P bit set to 1. The response shall be made at the earliest opportunity. The station may transmit response frames with the F bit set to 0 at any opportunity on an asynchronous basis. However, in the... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.5 Time-out considerations | In order to detect a no-reply or lost-reply condition, each station shall provide a response time-out function (T1). The expiry of the time-out function shall be used to initiate appropriate error recovery procedures. The duration of the time-out function in the two stations shall be unequal in order to resolve content... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6 Multiplexer Control Channel | At the initiation of communication between the TE and MS a control channel is set up with DLCI 0 using the procedures of subclause 5.8.1. This channel is used to convey information between the two multiplexers. The control channel may use either error recovery mode or non-error recovery mode procedures as defined by th... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.1 Message format | All messages sent between the multiplexers conform to the following type, length, value format: Type Length Value 1 Value2 … Value n Each box in the diagram represents a field of minimum size one octet. The type and length octets have extension bits so those fields may contain more than one octet. The first type field ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.2 Operating procedures | Messages always exist in pairs; a command message and a corresponding response message. If the C/R bit is set to 1 the message is a command, if it is set to 0 the message is a response. A response message has the same T bits as the command that provoked it. If a command does not produce a response within a time T2 the ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3 Message Type and Actions | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.1 DLC parameter negotiation (PN) | This procedure is optional. If this command is not supported, default values are applied to each DLC. Before a DLC is set up using the mechanism in subclause 5.4.1, the TE and MS must agree on the parameters to be used for that DLC. These parameters are determined by parameter negotiation. The parameter negotiation use... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.2 Power Saving Control (PSC) | (see also subclause 5.4.7) The power saving control messages use the following type field octet: ETSI TS 101 369 V6.3.0 (1999-03) 28 (GSM 07.10 version 6.3.0 Release 1997) Bit 1 2 3 4 5 6 7 8 EA C/R 0 0 0 0 1 0 The length byte contains the value 0 and there are no value octets. If a station wishes to enter a low-power ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.3 Multiplexer close down (CLD) | (see also subclause 5.8.2) The multiplexer close down command is used to reset the link into normal AT command mode without multiplexing. The multiplexer close down messages use the following type field octet: Bit 1 2 3 4 5 6 7 8 EA C/R 0 0 0 0 1 1 The length byte contains the value 0 and there are no value octets. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.4 Test Command (Test) | The test command is used to test the connection between MS and the TE. The length byte describes the number of values bytes, which are used as a verification pattern. The opposite entity shall respond with exactly the same value bytes. The type field octet has the following format: Bit 1 2 3 4 5 6 7 8 EA C/R 0 0 0 1 0 ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.5 Flow Control On Command (FCon) | The flow control command is used to handle the aggregate flow. When either entity is able to receive new information it transmits this command. The length byte contains the value 0 and there are no value octets The type field octet has the following format: Bit 1 2 3 4 5 6 7 8 EA C/R 0 0 0 1 0 1 |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.6 Flow Control Off Command (FCoff) | The flow control command is used to handle the aggregate flow. When either entity is not able to receive information it transmits the FCoff command. The opposite entity is not allowed to transmit frames except on the control channel (DLC=0). The length byte contains the value 0 and there are no value octets The type fi... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.7 Modem Status Command (MSC) | It is desired to convey virtual V.24 control signals to a data stream, this is done by sending the MSC command. The MSC command has one mandatory control signal byte and an optional break signal byte. This command is only relevant when the basic option is chosen. This command shall be sent prior to any user data after ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.8 Non Supported Command Response (NSC) | This response is sent whenever a command type is not supported by the receiving entity. The length byte contains the value 1 and there is one value octets. The type field octet has the following format: Bit 1 2 3 4 5 6 7 8 EA C/R 0 0 1 0 0 0 The value octet contains the Command Type of the non supported command. The va... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.9 Remote Port Negotiation Command (RPN) | This command is optional. This command is used for set the remote port communication settings. All devices must assure that the communication settings are correctly set, prior sending data. There are default values assigned on all parameters, if no negotiation is performed, the default value is chosen. During a connect... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.10 Remote Line Status Command(RLS) | This command is optional. This command is used for indicate remote port line status. During a connection, a device must send the RLS whenever the Remote Port Line Status are changed. The Remote Line Status command use the following type field octet: ETSI TS 101 369 V6.3.0 (1999-03) 35 (GSM 07.10 version 6.3.0 Release 1... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.6.3.11 Service Negotiation Command (SNC) | This command is used to query and set a specific service on a specific DLC. It is for instance used to set specific digital voice types. In some situations it is not very suitable to mix AT commands and raw data on the same DLC. For those situations, special DLCs can be established and converted to carry a specific dat... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.7 Power Control and Wake-up Mechanisms | It is very important in many types of MS and some TE that the power consumed by the equipment is minimised. This aim is often achieved by entering various power-saving states under conditions of inactivity, for example. The multiplexer system must be able to close down cleanly if either TE or MS wish to enter a low-pow... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.8 Flow Control | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.8.1 RTR Flow Control | Figure 12 shows a DTE connection to a DCE. The flow control scheme defined in this section also applies to DTE - DTE connections. Both 07.10 entities are configured to use RTR (RFR/CTS) flow control. The flow control signal to the local application is a combination of the RTR signal from the opposite device together wi... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.8.2 XON/XOFF Flow Control | Some 07.10 instance may detect XON/OFF characters coming from the local application when XON/XOFF is enabled. In this case the characters are acted upon, but not forwarded to the opposite 07.10 instance i.e. the XON/XOFF characters are filtered out and the flow control signal is transferred as a 07.10 flow signal, see ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.5 Convergence Layers | Convergence layers are defined to permit data which has implied structure to be conveyed through the multiplexer without losing the structure or other parameters which are associated with the data stream. Common uses of convergence layers are to carry the state of V.24 control signals through a DLC or to ensure that th... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.5.1 Type 1 - Unstructured Octet Stream | Data which consists of an unstructured sequence of octets, for example, 64 kbit/s uncoded voice or normal asynchronous data without V.24 control signals, is inserted directly into the I-field. In this case, it could be said that the convergence layer is null. Type 1 is the default convergence layer for each DLC. 5.5.2 ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.5.3 Type 3 - Uninterruptible Framed Data | An example of uninterruptible framed data is coded voice data made up of a sequence of voice frames. It is important that coded voice frames reach the voice decoder with the frame structure intact and with the shortest possible delay. The simplest way of ensuring this is to map one complete voice frame into one I-field... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.5.4 Type 4 - Interruptible Framed Data | This type of convergence layer is used might be used to convey data which has an implied structure but where the delay is not as important as Type 3. The structured data may be segmented across several frames and re-assembled at the other station. PPP-framed IP data is an example of the type of data that could be carri... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.6 DLCI Values | All DLCs use a type 1 convergence layer by default; the use of other layers may be negotiated using the multiplexer control channel. Table 27: DLCI Assignments Usage DLCI number (decimal) Priority Multiplexer control channel 0 0 AT commands (07.07 and 07.05) 1-7 7 AT commands (07.07 and 07.05) 8-15 15 AT commands (07.0... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7 System Parameters | The following system parameters are defined for the multiplexer. T1, N1, N2 and k may be negotiated by use of the multiplexer control channel or the default values given here should be used. T2 and T3 are set with the AT+CMUX command. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.1 Acknowledgement Timer (T1) | The acknowledgement timer governs the amount of time that a station will wait for an acknowledgement before resorting to other action (e.g. transmitting a frame). The two stations may operate with different values of T1. ETSI TS 101 369 V6.3.0 (1999-03) 43 (GSM 07.10 version 6.3.0 Release 1997) The units are hundredths... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.2 Maximum Frame Size (N1) | N1 defines the maximum number of octets that that may be contained in an information field. It does not include octets added for transparency purposes. The default value is 64 octets when the advanced option activated and 31octets when it is not activated. The range is 1 to 32768 octets. NOTE: The maximum frame size sh... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.3 Maximum number of retransmissions (N2) | N2 defines the maximum number of times that a station re-attempt a procedure requiring a response. The two stations may operate with a different value of N2. The default value is 3 and the range is 0-255. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.4 Window Size (k) | The window size parameter (k) defines the maximum number of I frames that a DLC can have outstanding (i.e. unacknowledged). Identical values need not be used for each direction. The window size may not be larger than 7. This parameter is only applicable when Error Recovery Option is activated. See clause 6. The default... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.5 Response Timer for multiplexer control channel (T2) | The T2 timer is the amount of time the multiplexer control channel waits before re-transmitting a command. T2 must be greater than T1. The units are hundredths of a second. Times of up to 2.55 seconds may be used. The default value is 300 ms and minimum 20 ms. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.7.6 Response Timer for wake-up procedure(T3) | The T3 timer is the amount of time the transmitting station of a power wake-up command waits before raising an alarm when no response is received. The units are seconds. Times of up to 255 seconds may be used. The default value is 10 s and minimum 1 s. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.8 Start-up and close-down of multiplexer | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.8.1 Start-up procedure | Multiplexer operation is started by the use of the +CMUX command (see GSM 07.07). This command instructs the multiplexer to start up the multiplexer control channel (see subclause 5.8.1) using either error recovery mode or non- error recovery mode. The TE multiplexer initiates the establishment of the multiplexer contr... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.8.2 Close-down procedure | Initiation of the close-down will come from higher layers in either the TE or MS and is outside the scope of this specification. Once the command to close down is received the multiplexer will close down each DLC in turn using the procedures of subclause 5.4.2. When all DLCs (except the multiplexer control channel - DL... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6 Error Recovery Mode Option | When the Advanced option is selected an error recovery mechanism may be used for better security. The error-recovery mode is optional and is intended for those cases where the quality of the TE-MS link can not be guaranteed and/or when the integrity of the data to be transmitted is critical. Some DLCs may use error rec... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.1 Frame Types | Table 28: Coding of Control Field Frame Type 1 2 3 4 5 6 7 8 I (Information) 0 N(S) P/F N(R) RR (Receive Ready) 1 0 0 0 P/F N(R) RNR (Receive Not Ready) 1 0 1 0 P/F N(R) REJ (Reject) 1 0 0 1 P/F N(R) N(R) and N(S) are receive and send sequence numbers, respectively. They are described later in the present document. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.1.1 Information transfer, I, command and response | The function of the information, I, command and response shall be to transfer sequentially numbered frames, each containing an information field, across a data link. The encoding of the I command/response control field shall be as shown in table 28. The I frame control field shall contain two sequence numbers: - N(S), ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.1.2 Receive ready, RR, command and response | The receive ready, RR, frame shall be used by a station to a) indicate that it is ready to receive an I frame; and b) acknowledge previously received I frames numbered up to N(R) - 1 inclusive. ETSI TS 101 369 V6.3.0 (1999-03) 45 (GSM 07.10 version 6.3.0 Release 1997) When transmitted, the RR frame shall indicate the c... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.1.3 Receive not ready, RNR, command and response | The receive not ready, RNR, frame shall be used by a station to indicate a busy condition; i.e., temporary inability to accept subsequent I frames. I frames numbered up to N(R) - 1 inclusive shall be considered as acknowledged. The I frame numbered N(R) and any subsequent I frames received, if any, shall not be conside... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.1.4 Reject, REJ, command and response | The reject, REJ, frame shall be used by a station to request retransmission of I frames starting with the frame numbered N(R). I frames numbered N(R) - 1 and below shall be considered as acknowledged. Additional I frames awaiting initial transmission may be transmitted following the retransmitted I frame(s). With respe... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2 Procedure and State | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1 Frame state variables and sequence numbers | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.1 General | Each station shall maintain an independent send state variable V(S) for the frames it transmits and an independent receive state variable V(R) for the I frames it sends to and receives from another station. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.2 Send state variable V(S) | The send state variable denotes the sequence number of the next in-sequence I frame to be transmitted. The send state variable can take the value 0 to 7 inclusive. The value of the send state variable shall be incremented by one with each successive I frame transmission, but shall not exceed N(R) of the last received f... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.3 Send sequence number N(S) | Only I frames shall contain N(S), the send sequence number of transmitted frames. Prior to transmission of an I frame, N(S) shall be set equal to the value of the send state variable. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.4 Receive state variable V(R) | The receive state variable denotes the sequence number of the next I frame expected to be received. The receive state variable can take the value 0 to 7 inclusive. The value of the receive state variable shall be incremented by one on receipt of an error-free I frame whose send sequence number N(S) equals the receive s... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.5 Receive sequence number N(R) | All frames which contain N(R) (see Table 28) shall indicate the N(S) sequence number of the next expected I frame. Prior to transmission of a frame containing N(R), the N(R) shall be set equal to the current value of the receive state variable. The N(R) indicates that the station transmitting the N(R) has correctly rec... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.1.6 Use of the P/F bit to assist in error recovery | As the P and F bits set to 1 are always exchanged as a pair (for every P bit there shall be one F bit, and another P bit shall not be issued until the previous P bit has been matched with an F bit, and, similarly, another F bit shall not be issued until another P bit is received), the N(R) contained in a received frame... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2 Exchange of information (I) frames | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.1 Sending I frames | The control field format shall be as defined in subclause 6.1 for an I frame, with N(S) set to the value of the send state variable V(S) and with N(R) set to the value of the receive state variable V(R). Following data link set-up, both V(S) and V(R) shall be set to zero. The maximum length of the information field in ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.2 Receiving I frames | After a station receives correctly an I frame [i.e., N(S) equals the value of the receive state variable V(R)] that it can accept, the station shall increment its receive state variable V(R), and, at its next opportunity to send, take one of the following actions: - if information is available for transmission and the ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.3 Reception of incorrect frames | If a frame is received with an incorrect FCS, it shall be discarded. If an I frame is received with a correct FCS but with an incorrect N(S), the receiving station shall ignore the N(S) field and discard the information field in that frame. This shall continue until the expected I frame is received correctly. ETSI TS 1... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.4 Station receiving acknowledgements | A station receiving an I, RR, or RNR frame with a valid N(R) = x shall treat as acknowledged all previously transmitted I frames up to and including the I frame transmitted with N(S) equal to x - 1. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5 Exception conditions and recovery | The following procedures are available to effect recovery following the detection/occurrence of an exception condition at the data link layer. The exception conditions described are those situations which may occur as the result of transmission errors, data station malfunction or operational situations. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.1 Busy | The busy condition shall result when a station is temporarily unable to receive, or unable to continue to receive, I frames due to internal constraints; for example, receive buffering limitations. In this case, an RNR frame shall be transmitted with the N(R) number of the next I frame that is expected. Traffic awaiting... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.2 N(S) sequence error | An N(S) sequence error exception condition shall occur in the receiver when an I frame that is received error free (no FCS error) contains an N(S) that is not equal to the receive state variable at the receiver. The receiver shall not acknowledge (i.e., not increment its receive state variable) the frame causing the se... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.3 Poll/final (P/F) bit (checkpoint) recovery | When a data station receives a frame with the P/F bit set to 1, it shall initiate retransmission of unacknowledged I frames previously transmitted with sequence numbers that are less than the V(S), send state variable, value that was current at the time of transmission of the last frame with the P/F bit, respectively, ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.4 REJ recovery | The REJ command/response shall be used primarily to initiate an exception recovery (retransmission), following the detection of a sequence error, earlier than is possible by checkpoint (P/F bit) recovery; for example, if a REJ frame is immediately transmitted upon detection of a sequence error, then there is no require... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.5 SABM Command | When this command is actioned, the responsibility for all unacknowledged I frames assigned to data link control reverts to a higher layer. Whether the content of the information field of such unacknowledged I frames is reassigned to data link control for transmission or not is decided at a higher layer. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 6.2.2.5.6 DISC Command | When this command is actioned, the responsibility for all unacknowledged I frames assigned to data link control reverts to a higher layer. Whether the content of the information field of such unacknowledged I frames is reassigned to data link control for transmission or not is decided at a higher layer. ETSI TS 101 369... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 1 Scope | The present document provides the overall description for lower-layer functions of the General Packet Radio Service (GPRS) radio interface (Um). The overall description provides the following information: - The services offered to higher-layer functions, - The distribution of required functions into functional groups, ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 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... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 3 Abbreviations, symbols and definitions | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 3.1 Abbreviations | In addition to abbreviations in GSM 01.04 and GSM 02.60 the following abbreviations apply: BCS Block Check Sequence BEC Backward Error Correction BH Block Header CS Coding Scheme CU Cell Update FH Frame Header GGSN Gateway GPRS Support Node LLC Logical Link Control MAC Medium Access Control NCH Notification Channel (fo... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: Gb Interface between an SGSN and a BSC. Um Interface between MS and GPRS fixed network part. The Um interface is the GPRS network interface for providing packet data services over the radio to the MS. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 3.3 Definitions | GPRS specific definitions can be found in 02.60 and 03.60. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4 Packet data logical channels | 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. ETSI ETSI TS 101 350 V7.0.0 (1999-07) 10 (GSM 03.64 version 7.0.0 Release 1998) |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.1 General | This subclause describes the packet data logical channels that are supported by the radio subsystem. The packet data logical channels are mapped onto the physical channels that are dedicated to packet data. The physical channel dedicated to packet data traffic is called a Packet Data Channel (PDCH). |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.2 Packet Common Control Channel (PCCCH) | PCCCH comprises logical channels for common control signalling used for packet data as described in the following subclauses. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.2.1 Packet Random Access Channel (PRACH) - uplink only | PRACH is used by MS to initiate uplink transfer for sending data or signalling information. Packet Access burst and Extended Packet Access burst are used on PRACH [12]. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.2.2 Packet Paging Channel (PPCH) - downlink only | PPCH is used to page an MS prior to downlink packet transfer. PPCH uses paging groups in order to allow usage of DRX mode. PPCH can be used for paging of both circuit switched and packet data services. The paging for circuit switched services on PPCH is applicable for class A and B GPRS MSs in Network operation mode I,... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.2.3 Packet Access Grant Channel (PAGCH) - downlink only | PAGCH is used in the packet transfer establishment phase to send resource assignment to an MS prior to packet transfer. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.2.4 Packet Notification Channel (PNCH) - downlink only | PNCH is used to send a PTM-M (Point To Multipoint - Multicast) notification to a group of MSs prior to a PTM-M packet transfer. DRX mode shall be provided for monitoring PNCH. Furthermore, a “PTM-M new message” indicator may optionally be sent on all individual paging channels to inform MSs interested in PTM-M when the... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.4 Packet Traffic Channels | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.4.1 Packet Data Traffic Channel (PDTCH) | PDTCH is a channel allocated for data transfer. It is temporarily dedicated to one MS or to a group of MSs in the PTM-M case. In the multislot operation, one MS may use multiple PDTCHs in parallel for individual packet transfer. All packet data traffic channels are uni-directional, either uplink (PDTCH/U), for a mobile... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.5 Packet Dedicated Control Channels | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.5.1 Packet Associated Control Channel (PACCH) | PACCH conveys signalling information related to a given MS. The signalling information includes e.g. acknowledgements and power control information. PACCH carries also resource assignment and reassignment messages, comprising the assignment of a capacity for PDTCH(s) and for further occurrences of PACCH. The PACCH shar... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.5.2 Packet Timing advance Control Channel, uplink (PTCCH/U) | PTCCH/U is used to transmit random access burst to allow estimation of the timing advance for one MS in packet transfer mode. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 4.5.3 Packet Timing advance Control Channel, downlink (PTCCH/D) | PTCCH/D is used to transmit timing advance information updates to several MS. One PTCCH/D is paired with several PTCCH/U’s. 5 Mapping of packet data logical channels onto physical channels NOTE: The text in this clause is informative. The normative text is in GSM 05.02 [11]. Where there is a conflict between these desc... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.1 General | Different packet data logical channels can occur on the same physical channel (i.e. PDCH). The sharing of the physical channel is based on blocks of 4 consecutive bursts, except for PTCCH. The mapping in frequency of PDCH on to the physical channel shall be as defined in GSM 05.02. On PRACH and PTCCH/U, access bursts a... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.2 Packet Common Control Channels (PCCCH) | At a given time, the logical channels of the PCCCH are mapped on different physical resources than the logical channels of the CCCH. The PCCCH does not have to be allocated permanently in the cell. Whenever the PCCCH is not allocated, the CCCH shall be used to initiate a packet transfer. One given MS may use only a sub... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.2.1 Packet Random Access Channel (PRACH) | The PRACH is mapped on one or several physical channels. The physical channels on which the PRACH is mapped are derived by the MS from information broadcast on the PBCCH or BCCH. PRACH is determined by the Uplink State Flag marked as free that is broadcast continuously on the corresponding downlink (see subclause 6.6.4... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.2.2 Packet Paging Channel (PPCH) | The PPCH is mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2), as it is done for the PCH. The physical channels on which the PPCH is mapped, as well as the rule that is followed on the physical channels, are derived by the MS from info... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.2.3 Packet Access Grant Channel (PAGCH) | The PAGCH is mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2). The physical channels on which the PAGCH is mapped, as well as the rule that is followed on the physical channels, are derived by the MS from information broadcast on the ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.2.4 Packet Notification Channel (PNCH) | The PNCH is mapped on one or several blocks on PCCCH. The exact mapping follows a predefined rule. The mapping is derived by the MS from information broadcast on the PBCCH. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.3 Packet Broadcast Control Channel (PBCCH) | The PBCCH shall be mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2), as it is done for the BCCH. The existence of the PCCCH, and consequently the existence of the PBCCH, is indicated on the BCCH. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.4 Packet Timing advance Control Channel (PTCCH) | Two defined frames of multiframe are used to carry PTCCH (see subclause 6.1.2). The exact mapping of PTCCH/U sub-channels and PTCCH/D shall be as defined in GSM 05.02. On PTCCH/U, access bursts are used. On PTCCH/D, four normal bursts comprising a radio block are used. |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.5 Packet Traffic Channels | |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.5.1 Packet Data Traffic Channel (PDTCH) | One PDTCH is mapped onto one physical channel. Up to eight PDTCHs, with different timeslots but with the same frequency parameters, may be allocated to one MS at the same time. ETSI ETSI TS 101 350 V7.0.0 (1999-07) 13 (GSM 03.64 version 7.0.0 Release 1998) |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.5.2 Packet Associated Control Channel (PACCH) | PACCH is dynamically allocated on the block basis on the same physical channel as carrying PDTCHs.However, one block PACCH allocation is used on the physical channel carrying only PCCCH, when the MS is polled to acknowledge the initial assignment message. PACCH is of a bi-directional nature, i.e. it can dynamically be ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.6 Downlink resource sharing | Different packet data logical channels can be multiplexed on the downlink on the same physical channel (i.e. PDCH). See details in GSM 05.02. The type of message which is indicated in the radio block header allows differentiation between the logical channels. Additionally, the MS identity allows differentiation between... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 5.7 Uplink resource sharing | Different packet data logical channels can be multiplexed on the uplink of the same physical channel (i.e. PDCH). See details in GSM 05.02. The type of message which is indicated in the radio block header, allows differentiation between the logical channels. Additionally, the MS identity allows differentiation between ... |
a02c9ef5f89363d47206d8defd4c4a56 | 101 350 | 6 Radio Interface (Um) | The logical architecture of the GPRS Um interface can be described using a reference model consisting of functional layers as shown in Figure 3. Layering provides a mechanism for partitioning communications functions into manageable subsets. Communication between the MS and the Network occurs at the Physical RF, Physic... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.