Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 43.064  Word version:  16.0.0

Top   Top   Up   Prev   Next
1…   3.3…   3.3.9…   4…   5…   6…   A…

 

3.3  Network and mobile station capabilities

3.3.1  General

In addition to GPRS specific definitions which can be found in TS 22.060 and TS 23.060 the following apply.
When referring to radio resources (i.e. physical channels) provided by the network to the mobile station, the term "assignment" refers to granting of resources on a semi-static basis, whereas "allocation" refers to the dynamically changing permission to use those resources that have been "assigned" to it and are shared with other users. An exception applies when granting resources using Fixed Uplink Allocation where only the term "allocation" is used. In this case, resources are assigned and allocated by the same message.
Multislot Capability:
the capability of the mobile station to support Multislot Configurations.
Multislot Class:
a value which implicitly determines the Multislot Capability of the mobile station.
Multislot Configuration:
the set of receive and transmit timeslots assigned to the MS.
Up

3.3.2  EGPRS mobile stationWord‑p. 12

An EGPRS mobile station is a GPRS mobile station with additional capabilities for new radio access protocol features and new modulation and coding schemes. An EGPRS mobile station shall comply with GPRS requirements and the additional requirements defined for an EGPRS mobile station. The support of EGPRS is optional for the mobile station and the network.
An EGPRS mobile station may additionally indicate support for EGPRS2 in uplink and/or downlink direction. In this case an EGPRS mobile station supports additional modulation and coding schemes, and may also support higher symbol rate, see sub-clause 3.3.6. The support of EGPRS2 is optional for the mobile station and the network.
An EGPRS mobile station may additionally indicate the support of Reduced Latency. In this case an EGPRS mobile station may be assigned a TBF with FANR activated either in BTTI configuration or in RTTI configuration, see sub-clause 3.3.5. The support of Reduced Latency is optional for the mobile station and the network.
Up

3.3.3  Dual Transfer Mode

In dual transfer mode, the mobile station is assigned resources providing an RR connection and one or more Temporary Block Flows on one or more physical channels. This feature is optional for the mobile station and the network. It is only applicable for a mobile station supporting GPRS, EGPRS or EGPRS2. Dual transfer mode is a subset of class A mode of operation, which is only possible if there is radio resource assignment co-ordination in the network.

3.3.4  Downlink dual carrier configuration |R7|

In a downlink dual carrier configuration, one or more PDCHs are assigned to a single MS on each of two different radio frequency channels on either the uplink or downlink, or both. On the downlink, radio blocks may be allocated on both radio frequency channels in any radio block period. On the uplink, radio blocks shall not be allocated on both radio frequency channels in any given radio block period.
A downlink dual carrier configuration shall support multislot configurations either for packet switched connections or dual transfer mode. For a Dual Transfer Mode capable MS which supports Downlink Dual Carrier, support of Downlink Dual Carrier configurations for Dual Transfer Mode is optional.
Downlink dual carrier is not supported in GPRS mode.
Up

3.3.5  Reduced Latency TBF |R7|

A TBF applying Reduced Latency shall operate according to all EGPRS/EGPRS2 requirements, unless otherwise stated, with the Fast Ack/Nack Reporting procedure (see sub-clause 3.3.5.1). In addition, a TBF applying Reduced Latency is characterized by either RTTI configuration or BTTI configuration (see sub-clause 3.3.5.2).

3.3.5.1  Fast Ack/Nack Reporting procedure

The Fast Ack/Nack reporting procedure (FANR) refers to the possibility to include, in a radio block for data transfer sent in one direction, piggy-backed ack/nack information relative to a TBF with FANR activated in the other direction.
This is achieved by inserting a fixed-size piggy-backed ack/nack (PAN) field in the radio block. When a PAN field is inserted, a suitable Puncturing Scheme variant for the modulation and coding schemes in use is chosen, so that the RLC data field and the PAN field fit together in the radio block along with the RLC/MAC header. The presence of the PAN field, is signalled by the PAN indicator bit in the RLC/MAC header. When this bit is set the receiver shall use the corresponding Puncturing Scheme variant of the CPS indicated in the RLC/MAC header to decode the RLC data field.
If a mobile station is assigned a TBF with FANR activated, all concurrent TBFs assigned to the mobile station shall have FANR activated irrespective of the RLC/MAC mode of each TBF (acknowledged mode, non-persistent mode or unacknowledged mode).
Fast Ack/Nack reporting is not supported in GPRS TBF mode.
Up

3.3.5.2  RTTI configurationWord‑p. 13

In RTTI configuration, a radio block consisting of four bursts is sent using two PDCHs, i.e. a PDCH-pair, in each of two consecutive TDMA frames. In RTTI configuration, the time to transmit a radio block is half of a basic radio block period.
In RTTI configuration, a downlink TBF assignment consists of a number of PDCH-pairs, each PDCH-pair comprising two PDCHs. In a downlink dual carrier configuration (see sub-clause 3.3.4), up to 8 PDCH-pairs may be assigned per TBF. In a single carrier configuration up to 4 PDCH-pairs may be assigned per TBF. Two PDCHs constituting a downlink PDCH-pair need not be contiguous.
In RTTI configuration, an uplink TBF assignment consists of up to four PDCH-pairs. The two PDCHs constituting an uplink PDCH-pair need not be contiguous.
The PACCH shall have the same TTI configuration as the TBF with which it is associated.
In each direction PDCH-pairs cannot be assigned so that they are partially overlapped, i.e. two different PDCH-pairs cannot have one PDCH in common.
For an uplink TBF in RTTI configuration USFs can be sent in one of two ways:
  • RTTI USFs: a USF is sent in one reduced radio block period, i.e. a USF is mapped on four bursts transmitted on a downlink PDCH-pair during two consecutive TDMA frames. The USF allocates resources for one or four uplink radio blocks in the next reduced radio block period(s), depending on the value of USF_GRANULARITY.
  • BTTI USFs: two USFs are sent in a basic radio block period. One USF is mapped on four bursts transmitted on the first PDCH of a downlink PDCH-pair during four consecutive TDMA frames. This USF allocates resources for one or four uplink radio blocks in the first 2 TDMA frames of the next basic radio block period(s), depending on the value of USF_GRANULARITY. A second USF is mapped on four bursts transmitted on the second PDCH of a downlink PDCH-pair during four consecutive TDMA frames. This USF allocates resources for one or four uplink radio blocks in the second 2 TDMA frames of the next basic radio block period(s), depending on the value of USF_GRANULARITY.
For each TBF, the network signals the corresponding TTI configuration (i.e. either basic or reduced) at TBF establishment/ reconfiguration. In case of RTTI configuration, the network also signals at uplink TBF establishment/reconfiguration the USF mode (i.e. either RTTI or BTTI) to be used for that TBF.
For each assigned uplink PDCH-pair, the network may signal at TBF establishment/reconfiguration the "corresponding downlink PDCH-pair", i.e. the DL PDCH-pair where USFs and PACCH/D are monitored. The timeslot numbers of the PDCHs constituting an uplink PDCH-pair may be different from those of the PDCHs constituting the corresponding downlink PDCH-pair. If no indication is provided, the corresponding downlink PDCH-pair will be the one with the same timeslot numbers as the uplink PDCH-pair.
On a given downlink PDCH-pair all USFs shall be sent with the same USF mode.
For a given mobile station, in each direction, the same TTI configuration shall be used for all TBFs (and PACCHs) assigned with one or more PDCH(s) in common in that direction. If a TBF is assigned on completely different PDCH(s) the TTI used may be different.
For a given mobile station, different uplink TBFs may use different USF modes if assigned on completely different PDCH(s).
A PDCH may be shared between RTTI TBF and BTTI TBF (assigned to different mobile stations). Alternatively, both PDCHs forming a PDCH-pair may be assigned to only support RTTI TBFs.
RTTI configuration is not supported in GPRS TBF mode.
Up

3.3.6  EGPRS2 mobile station |R7|Word‑p. 14

An EGPRS2 mobile station is an EGPRS mobile station supporting additional modulation and coding schemes on the downlink and/or the uplink. An EGPRS2 mobile station shall comply with GPRS requirements and the additional requirements defined for an EGPRS mobile station. The support of EGPRS2 is optional for the mobile station and the network.
EGPRS2 features can be supported independently in the downlink and in the uplink.
An EGPRS2 mobile station may additionally indicate the support of Reduced Latency. In this case an EGPRS2 mobile station may be assigned a TBF applying Reduced Latency, see sub-clause 3.3.5. The support of Reduced Latency is optional for the mobile station and the network.
Up

3.3.6.1  EGPRS2 in the downlink

A mobile station supporting EGPRS2 in the downlink supports additional modulation and coding schemes on the downlink.
3.3.6.1.1  EGPRS2-A and EGPRS2-B in the downlink.
Two levels of support are defined for the EGPRS2 feature in the downlink: EGPRS2-A and EGPRS2-B. EGPRS2-A includes additional modulation and coding schemes. EGPRS2-B includes additional modulation and coding schemes as well as a higher symbol rate. For a MS, support of EGPRS2-B in the downlink implies support of EGPRS2-A in the downlink.

3.3.6.2  EGPRS2 in the uplink

A mobile station supporting EGPRS2 in the uplink supports additional modulation and coding schemes on the uplink.
3.3.6.2.1  EGPRS2-A and EGPRS2-B in the uplink
Two levels of support are defined for the EGPRS2 feature in the uplink: EGPRS2-A and EGPRS2-B. EGPRS2-A includes additional modulation and coding schemes. EGPRS2-B includes additional modulation and coding schemes as well as a higher symbol rate. For a MS, support of EGPRS2-B in the uplink implies support of EGPRS2-A in the uplink.

3.3.7  Downlink multi carrier configuration |R12|

In a downlink multi carrier configuration, one or more PDCHs are assigned to a single MS on each of up to 16 different downlink radio frequency channels, depending on the MS capability. On the downlink, radio blocks may be allocated on all assigned radio frequency channels in any given radio block period. On the uplink, radio blocks shall only be allocated on one radio frequency channel in any given radio block period.
The MS shall monitor the assigned PDCHs on the assigned and selected radio frequency channels in a DLMC configuration. Which radio frequency channels that are selected depends on the maximum carrier separation supported by the MS and the ARFCNs of the radio frequency channels in a given radio block period.
A MS indicating support for downlink multi carrier may optionally indicate support for non-contigous intra-band reception and /or inter-band receception. In case of inter-band reception radio frequency channels are assigned in two different frequency bands. Inter band reception is only supported in multiband operatation. In non-contigous intra-band reception the assigned radio frequency channels are grouped into two separate groups during each TDMA frame, where the carrier separation indicated by the maximum bandwidth applies in each group.For a MS in Downlink Multi Carrier configuration, fallback to reception of a single radio frequency channel, irrespective of the number of assigned radio frequency channels is performed with regular periodicity.
A downlink multi carrier configuration shall support multislot configurations for packet swiched connections.
Dual Transfer Mode is not supported in downlink multi carrier configurations.
Downlink multi carrier is not supported in GPRS mode.
Up

3.3.8  Power Efficient Operation (PEO) |R13|Word‑p. 15

3.3.8.1  General

Power Efficient Operation (PEO) is used by a MS to reduce its power consumption through the use of relaxed mobility related requirements and extended DRX (eDRX) or Power Saving Mode (PSM). A PEO capable MS shall support at least one of eDRX or PSM. When eDRX or PSM has been successfully negotiated a PEO capable MS can choose to enable PEO in a cell that supports PEO in which case it enables the use of relaxed mobility related requirements and use the EGPRS PACKET CHANNEL REQUEST message indicating 'PEO One Phase Access Request' when attempting packet access.
The mobility related requirements for a MS that has enabled PEO are relaxed compared to a MS that has not enabled PEO, and are referred to as relaxed mobility related requirements. The relaxation includes:
  • No periodic measurements of the serving and non-serving cells are required.
    • Measurements of only the serving cell need to be performed before each time the paging block is monitored or each uplink transmission;
    • Measurements for cell reselection are only triggered if at least one, out of a set of criteria used to determine the suitability of the serving cell, is fulfilled based on the measurements of the serving cell.
    • Fewer non-serving cells, compared to MS not in PEO, need to be considered in measurements for cell reselection;
  • System Information (SI) acquisition required only before each time the paging block is monitored or each uplink transmission and in this case only if more than 24 h have passed since last acquisition, or, a change in SI is detected;
  • Only autonomous cell reselection supported in idle mode;
  • No mobility related procedures need to be supported in packet transfer mode and no neighbour cell measurements need to be performed when in packet transfer mode.
For more detailed procedures, see TS 45.008.
A cell indicates its support of PEO in the SI13 Rest Octets IE, see TS 44.018. In this case it supports the reception of an EGPRS PACKET CHANNEL REQUEST message indicating 'PEO One Phase Access Request' (see TS 44.018 and TS 44.060) from a MS attempting packet access.
When eDRX is supported, the number of blocks per 51-multiframe reserved for AGCH is subject to the requirement that all cells in the routing area shall have the same number of paging blocks per 51-multiframe (see TS 45.002). DTM is not supported in PEO.
Support of PEO is optional for the MS and the network. The MS shall disable PEO in case it enters a cell that does not support PEO. The MS may also disable PEO (see TS 45.008) at any time, in which case it operates as if it was in a cell that does not support PEO. A MS that chooses to disable PEO shall disable the use of relaxed mobility related requirements and the EGPRS PACKET CHANNEL REQUEST message indicating 'PEO One Phase Access Request'.
PEO makes use of a 9 bit BSIC wherein the 6 bit BSIC is supplemented with a 3 bit Radio frequency Colour Code with the purpose to help distinguish between cells in tight frequency reuse networks.
A PEO capable mobile station may support deferred System Information acquisition (see subclause 3.3.8.2).
Up

3.3.8.2  Deferred System Information Acquisition for PEO |R15|Word‑p. 16

In order to reduce energy consumption in packet idle mode, the network may broadcast information to assist the MS to apply deferred SI acquisition for PEO (see TS 45.008).
To this purpose it reconfigures SI 13 for a given cell to include the PEO Idle Mode Mobility Cell Group Description comprising cells, geographically adjacent or close to each other, with shared cell parameters related to cell (re)selection, Routing Area assignment, paging monitoring, mobility support and cell barring and assigns it a broadcast frequency list containing BCCH carriers allocated in these cells. To better match cell deployments, some cell parameters may deviate from the common values and are separately indicated on a per cell basis (see TS 44.018).
To allow for different settings of shared cell parameters in geographic adjacent areas, different PEO Idle Mode Mobility (IMM) cell groups are defined with an identifier to distinguish one from the other, thus providing a spatially definite assignment of cells to PEO IMM cell groups. Since values of shared or non-shared cell parameters in a particular PEO IMM cell group are subject to change in time, a change mark is assigned to the PEO IMM cell group. An increment of the change mark for a particular PEO IMM cell group hence indicates to the MS the requirement to acquire the complete SI in the serving cell.
To enable fast detection if a non-serving cell, subject to BSIC identification for the purpose of identifying candidates for cell reselection in idle mode, is part of a given PEO IMM cell group or not, the PEO IMM Cell Group Identifier and the related PEO IMM Change Mark are sent in AGCH/PCH messages along with RCC being required for BSIC identification.
Thus, an MS supporting deferred SI acquisition for PEO reads AGCH/PCH messages of a non-serving cell to identify both the PEO IMM Cell Group Identifier and the PEO IMM Change mark. If both values match with those of the serving cell, it will not need to read the BCCH for this cell prior to the decision for cell reselection, neither after cell reselection to this cell for subsequent cell reselections and for paging monitoring in packet idle mode. Only in case a matching page is received (matching IMSI or P-TMSI of the MS), that requires to send a paging response, or the MS needs to perform an uplink data transmission, or a timeout since the last reading of the complete SI in a different than the serving cell (current cell) is expired, the MS is required to read the complete System Information in the serving cell.
The network may choose to deactivate deferred SI acquisition for PEO in network deployments for which System Information needs to be reconfigured more frequently or for which adjacent cells' idle mode mobility parameters differ too much. The support of deferred SI acquisition for PEO is broadcasted in System Information (SI 13).
Up

Up   Top   ToC