Wednesday, December 2, 2015

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 series3G and beyond / GSM (R99 and later)GSM only (Rel-4 and later)GSM only (before Rel-4)
General information (long defunct)00 series
Requirements21 series41 series01 series
Service aspects ("stage 1")22 series42 series02 series
Technical realization ("stage 2")23 series43 series03 series
Signalling protocols ("stage 3") - user equipment to network24 series44 series04 series
Radio aspects25 series45 series05 series
CODECs26 series46 series06 series
Data27 series47 series (none exists)07 series
Signalling protocols ("stage 3") -(RSS-CN) and OAM&P and Charging (overflow from 32.- range)28 series48 series08 series
Signalling protocols ("stage 3") - intra-fixed-network29 series49 series09 series
Programme management30 series50 series10 series
Subscriber Identity Module (SIM / USIM), IC Cards. Test specs.31 series51 series11 series
OAM&P and Charging32 series52 series12 series
Access requirements and test specifications13 series (1)13 series (1)
Security aspects33 series(2)(2)
UE and (U)SIM test specifications34 series(2)11 series
Security algorithms (3)35 series55 series(4)
LTE (Evolved UTRA) and LTE-Advanced radio technology36 series--
Multiple radio access technology aspects37 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.

Friday, November 27, 2015

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

How do UE read ETWS Info in SIB10 SIB11

Below are the steps how do UE read when there is a ETWS notification from NW.

SIB 10 and SIB 11 are  the responsible SIB's for ETWS.
Where SIB10 carry info about primary notification and SIB11 will carry info for secondary notification.



This we can get from below test case according 3GPP spec TS-36.523-1
14.1  ETWS reception in RRC_IDLE state / Duplicate detection
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection


According the Test Case Below is the steps included for the Test case,

       
St
Procedure
Message Sequence
TP
Verdict


U - S
Message
-
-
1
The SS include an ETWS message with new messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE1).
<--
Paging
-
-
2
Check: Does the UE indicate the contents of the "warning message" to the user, and alert or activate alerting the user (NOTE2)?
-
-
1
P
3
The SS wait for 10s.
-
-
-
-
4
The SS include an ETWS message with same messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE1).
<--
Paging
-
-
5
Check: Does the UE indicate the contents of the "warning message" to the user, or alert or activate alerting the user (NOTE2)?
-
-
1
F
NOTE1:     SystemInformationBlockType11 contain 3 segments.
NOTE2:     The data indication and user alerting are the UE implementation issues.





Paging Message for the test case will be as below,

Derivation Path: 36.508 Table 4.6.1-7
Information Element
Value/remark
Comment
Condition
Paging ::= SEQUENCE {



  pagingRecordList
Not present
 Not needed as this is for all the UE

  systemInfoModification
Not present


  etws-Indication
true
 This filed will be true for ETWS notification

  nonCriticalExtension SEQUENCE {}
Not present


}




SIB1 Content will be like below,

Derivation Path: 36.508 table 4.4.3.2-3
Information Element
Value/remark
Comment
Condition
SystemInformationBlockType1 ::= SEQUENCE {



  schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {}
Combination 8 in TS 36.508 section 4.4.3.1
SIB2, SIB3, SIB10 and SIB11 are transmitted

}





1. Paging to UE for ETWS (Paging will be there for both Idle and Connected Mode)
2. UE Reads SIB1 , where  "systemInfoValueTag" will be 1 and will contain scheduling info about
3. SIB10 and SIB11.
4. UE reads  other SIB's accordingly
5. User will be notified via alert messages/tones/both as per UE implementation.

Source: 3GPP TS-36.523-1