RB RE Speed

Resource Element:
Covered by 1 sub carrier and one symbol period i.e 1 Symbol

Resource Block:
Covered by 12 Subcarriers and 6 or 7 symbols(Based on Cyclic prefix)

We can calculate the capacity if we know the Bandwidth allocated,Modulation scheme used and Cyclic Prefix type.
Consider 
Bandwidth Allocated = 5MHz
Modulation Scheme = QPSK(2 its per symbol)
Cyclic prefix used = Normal Cyclic Prefix (7 symbols in a slot)

Capacity = No of bits transferred in a sub frame / Duration of the Subframe(i.e 1milli sec)

Calculation No of Bits transferred in a Subframe

Total number of Resource block in a slot = Bandwidth / (Each subcarrier bandwidth * no of subcarriers in a Resource Block) 
Bandwidth = 5Mhz
Each sub carrier width = 15Khz
No of sub carriers in a Resource Block = 12 (As 12 Subcarrier is 1 Resource block )

Calculation of total no of resource blocks in 5MHz Bandwidth

so Resource block in one slot = 5 Mhz / (15 KHz *12 ) = 27.77 (But used RBs will be 25 for 5MHz bandwidth)
so Total Resource block in one subframe = 2 * Resource blocks in a slot = 50 RBs

Calculation of total no of symbols/Resource Elements in 5MHz Bandwidth
Total no of symbols / Resource Elements = 50 * no of symbols(REs) in a Resource block
No of symbols(REs) in a resource block = 12 subcarrier * 7 symbols = 84 symbols(REs)
Total symbols(REs ) in 50 Resource blocks = 50 * 84 = 4200 Resource Elements.

****Calculation of total no of bits sent in 5MHz Bandwidth in one subframe ****

In one symbol we can send no of bits at a time which depends on the modulation scheme (like BPSK,QPSK ,64QAM
BPSK - 1 bit,QPSK - 2 bit ,64 QAM - 6bits in a Symbol/ Resource elements
We will consider QPSK Scheme so in one symbol 2bits we can send.
So 1 Symbol = 2 bits.

So total no of Bits sent in a subframe = 2 * 4200 = 8400 bits.

So capacity = 8400 / 1ms = 8.4 MBPS

So capacity in 5MHz Bandwidth with QPSK Modulation with normal cyclic Prefix is 8.4MBPS.

if Modulation scheme is BPSK, 1 bits in a symbol = 1 * 4200 / 1ms = 4.2 MBPS
if Modulation scheme is 64QAM , 6 bits in a symbol = 6 * 4200 / 1ms = 25.2 MBPS.

3GPP Specification Numbering

Specification Numbering

All 3GPP specifications have a specification number consisting of 4 or 5 digits. (e.g. 09.02 or 29.002).

The first two digits define the series, followed by 2 further digits for the 01 to 13 series or 3 further digits for the 21 to 55 series.

The full title, specification number and latest version number for every specification can be found in the current status list (warning: large file!).

An automated list of Specification numbers - with the Title and details of the Specification Group responsible.

The first category have numbers of the form: xx.9xx

The second category have numbers of the form:
xx.8xx (feasibility study reports, etc) or, more rarely,
30.xxx / 50.xxx (planning and scheduling)

Missing Specs: Click here to see those Specs not yet available following the most recent round of TSG meetings.

The 3GPP Specifications are stored on the file server as zipped MS-Word files. The filenames have the following structure:

SM[-P[-Q]]-V.zip

where the character fields have the following significance ...

S = series number - 2 characters (see the table below)
M = mantissa (the part of the spec number after the series number) - 2 or 3 characters (see below)
P = optional part number - 1 or 2 digits if present
Q = optional sub-part number - 1 or 2 digits if present
V = version number, without separating dots - 3 digits

So for example:

• 21900-320.zip is 3GPP TR 21.900 version 3.2.0
• 0408-6g0.zip is 3GPP TS 04.08 version 6.16.0
• 32111-4-410 is 3GPP TS 32.111 part 4 version 4.1.0
• 29998-04-1-100 is 3GPP TS 29.998 part 4 sub-part 1 version 1.0.0
  
  

Subject of specification series	3G and beyond / GSM (R99 and later)	GSM only (Rel-4 and later)	GSM only (before Rel-4)
General information (long defunct)			00 series
Requirements	21 series	41 series	01 series
Service aspects ("stage 1")	22 series	42 series	02 series
Technical realization ("stage 2")	23 series	43 series	03 series
Signalling protocols ("stage 3") - user equipment to network	24 series	44 series	04 series
Radio aspects	25 series	45 series	05 series
CODECs	26 series	46 series	06 series
Data	27 series	47 series (none exists)	07 series
Signalling protocols ("stage 3") -(RSS-CN) and OAM&P and Charging (overflow from 32.- range)	28 series	48 series	08 series
Signalling protocols ("stage 3") - intra-fixed-network	29 series	49 series	09 series
Programme management	30 series	50 series	10 series
Subscriber Identity Module (SIM / USIM), IC Cards. Test specs.	31 series	51 series	11 series
OAM&P and Charging	32 series	52 series	12 series
Access requirements and test specifications		13 series (1)	13 series (1)
Security aspects	33 series	(2)	(2)
UE and (U)SIM test specifications	34 series	(2)	11 series
Security algorithms (3)	35 series	55 series	(4)
LTE (Evolved UTRA) and LTE-Advanced radio technology	36 series	-	-
Multiple radio access technology aspects	37 series	-	-

Note (1): The 13 series GSM specifications relate to European-Union-specific regulatory standards. On the closure of ETSI TC SMG, responsibility for these specifications was transferred to ETSI TC MSG, (Mobile Specification Group) and they do not appear on the 3GPP file server.

Note (2): The specifications of these aspects are spread throughout several series.

Note (3): Algorithms may be subject to export licensing conditions. See the relevant 3GPP page. See also the relevant ETSI pages.

Note (4): The original GSM algorithms are not published and are controlled by the GSM Association.

Technical Reports are of two classes:

• Those intended to be transposed and issued by the Organizational Partners as their own publications; and

• Those not intended for publication but which are simply 3GPP internal working documents, used, for example, for documenting planning and scheduling of work, or for holding the interim results of feasibility studies.

The first category have numbers of the form: xx.9xx

The second category have numbers of the form:
xx.8xx (feasibility study reports, etc) or, more rarely,
30.xxx / 50.xxx (planning and scheduling)

Missing Specs: Click here to see those Specs not yet available following the most recent round of TSG meetings.

The 3GPP Specifications are stored on the file server as zipped MS-Word files. The filenames have the following structure:

SM[-P[-Q]]-V.zip

where the character fields have the following significance ...

S = series number - 2 characters (see the table above)
M = mantissa (the part of the spec number after the series number) - 2 or 3 characters (see above)
P = optional part number - 1 or 2 digits if present
Q = optional sub-part number - 1 or 2 digits if present
V = version number, without separating dots - 3 digits

So for example:

• 21900-320.zip is 3GPP TR 21.900 version 3.2.0
• 0408-6g0.zip is 3GPP TS 04.08 version 6.16.0
• 32111-4-410 is 3GPP TS 32.111 part 4 version 4.1.0
• 29998-04-1-100 is 3GPP TS 29.998 part 4 sub-part 1 version 1.0.0

Further information:

Latest version
The latest versions of the approved specifications in the "latest" directory. The latest version of draft specs (i.e. those not yet under change control) are in the "latest-drafts" directory. See also the page on version numbering.

Particular version
All older versions of specifications (where available) are stored in the archive subdirectory. All versions of all releases of a given specification are placed directly under the name of the specification.

Title or subject
If you only know the title or the subject, but not the specification number, the best place to start looking is the complete list of all 3GPP specification numbers and titles. This list also shows the most recent version in each Release.

Specs related to a particular working group
Each 3GPP TSG Working Group has a home page, which lists the specifications under its responsibility. Follow the links fromhere, or use the main menu item "Specification Groups".

Official versions published by recognized Standards Development Organizations
The 3GPP Technical Specifications (and Technical Reports) which are publicly available from this site have, in themselves, no legal standing. They only become "official" when transposed into corresponding publications of the Partner Organizations. If you are looking for the official versions, see the official publications page.

Yet more information:

Work plan
The 3GPP Work plan describes the new functionality currently being elaborated in the TSG working groups. It also indicates the expected timescales for their finalization.

Releases (and phases, stages)
An introduction to the 3GPP mechanism for specifications releases can be found here.

Historical information
If you need to look for old / superseded specifications or change requests, start here.

TSG working methods
The procedures for creating, enhancing and maintaining specifications are described in TR 21.900. A presentation outlining the release and change request process can be found here.

3GPP Drafting rules
The rules for drafting specifications are described in TR 21.801.

Change Requests
The change request mechanism is used when a correction or new functionality is required for an existing specification.

Version numbering
More information on the version numbering page.

Issuing new TS/TR numbers. More information on this page.

UpLink DownLink SideLink

Mapping to physical channels

4.1        Uplink

Table 4.1-1 specifies the mapping of the uplink transport channels to their corresponding physical channels. Table 4.1-2 specifies the mapping of the uplink control channel information to its corresponding physical channel.

Table 4.1-1

TrCH	Physical Channel
UL-SCH	PUSCH
RACH	PRACH

Table 4.1-2

Control information	Physical Channel
UCI	PUCCH, PUSCH

4.2        Downlink

Table 4.2-1 specifies the mapping of the downlink transport channels to their corresponding physical channels. Table 4.2-2 specifies the mapping of the downlink control channel information to its corresponding physical channel.

Table 4.2-1

TrCH	Physical Channel
DL-SCH	PDSCH
BCH	PBCH
PCH	PDSCH
MCH	PMCH

Table 4.2-2

Control information	Physical Channel
CFI	PCFICH
HI	PHICH
DCI	PDCCH, EPDCCH

4.3        Sidelink

Table 4.3-1 specifies the mapping of the sidelink transport channels to their corresponding physical channels. Table 4.3-2 specifies the mapping of the sidelink control information to its corresponding physical channel.

Table 4.3-1

TrCH	Physical Channel
SL-SCH	PSSCH
SL-BCH	PSBCH
SL-DCH	PSDCH

Table 4.3-2

Control information	Physical Channel
SCI	PSCCH

Source : http://www.3gpp.org/dynareport/36212.htm