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

How do UE read modified SI by NW

Below are the steps how do UE read when there is a modification of sib from NW side.

This we can get from below test case according 3GPP spec TS-36.523-1
8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode


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


Main Steps in this test cases are 1,5,6,7 and 7a.

Step 1 verifies whether the UE is able respond to paging or not after the attach which is without any SI modification. In-fact this during this attach whatever SI has been transmitted are the scale to determine about the SI changes done by NW.

Step 5 NW transmits a paging like below,

Air Message: AIR_MSG_TYPE_PCCH
        paging Paging
          systemInfoModification PagingsystemInfoModification_true
          pagingRecordList_exist         0
          systemInfoModification_exist 1
          etws_Indication_exist                 0
          nonCriticalExtension_exist         0
As this is applicable to all the UE on that eNB so this kind of Paging doesn't include any UE identity.

Step 6 ensures that UE receive's the changed system information.
         This will be done by in this test scenario,
          First UE will go and read SIB1 - which will have SystemInfoValueTag as 1 in this case.
          Then UE will go and read SIB2 according scheduling Info provided by the new SIB1.
           This test case includes only PRACH CONFIG INDEX changed in SIB2 as below,

Previously:
prach_ConfigIndex 3
Now:
prach_ConfigIndex 10


Step 7  and 7a is just for checking whether UE is able to setup RRC Connection with NW or not?
         This steps will not be happening in case of live NW.
          Here NW pages (Step 7) UE with Paging message as below with S-Tmsi and UE establishes Rrc Connection Successfully (Step 7a).

Air Message: AIR_MSG_TYPE_PCCH

 

          pagingRecordList_exist         1

          systemInfoModification_exist 0

          etws_Indication_exist                 0

          nonCriticalExtension_exist         0

        pagingRecordList[0] PagingRecord

            ue_Identity PagingUE_Identity_

              s_TMSI S_TMSI

                mmec MMEC

                  buff[0..0] 01 

                TMSI S_TMSIm_TMSI

                  buff[0..3] c2 34 56 78 

       

St	Procedure	Message Sequence		TP	Verdict
		U - S	Message
1	The SS transmits a Paging message including a matched identity.	<--	Paging	-	-
2	Check: Does the UE transmit an RRCConnectionRequest message?	-->	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message.	<--	RRCConnectionSetup	-	-
3A	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	-->	RRCConnectionSetupComplete	-	-
3B	The SS transmits a SecurityModeCommand message.	<--	SecurityModeCommand	-	-
3C	The UE transmits a SecurityModeComplete message.	-->	SecurityModeComplete	-	-
3D	The SS transmits an RRCConnectionReconfiguration message.	<--	RRCConnectionReconfiguration	-	-
3E	The UE transmits an RRCConnectionReconfigurationComplete message.	-->	RRCConnectionReconfigurationComplete	-	-
3F	The SS transmits an RRCConnectionRelease message.	<--	RRCConnectionRelease	-	-
3G	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	-	-	-	-
4	The SS changes the prach-ConfigIndex in the system information	-	-	-	-
5	The SS transmits a Paging message including a systemInfoModification.	<--	Paging	-	-
6	Wait for 15s for the UE to receive system information.	-	-	-	-
7	The SS transmits a Paging message including a matched identity.	<--	Paging	-	-
7A	Check: Does the UE re-transmit a random access using prach-ConfigIndex given in step 4?	-	-	1	P
8	The UE transmit an RRCConnectionRequest message.	-->	RRCConnectionRequest	-	-
9	The SS transmits an RRCConnectionSetup message.	<--	RRCConnectionSetup	-	-
9A	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	-->	RRCConnectionSetupComplete	-	-
9B	The SS transmits a SecurityModeCommand message.	<--	SecurityModeCommand	-	-
9C	The UE transmits a SecurityModeComplete message.	-->	SecurityModeComplete	-	-
9D	The SS transmits an RRCConnectionReconfiguration message.	<--	RRCConnectionReconfiguration	-	-
9E	The UE transmits an RRCConnectionReconfigurationComplete message.	-->	RRCConnectionReconfigurationComplete	-	-
9F	The SS transmits an RRCConnectionRelease message.	<--	RRCConnectionRelease	-	-
9G	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	-	-	-	-
10	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.2 indicate that the UE is in E-UTRA RRC_IDLE state on Cell 1?	-	-	1	-