top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How CBC is authenticating the emergency broadcast request from CBE in case of ETWS ?

+1 vote
103 views
How CBC is authenticating the emergency broadcast request from CBE in case of ETWS ?
posted Nov 24, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes
How to Broadcast paging and SI's when ENodeB receives ETWS Indication.

If once ENodeB recevies ETWS indication form MME, ENodeB should broadcast the paging message to all UE.

Inorder to send paging message with DL indication ENodeB will have UE_ID to calculate PO & PF to broadcast Paging message.

What will UE_ID in case of ETWS indication? How to calculate PO or is their any specific PO's which is their to broadcast?

+4 votes
In case of ETWS, SIB11 secondary notification sent as segments do I need to send SIB1 for each segment or once?

The ETWS msg from RRC send as primary and secondary notifications. Secondary notification size can be 9600 bytes at max so to handle such big size on radio interface between ENB and UE we are segmenting SIB 11. As per RRC spec we need to send paging, SIB1 along with SIB11 for secondary notification. As we are segmenting SIB 11 into number of segments for that do I need to send SIB1 for each segment or once?

+1 vote
LTE: Can a UE send Attach Request with IMSI if already Emergency attached with IMEI?

I have a question regarding the behavior of UE when SIMless attached. In case when a UE is Emergency Attached wth IMEI, can it trigger again Attach with IMSI, without been detached in the meanwhile?

In other words, is it valid a case that UE triggers an Emergency call without SIM (only IMEI sent), and while calling, we put the SIM and UE triggers IMSI attach? Is this a valid scenario?

+1 vote
LTE: What target eNodeB does in case it receives "Path switch request failure" from MME ?

As one failure message is defined in specification for the path switch procedure then what would be the behavior of target eNodeB after getting failure response from the MME ? Action would be vendor specific or standard action has been defined for this scenario ?

...