Service request & Extended service Request: An EMM procedure (This procedure is used

when a UE, initially attached to the network but staying in Idle/Connected state, wishes to
use LTE services when there is new traffic.)

1. SERVICE REQUEST is triggered by the UE when there is need of NAS signaling

establishment.
2. EXTENEDED SERVICE REQUEST is triggered by the UE to initiate a "CS fallback call" or
respond to an "MT CS fallback" request from the network.

This procedure is used:

1) EMM-IDLE (Service Request)
- When downlink/uplink signaling is pending (EX: MT / MO Call)
- When UE or the network has user data pending
2) EMM-Connected (Extended Service Request) (EX: MT / MO Call)
-When mobile originating/terminating CS fallback happens

1) EMM-IDLE example with message flow and key IE

MO CALL:
 UE --> NW : Service Request
short_mac_value
When UE initiates MO service in idle
mode it triggers Service request
MT CALL:
 NW --> UE : Paging
message c1 : paging : cn-Domain ps
 UE --> NW : Service Request
short_mac_value
When UE is in idle mode and about to receive MT call, NW
send PAGING with cn-domain as PS and in response UE send
service request.

2) EMM-Connected example with message flow and key IE

MO CALL:
 UE --> NW : Extended service request
msg_type = 76 (Extended service Req )
service_type = 0 (0x0) (mobile
originating CS fallback)
Similar as above description UE triggers ESR when terminating CS fallback)
MO call happens in EMM-connected mode.
MT CALL:
 NW --> UE : CS Service Notification
 UE --> NW : Extended service request
msg_type = 76 (0x4c) (Extended
service request)
service_type = 1 (0x1) (mobile
Similar as Idle mode MT CALL, NW send CS
notification instead of paging and US starts with
service request.

Note: UE  NW (UPLINK Messages) & NW  UE (DOWNLINK Messages)