5G GUTI






GUTI -Globally Unique Temporary Identifier
AMF is in-charge to assign GUTI to an UE and it is common to both 3GPP and non-3GPP access.

5G GUTI (80 bits) = GUAMI + 5G TMSI



GUAMI - Globally Unique AMF Identifier

AMF Region ID: identifies the region
AMF Set ID: identifies the AMF Set within the AMF Region
AMF Pointer: identifies the AMF within the AMF Set.

GUAMI = AMF Region ID + AMF Set ID + AMF Pointer ID



TMSI identifies the UE with in the AMF

Since GUTI is longer, to enable more efficient radio resources (especially in Paging and Service Request), new identifier called 5G-S-TMSI is created.


S-TMSI (48 bits)= AMF Set ID + AMF Pointer ID + 5G TMSI


5G: Important Identifiers


DNN: Data Network Name. This is similar to APN in 4G. 

Each S-NSSAI may be served by different DNN.


SUCI: Subscription Concealed Identifier.

In 4G, IMSI was provided to the network as a simple text and hackers can easily hack it. 5G addresses this concern and conceals the IMSI (SUPI in 5G) before sending it to the network.

SUPI: Subscription Permanent Identifier Similar to IMSI in 4G. Valid in 3GPP system and is provisioned in UDM/UDR.

PEI: Permanent Equipment Identifier. Similar to IMEI in 4G.


ReportCGI in Measurement Report and ANR


ReportCGI and it's relation to ANR



ANR: Automatic Neighbour Relation is one of the SON features where SON banks on UE to detect unknown cells and report them to eNB. These unknown cells can be Intra-frequency, Inter-frequency and Inter-RAT.


Intra-frequency: Same carrier frequency, can be of different bandwidths

Inter-frequency: Different carrier frequency as compared to the serving cell
Inter-RAT: UTRAN, GERAN

In LTE, the operator is relieved from the duty of handling neighbour information. The ANR functionality resides with the eNB and it is responsible for creation/updation/deletion of NEIGHBOUR RELATION.



eNB:
1. The procedure of building the NRT lies with eNB. eNB initiates the procedure by asking the UE to start and send measurement of nCell (NEIGHBOUR CELL)
2. Here, UE plays the role of identifying the neighbour cell, measuring the signal strength (RSRP/RSRQ) and informing the serving eNB
3. eNB receives the Measurement Report of the nCell which contains the E-UTRAN CELL GLOBAL IDENTITY of the neighbour cell


MME:
1. The serving eNB gets in touch with MME (if an X2 connection doesn’t exist) to assist it-self for creating a X2 tunnel with the target eNB. Once when this tunnel (IPSec and SCTP) is established, the serving cell eNB forwards the CGI-info to the target eNB. Thus, both the eNB's updates its own respective NRT (NEIGHBOUR RELATION TABLE).
2. Now, an INTRA or INTER FREQUENCY HO can take place:
   a. (click here) to know about INTRA/INTER Frequency Handover procedure (with SGW Relocation)
   b. (click here) to know about INTRA/INTER Frequency Handover procedure (without SGW Relocation)

Let's continue with CGI-info in this post:


Thought:

Why does UE have to get involved in building the Neighbour table in the eNB's?
Answer: In order to reduce the signaling over-head among eNB's. It will be a tedious task for the operator to manually manage Neighbour tables. Even if there is an automatic procedure for eNB to update NRs, it would cause enough signaling (talking to LTE/UTAN/GERAN) overhead for eNB.


UE:
1. UE is in RRC Connected state
2. The eNB sends RRCConnectionReconfiguration message to UE which configures necessary parameters for nCell measurements

Query_1: UE is already connected to serving cell then how will UE read measurement of the nCell?

For INTER-frequency nCell measurements and INTRA-frequency nCell measurements are defined as follows:

a. Intra-frequency neighbour (cell) measurements: nCell measurements performed by the UE are intra-frequency measurements when the current and target cell operates on the same carrier frequency. The UE shall be able to carry out such measurements without measurement gaps.

b. Inter-frequency neighbour (cell) measurements: Neighbour cell measurements performed by the UE are inter-frequency measurements when the neighbour cell operates on a different carrier frequency, compared to the current cell. The UE should not be assumed to be able to carry out such measurements without measurement gaps.

Query_2: What are Measurement Gaps?

Measurement Gaps are periods where UE switches off its Rx and TX from the serving Cell and starts listening to other. This GAP period has to be in sync with the eNB because the eNB should know when the UE will enter the GAP state. To configure the GAP period in UE, eNB uses measGapConfig IE which is included in RRCConnectionReconfiguration message.

Therefore, the UE has now the required parameters for nCell measurements and GAP periods. Remember, for Intra-frequency measurements, GAPS are not required as stated above. The above call flow is for Intra-frequency as the EAFCN for both the cells are 5780.

If the EARFCN were differents then Meaurement Gaps would have been required. This would be the case of Inter-frequency measurements. 

4. UE measures the power level (RSRP/RSRQ) of the nCell and informs eNB in MEASUREMENT REPORT. This report consists of measResults of sCell and nCell.

5. eNB receives this report and decides whether a HO is required or not.
6. If HO is required, then eNB checks whether Physical Cell Identity of nCell is present in the MR.
  a. If PCI is not there then eNB proceeds with ANR procedure 
7. eNB constructs another RRCConnectionReconfiguration message and includes the "cellForWhichToReportCGI" IE. This IE contains the cellID of the nCell for which CGI-INFO is requested.  
8. Now, UE has to report the CGI-INFO for the Cell so that eNB will be able to contact the nCell-eNB and exchange necessary configurations for building the NRT

CGI-INFO consists of:

i. eCGI (EUTRAN CELL GLOBAL IDENTIFIER)
ii. TAC (TRACKING AREA CODE)
iii. PLMN Identity List

Query_3: UE is in state RRC-connected to sCell so how does UE get the CGI-Info from nCell?

1. Measurement Gaps are used for the purpose of measurements only. To get the CGI-Info, UE have to read SIB-1 of the nCell. To read the SIB1, UE have to decode MIB as well as the PSS and SSS of the nCell. To achieve this, UE would need quite a amount of time as compared to performing measurements of the nCell; and, measurement Gaps does not provide such a long time for this activity.
Therefore, to get the SIB1, UE uses IDLE periods to read SIB1. These idle periods are configured using drx-config IE embedded in the RRCConnectionReconfiguration message.

drx_Config  

            setup  DRX_Config
             onDurationTimer sf50
             drx_InactivityTimer sf2560
             drx_RetransmissionTimer psf1  


Therefore, when the inactivity timer expires, UE enters IDLE period and it is during this idle period, UE will sync with nCell and read MIB/SIB of the nCell.


2.

  a. There is one more alternate way to read the CGI-info of the nCell which is -AUTONOMOUS GAPS-. If the UE supports autonomous gaps then it sends this information in the UECapabilityInformation message.
  b. eNB knows that UE supports autonomous gaps and asks the UE to use autonomous gaps for reading CGI-info of the nCell. A new IE is introduced in Rel9 of 3GPP "si-RequestForHO". If this bit is set to TRUE in the measConfig then UE will use AUTONOMOUS GAPS. If autonomous gaps are used then there is a time limit prescribed by 3GPP to complete the reading of cgi-info.

Query_4: What are AUTONOMOUS GAPS?

These are GAP periods where UE will halt the Tx/Rx of the sCell for a moment to perform measurements or read MIB/SIB of the nCell. If Autonomous Gaps are not configured i.e. si-RequestForHO is set to FALSE  then UE will use IDLE periods as stated in Query_1 above.


Important Points to use:
1. An interesting point to note is that if the DRX configurations are not optimized correctly then eNB will not allow the UE to breathe, which means UE will not be able to enter IDLE periods. If this is the case, then UE will not be able to read SIB1, but it will still send MeasurementReport. However, this MR will not contain the CGI-info, instead it will carry only the signal strengths of sCell and nCell.
 2. When DRX IDLE period is on-going, eNB shouldn't send any data or UL grant because:
   a. Handling of UL grant has higher priority than DRX, which means, if UE has any UL grant or DL data during the ON time of DRX cycle then UE does not enter the IDLE period
   b. If eNB keeps on sending UL grant or DL data then UE will never enter IDLE period which is needed for switching to target cell for reading CGI detection.

3. In case of Measurement GAPS, GAPS have higher priority than data Tx/Rx.




comments and queries are welcome....

Paging in LTE





S-GW:
1. DL data arrives for the UE
2. Creates DL Data Notification message and forwards to MME

MME: 
1. When UE is in ECM-Idle state, the UE location is known to MME on a per TA basis. Therefore, MME has to page all eNB's within a group of TA.
2. MME starts timer 3413when:
    a. Paging is for PS data
    b. UE is addressed by S-TMSI
3. List of TAI: informs the eNB to broadcast the Paging messages in the mentioned TAI's
4. Sends DL Data Notification ACK message to S-GW

eNB:
1. Receives S1AP: Paging and constructs RRC: Paging message
2. RRC: Paging message may contain multiple PAGING RECORDS to page multiple UE's

UE:
1. Wakes up every Paging occasion and searches for P-RNTI within the PDCCH transmission
2. If UE finds the P-RNTI then it proceeds to decode the PDSCH information which is present in PDCCH
3. UE decodes RRC:Paging from the PDSCH Resource Block within which the PAGING message is sent
4. If UE doesn't find it's own UE identity then it returns to monitor the Paging Occasion.
5. When UE finds it's identity in the message it triggers the Random Access Procedure. followed by establishing the RRC Connection.
6. If PAGING is for PS domain then UE NAS layer triggers SERVICE REQUEST otherwise, if the PAGING is for CSFB then UE triggers Extended SERVICE REQUEST.


Thought:

How does UE determine the Paging Frame and Paging Occasion?
OR
How does eNB know when to send the Paging message so that UE will be awake to receive the message?

During this specific occurrence (Frame and Occasion), UE will wake up to check if there is any PAGING intended to it. If there is no information, UE will be go back to sleep. This happens when UE is in IDLE mode after registration. The related parameters are sent through SIB2. Therefore,a synchronization exist between the UE and eNB and both of them know when to look for Paging(UE) and when to transmit the Paging (eNB).

Paging Frame calulation:
Formula for calculating Paging Frame:::  SFN mod T=  (T div N) * (UE_id mod N)

where, 
- T: DRX cycle of the UE. T is determined by the shortest of the UE specific DRX value, if allocated by upper layers, and a default DRX value broadcast in system information. If UE specific DRX is not configured by upper layers, the default value is applied.
- nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32.
- N: min(T,nB)
- Ns: max(1,nB/T)
- UE_ID: IMSI mod 1024
Parameters broadcasted in SIB2:
Default Paging cycle=T; (value=rf128)
nB= Broadcasted in SIB2 (value=1T)

Example:
Calculation:
a.       IMSI of UE (in DECIMAL)= 262022008880715
b.      N=128 (Look for the formula above to determine the value of N)
c.       UE_id = 262022008880715 mod 1024= 587
d.      (UE_id mod N)= 587 mod 128=75
e.      (T div N)= 128 / 128 = 1

Therefore, SFN mod T =75
So, whenever SFN mod T will be 75, UE will wake to read if there is a Paging message addressed to it. 

From this particular SFN the frame is derived. Now, the frame is identified but we also need to know that on which sub frame the Paging information is present. To determine, this Paging Ocassion is used.

Paging Ocassion calculation:
Formula for calculating the PO::: i_s = floor(UE_ID/N) mod Ns

a.       Ns=1 (Look for the formula above to determine the value of N)
b.      floor (587/128)= 4
c.       i_s = 0

Index i_s points to PO from the sub-frame pattern defined in the below table will be derived from following calculation:
 Table taken from 3GPP for FDD:
Ns
PO when i_s=0
PO when i_s=1
PO when i_s=2
PO when i_s=3
1
9
N/A
N/A
N/A
2
4
9
N/A
N/A
4
0
4
5
9


The Ns is 1 and PO would be 9 since i_s =0 in this example. Also, Paging Frame is derived as 75.

Therefore, from this example, whenever SFN mod T will be equal to 75, UE will look for P-RNTI in sub-frame 9 of that particular Radio Frame.


comments and queries are welcome.....

All about SIB's in LTE

SIBs and their JOBS: (click on each of the SIB to know more about them)
SIB-1
Cell access related parameters and scheduling of other SIBs
SIB-2
Common and shared channel configuration, RACH related configuration are present
SIB-3
Parameters required for intra-frequency, inter-frequency and I-RAT cell re-selections
SIB-4
Information regarding INTRA-frequency neighboring cells (E-UTRA)
SIB-5
Information regarding INTER-frequency neighboring cells (E-UTRA)
SIB-6
Information for re-selection to INTER-RAT (UTRAN cells)
SIB-7
Information for re-selection to INTER-RAT (GERAN cells)
SIB-8
Information for re-selection to INTER-RAT (CDMA2000)
SIB-9
Information related to Home eNodeB  (FEMTOCELL)
SIB-10
ETWS (Earthquake and Tsunami Warning System) information (Primary notification)
SIB-11
ETWS (Earthquake and Tsunami Warning System) information (Secondary notification)
SIB-12
Commercial Mobile Alert Service (CMAS) information.
SIB-13
Contains the information required to acquire the MBMS control information associated with one or more MBSFN areas.


Query_1: Why SIBs are needed?

SIBs carry relevant information for the UE, which helps UE to access a cell, perform cell re-selection, information related to INTRA-frequency, INTER-frequency and INTER-RAT cell selections.

Query_2: How many types of SIBs are there?
In LTE there are 13 types of SIBs. Each SIB has its own job to do, which means, they are meant to carry information which are related to perform their assigned job.

Query_3: On which channels SIBs are transmitted?
All SIBs are transmitted on BCCH->DL-SCH->PDSCH.

Query_4: Minimum of how many SIBs are required for the UE to initiate Attach procedure?
In LTE, for a UE to access the eNB, at the most minimum 2 SIBs are required (SIB1 and SIB2).

Information regarding SIB2-SIB13 are carried in SI messages and are included in schedulingInfoList which is part of SIB1.

Scheduling of SIBs:
·         SIB1 uses a fixed schedule with a periodicity of 80 ms and repetitions made within 80 ms.
·         The first transmission of SIB1 is scheduled in subframe #5 of radio frames for which the SFN mod 8 = 0, and
·         Repetitions are scheduled in subframe #5 of all other radio frames for which SFN mod 2 = 0.
·         Scheduling of other SIB's i.e. SIB-2 to SIB-9 is defined by si-Periodicity and si-WindowLength. Both these IEs are explained below. For the rest of the SIBs, Paging is received by UE in RRC_IDLE or RRC_CONNECTED mode for notification of an in-coming SI message.

Scenarios where UE acquire SIBs:
UE will initiate the SIB acquisition procedure in any of the following criteria's:

·         UE is powered on (selecting a cell)
·         Cell re-selection
·         After HO completion
·         After entering E-UTRAN from another RAT
·         coming out of OUT OF COVERAGE situation
·         receiving a notification that SYSTEM INFORMATION has changed
·         receiving an indication about the presence of ETWS (Primary/Secondary), CMAS notification
·         receiving a request from CDMA 2000 upper layers
·         exceeding the maximum validity duration of SIBs

HOW and WHEN UE start acquiring SIBs (other than SIB1):
There are two IE's which help the UE to calculate when to read SI messages. They are:
a. schedulingInfoList
b. si-WindowLengthd

schedulingInfoList informs the UE regarding the presence of SIB type; other than SIB1. It carriers two more parameters:
i.  si_Periodicity
ii. sib_MappingInfo
· si_Periodicity tells about the period in terms of radio frames which helps the UE to read the required SIB. The value of this parameter is used for calculating the Radio frame where SI will be received.
· sib_MappingInfo carries the type of SIBs mapped
si-WindowLength specifies that a SIB should be transmitted somewhere within the specified window length. Value is in ms. This window starts at the starting sub-frame of the mentioned si_periodicity. SIBs can be received in any of the sub-frame as mentioned in the WindowLength.
Example:
SIB1 is received by UE with the following information:
schedulingInfoList[0]
SchedulingInfo
si_PeriodicitySchedulingInfosi_Periodicity_rf16
sib_MappingInfo[0]SIB_TypeSIB_Type_sibType3
schedulingInfoList[1]SchedulingInfo
si_PeriodicitySchedulingInfosi_Periodicity_rf32
sib_MappingInfo[0]SIB_TypeSIB_Type_sibType4
schedulingInfoList[2]SchedulingInfo
si_PeriodicitySchedulingInfosi_Periodicity_rf64
sib_MappingInfo[0]SIB_TypeSIB_Type_sibType5
si_WindowLength
ms20
(To look for the complete IE contents and explanation of SIB1 click here)

The above table states the following:
The first element of schedulingInfoList contains sib3Periodicity= 16 radio frames
or 160ms
Window length= 20ms
The seond element of schedulingInfoList contains sib4Periodicity= 32 radio frames
or 320ms
Window length= 20ms
The third element of schedulingInfoList contains sib5Periodicity= 64 radio frames
640ms
Window length= 20ms

Now, UE needs two information to read SI.
a. One is on which which Radio frame UE will receive the SIB. To determine which Radio frame, the formula is:

SFN mod T = FLOOR(x/10)

b. on which sub-frame will the SI window start. To determine the start of the SI window at sub-frame, the formula is:


a = x mod 10

Query: How to determine the value of x?


x = (n – 1)*w

where,

xInteger value
na number which corrosponds to the order of entry in schedulingInfoList.For sib3 n is 1,
for sib4 n is 2 and
for sib5 n is 3
wsi-WindowLength
Tsi-Periodicity of the concerned SI message


Let's start calulating the Radio frame and SI starting sub frame for SIB3, SIB4 and SIB5

Subframe from which the SI Window starts
For SIB-3x = (n – 1)*w
x=(1-1)*20
x=0
a = x mod 10
a= 0 mod 10
a=0
The SI Window will start at sub frame 0 of the Radio frame where SI will be acquired
For SIB-4x = (n – 1)*w
x=(2 - 1)*20
x=20
a = x mod 10
a= 20 mod 10
a=0
The SI Window will start at sub frame 0 of the Radio frame where SI will be acquired
For SIB-5x = (n – 1)*w
x=(3 - 1)*20
x=40
a = x mod 10
a= 40 mod 10
a=0
The SI Window will start at sub frame 0 of the Radio frame where SI will be acquired
Radio frame on which the UE will acquire designated SIB
For SIB-3SFN mod T = FLOOR(x/10)SFN mod 16 = FLOOR (0/10)
SFN mod 16 = 0
Whenever SFN mod 16 will be 0. UE is expecting SIB3 and it will start looking from sub frame 0 till the end of the mentioned si-WindowLength
For SIB-4SFN mod T = FLOOR(x/10)SFN mod 32 = FLOOR (20/10)
SFN mod 32 = 2
Whenever SFN mod 32 will be 2. UE is expecting SIB4 and it will start looking at sub frame 0 till the end of the mentioned si-WindowLength
For SIB-5SFN mod T = FLOOR(x/10)SFN mod 64 = FLOOR (40/10)
SFN mod 64 = 4
Whenever SFN mod 64 will be 4. UE is expecting SIB5 and it will start looking at sub frame 0 till the end of the mentioned si-WindowLength


SIBs and their JOBS: (click on each of the SIB to know more about them)
SIB-1
Cell access related parameters and scheduling of other SIBs
SIB-2
Common and shared channel configuration, RACH related configuration are present
SIB-3
Parameters required for intra-frequency, inter-frequency and I-RAT cell re-selections
SIB-4
Information regarding INTRA-frequency neighboring cells (E-UTRA)
SIB-5
Information regarding INTER-frequency neighboring cells (E-UTRA)
SIB-6
Information for re-selection to INTER-RAT (UTRAN cells)
SIB-7
Information for re-selection to INTER-RAT (GERAN cells)
SIB-8
Information for re-selection to INTER-RAT (CDMA2000)
SIB-9
Information related to Home eNodeB  (FEMTOCELL)
SIB-10
ETWS (Earthquake and Tsunami Warning System) information (Primary notification)
SIB-11
ETWS (Earthquake and Tsunami Warning System) information (Secondary notification)
SIB-12
Commercial Mobile Alert Service (CMAS) information.
SIB-13
Contains the information required to acquire the MBMS control information associated with one or more MBSFN areas.