AdSense doesn't know about your blog

 AdSense doesn't know about your blog:

             Friends this blog is about "when site and other tabs are not working in menu bar." on google adsense page. I am also the beginner in blogging and i also faced such issues while taking google adsense approval for site( But it is not an issue, Your site is under review by google. if any problem is with your site and blog, google will notify you by sending mail to you.

So friends, when you just apply for adsense approval and after some time you facing such issue like " AdSense doesn't know about your blog:". it means that your account is not activated yet from google ends. when google will activate your account below message will automatically removed from blogger.

adsense and blogger both are google products, so they can communicate and access each other functionality very efficiently and know each other.

If somehow, after activation of your google account still above issue is reported on your site. then you can visit adsense ~/Sites page and include your site URL. and nothing else...

Over the home page you will see that the google is saying that "We are working on setting you up". 
It means that google is having all the information regarding your site, which are needed for review your site. 
Because you have setup the adsense code in your html code in between <head>..</head> tag. by doing the same google can have access your site and start reviewing your site. and giving you the below message on adsense page.

So Don't be PANIC. your site is under review process.  If everything OK and your site fallows the google adsense policy. with in 3 to 4 days google will surly activate your account.

If there are some problem for accessing your site by google, then they will update you accordingly and will tell you the faults also.

After Activation:
When google will activate your adsense account this problem(AdSense doesn't know about your blog). will automatically removed and further instruction will come on blogger/adsense page. 

Need to check:
IF you are reading my blog, it means that you had did all the required changes for the adsense on blogger settings and adsense payments/settings pages. but if you didn't, please check.
1- place all your personal information in payments/settings pages on google adsense.
2- make sure that your robot.txt file allowing google for crawling and review you site.
3- make you post unique. google strictly check plagiarism.

Only quality of your blogs mattress in bloggings.



The 5G Globally Unique Temporary Identifier (5G-GUTI) is allocated by the AMF. It is a temporary identity so it docs not have a fixed association with a specific subscriber nor device. The use of a temporary identity helps to improve privacy. The AMF can change the allocated 5G-GUTI at any time.

The structure of the 5G-GUTI is illustrated in Figure below. It is a concatenation of the Globally Unique AMF Identifier (GUAMI) and 5G-TMSI. 

The GUAMI is a concatenation of the PLMN Identity and the AMF Identifier. Inclusion of the GUAMI allows identification of thc AMF which allocated the 5G-GUTI. The 5G-TMSI identifies the UE within that AMF.

3GPP has specified a mapping between the 5G-GUTI and the 4G-GUTI. This mapping is used when a UE moves between technologies. For example, when a UE moves from 5G to 4G and is required to send a GUTI to the MME, then the UE maps the 5G-GUTI onto the 4G-GUTI and forwards it to the MME. The MME can then complete the reverse mapping to identify the AMF that it needs to contact in order to retrieve the UE context. Similarly, when a UE moves from 4G to 5G then the 4G-GUTI can be mapped onto the 5G-GUTI and sent to the AMF. The AMF can then extract the MME Identity and subsequently request the UE context.


A 5G Subscription Permanent Identifier (SUPI) can be either:
  •   An International Mobile Subscriber Identity (IMSI)
  •   A Network Access Identifier (NAI)

A Subscription Concealed Identifier (SUCI) allows the SUPI to be signalled without exposing the identity of the user. 

Signalling procedures use the SUCI rather than the SUPI to provide privacy. For example, the '5GS Mobile Identity' within NAS signalling procedures can be based upon a SUCI (alternatively, the '5GS Mobile Identity' can be an IMEI, IMEISY, 5G-GUTI or 5G-S-TMSI)

* The SUCI uses a 'Protection Scheme' which can be set to 'null' in which case the SUPI is visible within the message. These protection schemes are used to encrypt the SUPI prior to including within the message.

5G(NR)- Radio Network Temporary Identifier (RNTI)

 Radio Network Temporary Identifier (RNTI):

Radio Network Temporary Identifiers (RNTl) are applicable within the Radio Access Network. They are allocated by the Base Station and are subsequently stored by both the Base Station and UE. They are used to address either an individual UE, a group of UE or all UE. For example, the C-RNTI can be used to address an individual UE, whereas an INT-RNTI can be used to address a group of UEs and the SI-RNTI can be used to address all UE.

A UE is addressed by using the RNTI to scramble the CRC bits which are attached to the PDCCH OCI payload, i.e. an RNTI is used to address the UE on the PDCCH. The PDCCH can then be used to provide uplink and downlink resource allocations, power control commands, pre-emption indications, Slot Format changes and System Information update indications.

The set of RNTI is presented in below table . All RNTI have a length of  16 bits.

The Sl-RNTI is used to scramble the CRC bits belonging to DCI Format 1_0 when allocating PDSCH resources for the transmission of System Information. 3GPP has standardised a single SI-RNTI value which is used by all UE.

The P-RNTI is used to scramble the CRC bits belonging to DCI Format 1_0 when allocating PDSCH resources for the transmission of Paging messages, or when using the PDCCH to encapsulate a 'Short Message'. A 'Short Message' can be used to indicate that System Information content has changed and needs to be re-acquired. It can also be used to indicate an Earthquake and Tsunami Warnings.

System (ETWS) primary notification on SIB6, or an ETWS secondary notification on SIB9, or a Commercial Mobile Alert System(CMAS) notification on SIB8. 3GPP has standardised a single IP-RNTI value which is used by all UE.

RNTI as per 3GPP 38.321 Table 7.1-2

The RA-RNTI is used during the Random Access procedure when allocating PDSCH resources for the Random Access Response(MSG2). There is a one-to-one mapping between the RA-RNTI and the time-frequency resource used by the UE when transmitting the Random Access Preamble. This means that all UE using the same Random Access occasion will share the same RA-RNTI and the same PDCCH transmission. The content of the PDSCH differentiates between the set of UE using the Random Access Preamble Identity (RAPID) within the MAC sub-header.

The Temporary C-RNTl (TC-RNTI) is allocated during tbc Random Access procedure within the Random Access Response (MSG2).It is subsequently used to address the UE when allocating PUSCH resources for MSG3 re-transmissions. It is not necessary to use the TC-RNTI when allocating resources for the initial MSG3 transmission because that resource allocation is included within MSG2(rather than within a PDCCH transmission). The TC-RNTI is also used when allocating PDSCH resources for MSG4

The Cell RNTI (C-RNTI) is set equal to the TC-RNTI after successful Random Access contention resolution. The C-RNTI is changed whenever a UE completes a handover towards a new cell. The C-RNTI is used to address the UE when allocating PDSCH or PUSCH resources to that UE.


The Inactive RNTI (1-RNTI) is applicable to the RRC Inactive State. In contrast to other RNTI, the I-RNTI is not used to scramble the CRC bits belonging to the PDCCH payload. instead, the 1-RNTI is used to address the UE within RRC signalling messages.

An I-RNTI can be allocated to a UE within an RRC Release message when moving the UE from RRC Connected to RRC Inactive.

There are two variants of the 1-RNTI:

  • A full I-RNTI which has a length of 40 bits. This variant can be included within an RRCResumeRequest1 message which has a size of 64 bits. This is relatively large for a MSG3 transmission, so there is a risk that uplink coverage may be compromised.
  • A short I-RNTI which has a length of 24 bits. This variant can be included within an RRCResumeReqest message which has a size of 48 bits. This is the normal size for MSG3 .

The useFullResumeID flag within SIB-1 instructs the UE to use either the full or short I-RNTI when resuming a connection, that means. this flag instructs the UE to send either an RRCResumeRequest message or an RRCResumeRequestl message.

The I-RNTI can be used to address a UE within an RRC Paging message when the UE is RRC Inactive state.



        The  UE identity is very important for authenticating the subscriber to access the network. authentication of subscriber is happened in various procedure  via RRC signalings. But to keep the subscriber safe, network allocated some unique identification, which  are used to identify the UE at various nodes. 


        The international Mobile Subscriber Identity (IMSI) is a globally unique permanent subscriber identity associated with in the USIM. An IMSI can be moved between UE by moving the USIM.

An IMSI is stored on the USIM and by the User Data Management (UDM) Network Function within the 5G Core Network.

The structure of an IMST is illustrated in below Figure.
  • The 'home' Public Land Mobile Network (PLMN) is identified using a combination of the Mobile Country Code (MCC) and Mobile Network Code (MNC). The ITU is responsible for allocating the MCC, whereas the national administrator is responsible for allocating the MNC. A UE uses the 'home' PLMN Identity when searching for a network, e.g. when completing a band scan, a UE will search for a cell which is broadcasting the 'home' PLMN Identity within SIB 1.
  • The subscriber is identified within the home PLMN using the Mobile Subscriber Identification Number (MSIN). 
  • MSIN is allocated by the service provider.

The IMSI can be used as the '5GS Mobile Identity' within NAS signalling procedures. 

For security reasons, the IMSI is included within NAS messages using a 'concealed' format which can hide the actual value. 

The 'Protection Scheme' indicated as part of the '5GS Mobile Identity' field can be set to 'null' in which case the IMSI is visible within the message.  

Some protection schemes are used to encrypt the IMSI prior to including within the message.

In the case of 5G, the IMSI is not used for paging procedures.


The International Mobile Equipment Identity (IMEI) is a permanent identity belonging to a device. 
It is stored within the device hardware and by the User Data Management (UDM) Network Function within the 5G Core Network.

The structure o1ran IMEI is illustrated in below figure.
  • The Type Allocation Code (TAC) is an 8 digit number which identifies the UE model. It can also identify a specific version of a UE model, i.e. different versions of the same UE model can be allocated different TAC. The TAC is allocated by the GSM Association (GSMA).
  • The Serial Number (SNR) uniquely identifies a device with a specific TAC. All UE which have the same TAC should be allocated different Serial Numbers. The Serial Number is allocated by the device manufacturer.
  • The Check Digit (CD) is calculated from a combination of the TAC and Serial Number. It provides a mechanism for detecting data entry errors, e.g. when the IMEI is manually entered into a system. 

The IMEI can be used within NAS signalling procedures as the '5GS Mobile Identity'. 

In contrast to the IMSI, the IMEI does not use a 'Protection Scheme' to provide encryption. Instead, the IMEI can be included directly within NAS signalling messages.

5G(NR): Scheduling Request


5G(NR): Scheduling Request:

This Blog will explain about the NR scheduling request mechanism which is applicable between UE and gNodeB. 

The Scheduling Request is triggered when UE is in uplink sync with gNodeB and It is not having and up-link (PUSCH/PUCCH) resource allocated for transmission of  new user plane or control plane data. 

The Scheduling Request (SR) is used for requesting UL-SCH resources( up-link grant ) for new transmission on PUCCH channel. 
Network (gNodeB) replies the UE with uplink grant in DCI 0_0 or DCI 0_1 messages on PDCCH channel.  


RRC connection setup or RRC reconfiguration request are used to configure the scheduling request related parameters. 
-MAC is controling the SR and the IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group.

MAC-CellGroupConfig ::= SEQUENCE {  

      drx-Config SetupRelease { DRX-Config } OPTIONAL, -- Need M 





       skipUplinkTxDynamic BOOLEAN,  

... }

-The IE SchedulingRequestConfig is used to configure the parameters, for the dedicated scheduling request (SR) resources. 


SchedulingRequestConfig ::= SEQUENCE {

    schedulingRequestToAddModList       SEQUENCE

                                               SchedulingRequestToAddMod  OPTIONA,

    schedulingRequestToReleaseList      SEQUENCE

                                               SchedulingRequestId  OPTIONAL -- Need N



SchedulingRequestToAddMod ::= SEQUENCE {

    schedulingRequestId                 SchedulingRequestId,

    sr-ProhibitTimer                    ENUMERATED {ms1, ms2, ms4, ms8, ms16,

                                                    ms32, ms64, ms128}

    sr-TransMax                         ENUMERATED {n4, n8, n16, n32, n64,

                                                    spare3, spare2, spare1}



- The IE "SchedulingRequestId" is used to identify a Scheduling Request instance in the MAC layer.


 SchedulingRequestId ::= INTEGER (0..7)



Each SR configuration corresponds to one or more logical channels. Each logical channel may be mapped to zero or one SR configuration, which is configured by RRC. 

 RRC configures the following parameters for the scheduling request procedure:  

- sr-ProhibitTimer (per SR configuration);  

- sr-TransMax (per SR configuration).


 SR will NOT be transmitted if:

  1. SR opportunity falls in measurement gap interval or
  2. another SR-Prohibit timer is running or
  3. DL PDCCH with UL resources is received.

5G(NR): MAC Control Elements

 MAC Control Elements:

- As we know that RRC and NAS messages functions are used to exchange the signalings between UE and gNodeB, But there are several communication path at MAC layer. so there are special MAC structures that carries special control information. These special MAC structure carrying the control information is called 'MAC CE', which means 'MAC Control Element'.
 -MAC CE works between UE(MAC) and gNodeB(MAC) for FAST Signaling Communication Exchange without  involving upper layers. 

- It is sent as a part of MAC PDUIt  always placed before any MAC SDUs LCID field denotes MAC CE Types.

There are several Type of MAC-CE, MAC CE List specified in 38.321 v15.3:




LCID Table for DL-SCH

 LCID values for UL-SCH channel.

LCID Table for UL-SCH



MAC-CE and reference:




Buffer Status Report

38.321 -


38.321 -

UE Contention Resolution Identity

38.321 -

Timing Advance Command

38.321 -

DRX Command

38.321 -

Long DRX Command

38.321 -

Configured Grant Confirmation

38.321 -

Single Entry PHR

38.321 -

Multiple Entry PHR

38.321 -

SCell Activation/Deactivation

38.321 -

Duplication Activation/Deactivation

38.321 -

SP CSI-RS / CSI-IM Resource Set Activation/Deactivation MAC CE

38.321 -

Aperiodic CSI Trigger State Subselection MAC CE

38.321 -

TCI States Activation/Deactivation for UE-specific PDSCH MAC CE

38.321 -

TCI State Indication for UE-specific PDCCH MAC CE

38.321 -

SP CSI reporting on PUCCH Activation/Deactivation MAC CE

38.321 -

SP SRS Activation/Deactivation MAC CE

38.321 -

PUCCH spatial relation Activation/Deactivation MAC CE

38.321 -

SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE

38.321 -

Recommended bit rate MAC CE

38.321 -




MAC CE Header:

- below are the MAC Control Elements of Buffer Status Report:

1- Short BSR and Truncated BSR format :

2- Long BSR format: 

Format of C-RNTI MAC Control Element: 

C-RNTI MAC control element fields

UE Contention Resolution Identity MAC Control Element :

UE Contention Resolution Identity MAC control element IEs
- it has fixed 48-bit size
- UE Contentions Resolution Identity: This field contains uplink CCCH SDU.

3C : MAC subheader - Contention Resolution:
R = 0
R = 0
E = 1
LCID = 11100 = Contention Resolution.

Timing Advance Command MAC control element
1- Timing Advance Command is of 6 bits in length. TA (0, 1, 2… 63)
Power Headroom MAC Control Element : 

Power Headroom MAC control element
Activation/De-activation MAC Control Element : 
- The Ci field is set to '0' to indicate that the SCell with SCellIndex i shall be de-activated.

Activation/De-activation MAC control elements

Padding MAC Sub-Header:

1F : MAC subheader - Padding
R = 0
R = 0
E = 0
LCID = 11111 = Padding