From ff8614e6a9b153767c78773c453e5ba3aceff210 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Wed, 11 Apr 2018 21:02:30 +0200 Subject: final phone_protocol-eh2018 slides --- 2018/phone_protocol-eh2018/gprs_attach.png | Bin 0 -> 82945 bytes 2018/phone_protocol-eh2018/gprs_attach.svg | 315 ++ 2018/phone_protocol-eh2018/gprs_control_stack.svg | 1341 ++++++ 2018/phone_protocol-eh2018/gprs_pdp_ctx_act.png | Bin 0 -> 80879 bytes 2018/phone_protocol-eh2018/gprs_pdp_ctx_act.svg | 338 ++ 2018/phone_protocol-eh2018/gsm_cell_selection.png | Bin 0 -> 76980 bytes .../gsm_control_stack.gnumeric | Bin 0 -> 2646 bytes 2018/phone_protocol-eh2018/gsm_control_stack.svg | 2556 +++++++++++ 2018/phone_protocol-eh2018/location_update.png | Bin 0 -> 101559 bytes 2018/phone_protocol-eh2018/location_update.svg | 505 +++ .../location_update_l3only.png | Bin 0 -> 48864 bytes .../location_update_l3only.svg | 215 + 2018/phone_protocol-eh2018/phone_powerup.adoc | 256 ++ 2018/phone_protocol-eh2018/phone_powerup.html | 4459 ++++++++++++++++++++ 2018/phone_protocol-eh2018/phone_powerup__1.png | Bin 0 -> 43358 bytes 2018/phone_protocol-eh2018/phone_powerup__2.png | Bin 0 -> 56582 bytes 2018/phone_protocol-eh2018/phone_powerup__3.png | Bin 0 -> 62940 bytes 2018/phone_protocol-eh2018/umts_cell_selection.png | Bin 0 -> 86691 bytes 18 files changed, 9985 insertions(+) create mode 100644 2018/phone_protocol-eh2018/gprs_attach.png create mode 100644 2018/phone_protocol-eh2018/gprs_attach.svg create mode 100644 2018/phone_protocol-eh2018/gprs_control_stack.svg create mode 100644 2018/phone_protocol-eh2018/gprs_pdp_ctx_act.png create mode 100644 2018/phone_protocol-eh2018/gprs_pdp_ctx_act.svg create mode 100644 2018/phone_protocol-eh2018/gsm_cell_selection.png create mode 100644 2018/phone_protocol-eh2018/gsm_control_stack.gnumeric create mode 100644 2018/phone_protocol-eh2018/gsm_control_stack.svg create mode 100644 2018/phone_protocol-eh2018/location_update.png create mode 100644 2018/phone_protocol-eh2018/location_update.svg create mode 100644 2018/phone_protocol-eh2018/location_update_l3only.png create mode 100644 2018/phone_protocol-eh2018/location_update_l3only.svg create mode 100644 2018/phone_protocol-eh2018/phone_powerup.adoc create mode 100644 2018/phone_protocol-eh2018/phone_powerup.html create mode 100644 2018/phone_protocol-eh2018/phone_powerup__1.png create mode 100644 2018/phone_protocol-eh2018/phone_powerup__2.png create mode 100644 2018/phone_protocol-eh2018/phone_powerup__3.png create mode 100644 2018/phone_protocol-eh2018/umts_cell_selection.png diff --git a/2018/phone_protocol-eh2018/gprs_attach.png b/2018/phone_protocol-eh2018/gprs_attach.png new file mode 100644 index 0000000..1e7759d Binary files /dev/null and b/2018/phone_protocol-eh2018/gprs_attach.png differ diff --git a/2018/phone_protocol-eh2018/gprs_attach.svg b/2018/phone_protocol-eh2018/gprs_attach.svg new file mode 100644 index 0000000..26a5ee8 --- /dev/null +++ b/2018/phone_protocol-eh2018/gprs_attach.svg @@ -0,0 +1,315 @@ + + + + + +MS + + + + +BSS (BTS,BSC,PCU) + + + + +SGSN + + + + +HLR + + + + + + + + + + + +GPRS Attach Procedure + + + + + + + + + + + + + + + + +Cell Selection + + + + + + + + + +L1 RACH burst (cause=TBF) + + + + + + + + + +AGCH: RR IMMEDIAGE ASSIGN + + + + + + + + + + + + +Switch from BCCH/CCCH to dedicated mode + + + + + + + + + + +UL TBF establishment + + + +RLC/MAC Layer + + + + + + + + + +RLC/MAC (LLC (GMM ATTACH REQUEST)) + + + + + + + + + +BSSGP UL-UD (LLC (GMM ATTACH REQUEST)) + + + + + + + + + + + + + + + + + +optional: GMM IDENTITY REQ + RESP (IMSI) if SGSN doesn't know TMSI + + + + + + + + + +MAP SEND AUTH INFO req + + + + + + + + + +MAP SEND AUTH INFO resp + + + + + + + + + +BSSGP DL-UD (LLC (GMM AUTH REQ)) + + + + + + + + + + +DL TBF establishment + + + +RLC/MAC Layer + + + + + + + + + +RLC/MAC (LLC (GMM AUTH REQ)) + + + + + + + + + +RLC/MAC (LLC (GMM AUTH RESP)) + + + + + + + + + +BSSGP UL-UD (LLC (GMM AUTH RESP)) + + + + + + + + + + + + +SRES(MS) == SRES(HLR) ? + + + + + + + + + +MAP UPD GPRS LOC AREA req + + + + + + + + + +MAP INSERT SUBSCR DATA req + + + + + + + + + +MAP INSERT SUBSCR DATA resp + + + + + + + + + +MAP UPD GPRS LOC AREA resp + + + + + + + + + +BSSGP DL-UD (LLC (GMM ATTACH ACCEPT)) + + + + + + + + + +RLC/MAC (LLC (GMM ATTACH ACCEPT)) + + + + + + + + + +RLC/MAC (LLC (GMM P-TMSI REALLOC COMPL) + + + + + + + + + +BSSGP (LLC (GMM P-TMSI REALLOC COMPL) + + + + + + diff --git a/2018/phone_protocol-eh2018/gprs_control_stack.svg b/2018/phone_protocol-eh2018/gprs_control_stack.svg new file mode 100644 index 0000000..8622512 --- /dev/null +++ b/2018/phone_protocol-eh2018/gprs_control_stack.svg @@ -0,0 +1,1341 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + MAC + RLC + LLC + + LLC + + E1 + + + + + PhysicalLayer + + + + + + + Um + A-bis + Gb + Gc + MS + BTS+CCU + BSC+PCU + SGSN + GPRS Control Plane + + + FrameRelay + NS + + BSSGP + + + E1 + + PhysicalLayer + TRAUFraming + + + MAC + RLC + + + E1 + + + + E1 + FrameRelay + NS + + BSSGP + TRAUFraming + + + + GMM + SM + + + GMM + SM + + E1 + + SCCP + + TCAP + + MAP + + MTP3 + + MTP2 + HLR + + E1 + + SCCP + + TCAP + + MAP + + MTP3 + + MTP2 + + + + + diff --git a/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.png b/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.png new file mode 100644 index 0000000..0bde375 Binary files /dev/null and b/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.png differ diff --git a/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.svg b/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.svg new file mode 100644 index 0000000..fff4e90 --- /dev/null +++ b/2018/phone_protocol-eh2018/gprs_pdp_ctx_act.svg @@ -0,0 +1,338 @@ + + + + + +MS + + + + +BTS/BSC/PCU + + + + +SGSN + + + + +GRX DNS + + + + +GGSN + + + + +Internet + + + + + + + + + + + +L1 RACH burst + + + + + + + + + + + + +RLC/MAC TBF establishment + + + + + + + + + + + +RLC/MAC (LLC (SM PDP CONTEXT ACT REQ)) + + + +APN=internet.foo.bar + + + + + + + + + + + +BSSGP UL-UD (LLC (SM PDP CONTEXT ACT REQ)) + + + +APN=internet.foo.bar + + + + + + + + + + + +DNS Lookup A record for APN + + + +internet.foo.bar.mncXXX.mccYYY.gprs + + + + + + + + + + + +DNS Response A record for APN + + + +internet.foo.bar.mncXXX.mccYYY.gprs + + + + + + + + + + + + + + +SGSN now knows IP address of GGSN for APN + + + + + + + + + + + +GTP-C (PDP CONTEXT ACT REQ) + + + + + + + + + + + + + + +Allocate IPv4 address + + + + + + + + + + + +GTP-C (PDP CONTEXT ACT RESP) + + + +IP addr + DNS + + + + + + + + + + + +BSSGP UL-UD (LLC (SM PDP CONTEXT ACT ACK)) + + + + + + + + + + + +RLC/MAC (LLC (SM PDP CONTEXT ACT ACK)) + + + + + + + + + + + + + + +MS now has IP addr + DNS server IP + + + + + + + + + + + + + + + + + +RLC/MAC (LLC (SNDCP (IP packet))) + + + + + + + + + + + +BSSGP UL-UD (LLC (SNDCP (IP packet))) + + + + + + + + + + + +GTP-U (IP packet) + + + + + + + + + + + +IP packet (e.g. ICMP ECHO REQ + + + + + + + + + + + + + + + + + +IP packet (e.g. ICMP ECHO RESP + + + + + + + + + + + +GTP-U (IP packet) + + + + + + + + + + + +BSSGP DL-UD (LLC (SNDCP (IP packet))) + + + + + + + + + + + +RLC/MAC (LLC (SNDCP (IP packet))) + + + + + + + + diff --git a/2018/phone_protocol-eh2018/gsm_cell_selection.png b/2018/phone_protocol-eh2018/gsm_cell_selection.png new file mode 100644 index 0000000..011be53 Binary files /dev/null and b/2018/phone_protocol-eh2018/gsm_cell_selection.png differ diff --git a/2018/phone_protocol-eh2018/gsm_control_stack.gnumeric b/2018/phone_protocol-eh2018/gsm_control_stack.gnumeric new file mode 100644 index 0000000..4a4cf60 Binary files /dev/null and b/2018/phone_protocol-eh2018/gsm_control_stack.gnumeric differ diff --git a/2018/phone_protocol-eh2018/gsm_control_stack.svg b/2018/phone_protocol-eh2018/gsm_control_stack.svg new file mode 100644 index 0000000..85ffc8a --- /dev/null +++ b/2018/phone_protocol-eh2018/gsm_control_stack.svg @@ -0,0 +1,2556 @@ + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/2018/phone_protocol-eh2018/location_update.png b/2018/phone_protocol-eh2018/location_update.png new file mode 100644 index 0000000..a1baa77 Binary files /dev/null and b/2018/phone_protocol-eh2018/location_update.png differ diff --git a/2018/phone_protocol-eh2018/location_update.svg b/2018/phone_protocol-eh2018/location_update.svg new file mode 100644 index 0000000..84de0ee --- /dev/null +++ b/2018/phone_protocol-eh2018/location_update.svg @@ -0,0 +1,505 @@ + + + + + +MSC + + + + +BTS + + + + +BSC + + + + +MSC/VLR + + + + +HLR + + + + + + + + + + + + + +GSM Location Update + + + + + + + + + + + + + + + +L1 RACH burst + + + + + + + + + + +RSL CHAN RQD + + + + + + + + + + + + + +Allocation of dedicated channel + + + + + + + + + + +RSL CHAN ACT + + + + + + + + + + +RSL CHAN ACT ACK + + + + + + + + + + +RSL IMM ASS CMD (RR IMM ASS) + + + + + + + + + + +AGCH: RR IMMEDIATE ASSIGN + + + + + + + + + + + + + +Switch form BCCH/CCCH + + + +to dedicated channel + + + + + + + + + + +LAPDm SABM (MM LOC UPD REQ) + + + + + + + + + + +RSL DATA IND (MM LOC UPD REQ + + + + + + + + + + +BSSAP COMPL L3 (MM LOC UPD REQ + + + + + + + + + + + + + + + + + + +optional: MM IDENTITY REQ + RESP (IMSI) if MSC doesn't know TMSI + + + + + + + + + + +MAP SEND AUTH INFO req + + + + + + + + + + + + + +Generate Auth Tuples + + + + + + + + + + +MAP SEND AUTH INFO resp + + + + + + + + + + +MM AUTH REQ + + + + + + + + + + +MM AUTH RESP + + + + + + + + + + + + + +SRES (MS) == SRES(HLR)? + + + + + + + + + + +MAP UPD LOC AREA req + + + + + + + + + + +MAP INSERT SUBSCR DATA req + + + + + + + + + + +MAP INSERT SUBSCR DATA resp + + + + + + + + + + +MAP UPD LOC AREA resp + + + + + + + + + + +BSSMAP CIPH MODE CMD + + + + + + + + + + +RSL ENCR CMD (RR CIPH MOD CMD) + + + + + + + + + + +RR CIPH MOD CMD + + + + + + + + + + +RR CIPH MOD COMPL + + + + + + + + + + +RSL DATA IND (RR CIPH MOD COMPL) + + + + + + + + + + +BSSMAP CIPH MODE COMPL + + + + + + + + + + +MM LOC UPD RESP + + + + + + + + + + +MM TMSI REALLOC COMPL + + + + + + + + + + +BSSMAP CLEAR CMD + + + + + + + + + + +RSL SACCH DEACT + + + + + + + + + + +RSL CHAN REL + + + + + + + + + + +LAPDm DISC + + + + + + + + + + + + + +Deactivate dedicated chan + + + + + + + + + + +RSL CHAN REL ACK + + + + + + + + + + + + + +Mark dedicated channel released + + + + + + + + + + +BSSMAP CLEAR COMPL + + + + + + + diff --git a/2018/phone_protocol-eh2018/location_update_l3only.png b/2018/phone_protocol-eh2018/location_update_l3only.png new file mode 100644 index 0000000..ac621d1 Binary files /dev/null and b/2018/phone_protocol-eh2018/location_update_l3only.png differ diff --git a/2018/phone_protocol-eh2018/location_update_l3only.svg b/2018/phone_protocol-eh2018/location_update_l3only.svg new file mode 100644 index 0000000..da26e9f --- /dev/null +++ b/2018/phone_protocol-eh2018/location_update_l3only.svg @@ -0,0 +1,215 @@ + + + + + +MSC + + + + +MSC/VLR + + + + +HLR + + + + + + + + + +GSM Location Update (L3 only) + + + + + + + + + + + +MM LOC UPD REQ + + + + + + + + + + + + + + + + +optional: MM IDENTITY REQ + RESP (IMSI) if MSC doesn't know TMSI + + + + + + + + +MAP SEND AUTH INFO req + + + + + + + + + + + +Generate Auth Tuples + + + + + + + + +MAP SEND AUTH INFO resp + + + + + + + + +MM AUTH REQ (RAND) + + + + + + + + +MM AUTH RESP (SRES) + + + + + + + + + + + +SRES(MS) == SRES(HLR) ? + + + + + + + + +MAP UPD LOC AREA req + + + + + + + + +MAP INSERT SUBSCR DATA req + + + + + + + + +MAP INSERT SUBSCR DATA resp + + + + + + + + +MAP UPD LOC AREA resp + + + + + + + + +CIPH MOD CMD + + + + + + + + +CIPH MOD COMPL + + + + + + + + +MM LOC UPD RESP + + + + + + + + +MM TMSI REALLOC COMPL + + + + + + + + +CLEAR CMD + + + + + + + + +CLEAR COMPL + + + + + diff --git a/2018/phone_protocol-eh2018/phone_powerup.adoc b/2018/phone_protocol-eh2018/phone_powerup.adoc new file mode 100644 index 0000000..2f592ec --- /dev/null +++ b/2018/phone_protocol-eh2018/phone_powerup.adoc @@ -0,0 +1,256 @@ +What happens on a protocol level when switching on a phone +========================================================== +:author: Harald Welte +:copyright: 2018 by Harald Welte (License: CC-BY-SA) +:backend: slidy +:max-width: 45em + +== Introduction + +* Everybody uses cellphones and mobile internet these days +* Still very few people know what's going on, even those with deep TCP/IP understanding +* Let's try to shed some light on the inner workings on a protocol level + +NOTE:: this talk is about 2G (GSM/GPRS/EDGE) and 3G (UMTS/HS*PA) only + +== Classic GSM (2G) network as digraph + +[graphviz] +---- +digraph G { + rankdir=LR; + MS0 [label="MS\n(Phone)"] + MS1 [label="MS\n(Phone)"] + MS2 [label="MS\n(Phone)"] + MS3 [label="MS\n(Phone)"] + BTS0 [label="BTS\n(Cell)"] + BTS1 [label="BTS\n(Cell)"] + MSC [label="MSC/VLR"] + HLR [label="HLR/AUC"] + MS0->BTS0 [label="Um"] + MS1->BTS0 [label="Um"] + MS2->BTS1 [label="Um"] + MS3->BTS1 [label="Um"] + BTS0->BSC [label="Abis"] + BTS1->BSC [label="Abis"] + BSC->MSC [label="A"] + MSC->HLR [label="C"] +} +---- + +== Powering up the phone + +* Your various processors / cores boot up +* Hardware gets initialized +* We will look at the cellular related activity only here +* Registering to a Cellular network can take *ages* at times. Why is that? + +== Network Selection (2G): RF Power Scan + +* GSM has many narrow-band channels/frequencies (ARFCN = Absolute Radio Frequency Channel Number): +** 123 ARFCN in 850 MHz +** 173 ARFCN in 900 MHz +** 373 ARFCN in 1800 MHz +** 298 ARFCN in 1900 MHz +** total of 967 ARFCN in a quad-band phone + +* The phone performs a (quick) RF power scan over all ARFCN to determine which channels contain how much energy (RxLev, RSSI) + +== Network Selection (2G): Freq + Sync burst detection + +* the phone picks the channels with highest amount of energy +* it tries to decode the FCCH (Frequency Correction Channel) to slave its own internal clock (VCTCXO) to the frequency information contained in the FCCH +* it then moves to the SCH (Synchronization Channel) to determine the current GSM frame number + training sequence code +* finally, it is aligned with both the *carrier frequency*, and knows where in the *time division multiplex* frame/multiframe the BTS (Cell) currently transmits + +== Network Selection (2G): BCCH decode + +* After Frequency and Sync burst detection, the phone moves to BCCH (Broadcast Common Control Channel) +* The BCCH contains a loop of repeated broadcasts of so-called *SYSTEM INFORMATION* messages +* There are many different *SYSTEM INFORMATION TYPEs* which are repeatedly iterated over +* SYSTEM INFORMATION (SI) 3 and 4 contain, among other things MCC + MNC information +** MCC: Mobile Country Code (262 for Germany) +** MNC: Mobile Network Code (01 for T-Mobile, 02 for Vodafone, 03 for E-Plus, ...) +* Now the phone knows to which operator the cell broadcasting on this ARFCN +* The process of FCCH + SCH alignment with successive BCCH decoding is repeated for a number of strong signal ARFCNs to create a list of "available networks" +** this is the output of what you see when you do a *manual network search* on your phone +*** the numeric MCC/MNC is typically translated in a string name based on a mapping table in the phone firmware, possibly extended by information on the SIM (EF.PNN, EF.OPL) + +== Network Selection: Which Network to register + +* Assuming we have a list of ARFCN <-> MCC+MNC, which network do we choose? +** if manual network selection: use whatever the user has chosen +** we assume automatic network selection below +* If the cell-advertised MCC+MNC matches the IMSI prefix, it is the home network +** home network trumps everything else +* SIM / USIM contains various lists which operators use to control selection policy in roaming +** EF.PLMNsel (PLMN Selector) +** EF.PLMNwAcT (User-controlled PLMN Selector with Access Technology) +** EF.HPPLMN (Higher Priority PLMN) +** EF.FPLMN (Forbidden PLMNs) +** EF.OPLMNwACT (Operator-controlled LMN Selector with Access Technology) +** EF.HPLMNwAcT (Home PLMN Selector with Access Technology) +** EF.EHPLMN (Equivalent HPLMN) +* finally, MS will select a (first) cell to attempt registration. + +== Cell Selection State Machine + +image::gsm_cell_selection.png[] + +== Registering to a network: LOCATION UPDATE + +* *LOCATION UPDATE* is a key transaction on the MM-sublayer of the Layer3 of the 2G/3G protocol stack +* it is used to update the location/presence information of the network +* there are variants: +** IMSI ATTACH is used for initial registration at power-up (our case here) +** NORMAL is an update triggered by a change of location (arae code) as the user moves around the coverage +** PERIODIC is used when a timer expires, similar to a 'keep alive' in many protocols +* the *MM LOCATION UPDATE* on the Um/Abis/A interface up to the MSC is translated into a *MAP UpdateLocation* towards the HLR (central subscriber database) +* authentication procedure may (should!) follow to cryptographically verify identity of subscriber +* finally, the network either sends a *MM LOCATION UPDATE ACCEPT* or *MM LOCATION UPDATE REJECT* + +== GSM Control Plane Protocol Stack + +image::gsm_control_stack.svg[width="100%"] + +== LOCATION UPDATE: Layer 3 Only + +image::location_update_l3only.png[] + +== LOCATION UPDATE: Ladder Diagram + +image::location_update.png[] + +== GPRS for packet switched servics + +[graphviz] +---- +digraph G { + rankdir=LR; + MS0 [label="MS\n(Phone)"] + MS1 [label="MS\n(Phone)"] + MS2 [label="MS\n(Phone)"] + MS3 [label="MS\n(Phone)"] + BTS0 [label="BTS\n(Cell)"] + BTS1 [label="BTS\n(Cell)"] + MSC [label="MSC/VLR"] + HLR [label="HLR/AUC"] + MS0->BTS0 [label="Um"] + MS1->BTS0 [label="Um"] + MS2->BTS1 [label="Um"] + MS3->BTS1 [label="Um"] + BTS0->BSC [label="Abis"] + BTS1->BSC [label="Abis"] + BSC->MSC [label="A"] + MSC->HLR [label="C"] + BTS0->PCU [color="red"] + BTS1->PCU [color="red"] + //subgraph cluster_PS { + PCU [color="red"]; + SGSN [color="red"]; + GGSN [color="red"]; + Internet [color="red"]; + PCU->SGSN [label="Gb",color="red"] + SGSN->GGSN [label="Gp",color="red"] + GGSN->Internet [label="Gi",color="red"] + // } +} +---- + + +== Registering for packet switched services: GPRS ATTACH + +* packet-switched services were added about a decade after circuit-switched +** hence, packet-switched attach is traditionally independent of circuit-switched attach +* GPRS ATTACH is performed from MS to SGSN +** it's called GPRS ATTACH even for EDGE or even UMTS + +== GPRS Control Plane Protocol Stack + +image::gprs_control_stack.svg[width="100%"] + +== GPRS ATTACH: Ladder Diagram + +image::gprs_attach.png[width="100%"] + +== Establishing a PDP Context + +* in order to exchange user-IP data with the public Internet, a tunnel must be established over the entire GSM/GPRS/UMTS infrastructure +** one Tunnel end is inside the phone +** other end is in the GGSN (Gateway GPRS Support Node) +** it's a true point-to-point link, no netmask/broadcast/arp/link-layer +** if PPP is involved, this is only between the phone/modem baseband processor and the external computer +* IP address allocation + DNS server addresses exchanged via *protocol control options (PCO)* inside PDP + context activation +* phone sends *PDP CONTEXT ACTIVATE* to network (SGSN) +* network (SGSN) responds with *PDP CONTEXT ACTIVATE ACK* in succesful case +* user IP data may now be exchanged + +== PDP CONTEXT ACT: Ladder Diagram + +image::gprs_pdp_ctx_act.png[width="100%"] + +== Classic UMTS (3G) network as digraph + +[graphviz] +---- +digraph G { + rankdir=LR; + MS0 [label="UE\n(Phone)"] + MS1 [label="UE\n(Phone)"] + MS2 [label="UE\n(Phone)"] + MS3 [label="UE\n(Phone)"] + BTS0 [label="NodeB\n(Cell)"] + BTS1 [label="NodeB\n(Cell)"] + BSC [label="RNC"]; + MSC [label="MSC/VLR"] + HLR [label="HLR/AUC"] + MS0->BTS0 [label="Uu"] + MS1->BTS0 [label="Uu"] + MS2->BTS1 [label="Uu"] + MS3->BTS1 [label="Uu"] + BTS0->BSC [label="Iub"] + BTS1->BSC [label="Iub"] + BSC->MSC [label="Iu-CS"] + SGSN [color="red"] + GGSN [color="red"] + Internet [color="red"] + BSC->SGSN [label="Iu-PS",color="red"] + SGSN->GGSN [label="Gp",color="red"] + SGSN->HLR [color="red"] + GGSN->Internet [label="Gi",color="red"] + MSC->HLR [label="C"] +} +---- + +== UMTS (3G) Cell Selection + +* differences primarily at physical layer +** WCDMA instead of TDMA (GSM) +** RF Channels are 5MHz wide, so many less RF channels to scan +** however, MS (now called UE) has to search in code-space, as many cells on same frequency channel + +== UMTS (3G) Cell Selection + +image::umts_cell_selection.png[] + +== UMTS (3G) Cell Selection + +* Layer 3 is almost identical to GSM +* *MM LOCATION UPDATE (Type: IMSI ATTACH)* between MS(UE) and MSC +* *PS ATTACH* between MS(UE) and SGSN +* *PDP CONTEXT ACTIVATION* between MS(UE) and SGSN + +== Further Reading + +* Die GSM Dm-Kanaele im Dialog, Prf. Dr. Joachim Goeller, http://www.informatik.hu-berlin.de/~goeller/isdn/DieGSMDmKanaele.pdf +* The GSM Dm-Channels (english version), http://www.informatik.hu-berlin.de/~goeller/isdn/GSMDmChannels.pdf +* 3GPP TS 43.022: "Functions related to Mobile Station in idle mode and + group receive mode" http://www.3gpp.org/DynaReport/43022.htm (GSM/GPRS) +* 3GPP TS 25.304 "User Equipment (UE) procedures in idle mode and + procedures for cell reselection in connected mode" + http://www.3gpp.org/DynaReport/25304.htm (UMTS_ + +== EOF + +End of File diff --git a/2018/phone_protocol-eh2018/phone_powerup.html b/2018/phone_protocol-eh2018/phone_powerup.html new file mode 100644 index 0000000..9992a60 --- /dev/null +++ b/2018/phone_protocol-eh2018/phone_powerup.html @@ -0,0 +1,4459 @@ + + + + +What happens on a protocol level when switching on a phone + + + + + + + + +
+

Introduction

+
+
    +
  • + +Everybody uses cellphones and mobile internet these days + +
    • +
  • + +Still very few people know what’s going on, even those with deep TCP/IP understanding + +
    • +
  • + +Let’s try to shed some light on the inner workings on a protocol level + +
    +
    +NOTE +
    +
    +

    +this talk is about 2G (GSM/GPRS/EDGE) and 3G (UMTS/HS*PA) only +

    +
    +
    +
    • +
+
+
+
+

Classic GSM (2G) network as digraph

+
+
+
+phone_powerup__1.png +
+
+
+
+
+

Powering up the phone

+
+
    +
  • + +Your various processors / cores boot up + +
    • +
  • + +Hardware gets initialized + +
    • +
  • + +We will look at the cellular related activity only here + +
    • +
  • + +Registering to a Cellular network can take ages at times. Why is that? + +
    • +
+
+
+
+

Network Selection (2G): RF Power Scan

+
+
    +
  • + +GSM has many narrow-band channels/frequencies (ARFCN = Absolute Radio Frequency Channel Number): + +
      +
    • + +123 ARFCN in 850 MHz + +
      • +
    • + +173 ARFCN in 900 MHz + +
      • +
    • + +373 ARFCN in 1800 MHz + +
      • +
    • + +298 ARFCN in 1900 MHz + +
      • +
    • + +total of 967 ARFCN in a quad-band phone + +
      • +
    +
    • +
  • + +The phone performs a (quick) RF power scan over all ARFCN to determine which channels contain how much energy (RxLev, RSSI) + +
    • +
+
+
+
+

Network Selection (2G): Freq + Sync burst detection

+
+
    +
  • + +the phone picks the channels with highest amount of energy + +
    • +
  • + +it tries to decode the FCCH (Frequency Correction Channel) to slave its own internal clock (VCTCXO) to the frequency information contained in the FCCH + +
    • +
  • + +it then moves to the SCH (Synchronization Channel) to determine the current GSM frame number + training sequence code + +
    • +
  • + +finally, it is aligned with both the carrier frequency, and knows where in the time division multiplex frame/multiframe the BTS (Cell) currently transmits + +
    • +
+
+
+
+

Network Selection (2G): BCCH decode

+
+
    +
  • + +After Frequency and Sync burst detection, the phone moves to BCCH (Broadcast Common Control Channel) + +
    • +
  • + +The BCCH contains a loop of repeated broadcasts of so-called SYSTEM INFORMATION messages + +
    • +
  • + +There are many different SYSTEM INFORMATION TYPEs which are repeatedly iterated over + +
    • +
  • + +SYSTEM INFORMATION (SI) 3 and 4 contain, among other things MCC + MNC information + +
      +
    • + +MCC: Mobile Country Code (262 for Germany) + +
      • +
    • + +MNC: Mobile Network Code (01 for T-Mobile, 02 for Vodafone, 03 for E-Plus, …) + +
      • +
    +
    • +
  • + +Now the phone knows to which operator the cell broadcasting on this ARFCN + +
    • +
  • + +The process of FCCH + SCH alignment with successive BCCH decoding is repeated for a number of strong signal ARFCNs to create a list of "available networks" + +
      +
    • + +this is the output of what you see when you do a manual network search on your phone + +
        +
      • + +the numeric MCC/MNC is typically translated in a string name based on a mapping table in the phone firmware, possibly extended by information on the SIM (EF.PNN, EF.OPL) + +
        • +
      +
      • +
    +
    • +
+
+
+
+

Network Selection: Which Network to register

+
+
    +
  • + +Assuming we have a list of ARFCN <→ MCC+MNC, which network do we choose? + +
      +
    • + +if manual network selection: use whatever the user has chosen + +
      • +
    • + +we assume automatic network selection below + +
      • +
    +
    • +
  • + +If the cell-advertised MCC+MNC matches the IMSI prefix, it is the home network + +
      +
    • + +home network trumps everything else + +
      • +
    +
    • +
  • + +SIM / USIM contains various lists which operators use to control selection policy in roaming + +
      +
    • + +EF.PLMNsel (PLMN Selector) + +
      • +
    • + +EF.PLMNwAcT (User-controlled PLMN Selector with Access Technology) + +
      • +
    • + +EF.HPPLMN (Higher Priority PLMN) + +
      • +
    • + +EF.FPLMN (Forbidden PLMNs) + +
      • +
    • + +EF.OPLMNwACT (Operator-controlled LMN Selector with Access Technology) + +
      • +
    • + +EF.HPLMNwAcT (Home PLMN Selector with Access Technology) + +
      • +
    • + +EF.EHPLMN (Equivalent HPLMN) + +
      • +
    +
    • +
  • + +finally, MS will select a (first) cell to attempt registration. + +
    • +
+
+
+
+

Cell Selection State Machine

+
+
+
+gsm_cell_selection.png +
+
+
+
+
+

Registering to a network: LOCATION UPDATE

+
+
    +
  • + +LOCATION UPDATE is a key transaction on the MM-sublayer of the Layer3 of the 2G/3G protocol stack + +
    • +
  • + +it is used to update the location/presence information of the network + +
    • +
  • + +there are variants: + +
      +
    • + +IMSI ATTACH is used for initial registration at power-up (our case here) + +
      • +
    • + +NORMAL is an update triggered by a change of location (arae code) as the user moves around the coverage + +
      • +
    • + +PERIODIC is used when a timer expires, similar to a keep alive in many protocols + +
      • +
    +
    • +
  • + +the MM LOCATION UPDATE on the Um/Abis/A interface up to the MSC is translated into a MAP UpdateLocation towards the HLR (central subscriber database) + +
    • +
  • + +authentication procedure may (should!) follow to cryptographically verify identity of subscriber + +
    • +
  • + +finally, the network either sends a MM LOCATION UPDATE ACCEPT or MM LOCATION UPDATE REJECT + +
    • +
+
+
+
+

GSM Control Plane Protocol Stack

+
+
+
+gsm_control_stack.svg +
+
+
+
+
+

LOCATION UPDATE: Layer 3 Only

+
+
+
+location_update_l3only.png +
+
+
+
+
+

LOCATION UPDATE: Ladder Diagram

+
+
+
+location_update.png +
+
+
+
+
+

GPRS for packet switched servics

+
+
+
+phone_powerup__2.png +
+
+
+
+
+

Registering for packet switched services: GPRS ATTACH

+
+
    +
  • + +packet-switched services were added about a decade after circuit-switched + +
      +
    • + +hence, packet-switched attach is traditionally independent of circuit-switched attach + +
      • +
    +
    • +
  • + +GPRS ATTACH is performed from MS to SGSN + +
      +
    • + +it’s called GPRS ATTACH even for EDGE or even UMTS + +
      • +
    +
    • +
+
+
+
+

GPRS Control Plane Protocol Stack

+
+
+
+gprs_control_stack.svg +
+
+
+
+
+

GPRS ATTACH: Ladder Diagram

+
+
+
+gprs_attach.png +
+
+
+
+
+

Establishing a PDP Context

+
+
    +
  • + +in order to exchange user-IP data with the public Internet, a tunnel must be established over the entire GSM/GPRS/UMTS infrastructure + +
      +
    • + +one Tunnel end is inside the phone + +
      • +
    • + +other end is in the GGSN (Gateway GPRS Support Node) + +
      • +
    • + +it’s a true point-to-point link, no netmask/broadcast/arp/link-layer + +
      • +
    • + +if PPP is involved, this is only between the phone/modem baseband processor and the external computer + +
      • +
    +
    • +
  • + +IP address allocation + DNS server addresses exchanged via protocol control options (PCO) inside PDP + context activation + +
    • +
  • + +phone sends PDP CONTEXT ACTIVATE to network (SGSN) + +
    • +
  • + +network (SGSN) responds with PDP CONTEXT ACTIVATE ACK in succesful case + +
    • +
  • + +user IP data may now be exchanged + +
    • +
+
+
+
+

PDP CONTEXT ACT: Ladder Diagram

+
+
+
+gprs_pdp_ctx_act.png +
+
+
+
+
+

Classic UMTS (3G) network as digraph

+
+
+
+phone_powerup__3.png +
+
+
+
+
+

UMTS (3G) Cell Selection

+
+
    +
  • + +differences primarily at physical layer + +
      +
    • + +WCDMA instead of TDMA (GSM) + +
      • +
    • + +RF Channels are 5MHz wide, so many less RF channels to scan + +
      • +
    • + +however, MS (now called UE) has to search in code-space, as many cells on same frequency channel + +
      • +
    +
    • +
+
+
+
+

UMTS (3G) Cell Selection

+
+
+
+umts_cell_selection.png +
+
+
+
+
+

UMTS (3G) Cell Selection

+
+
    +
  • + +Layer 3 is almost identical to GSM + +
    • +
  • + +MM LOCATION UPDATE (Type: IMSI ATTACH) between MS(UE) and MSC + +
    • +
  • + +PS ATTACH between MS(UE) and SGSN + +
    • +
  • + +PDP CONTEXT ACTIVATION between MS(UE) and SGSN + +
    • +
+
+
+
+

Further Reading

+
+ +
+
+
+

EOF

+
+

End of File

+
+
+ + diff --git a/2018/phone_protocol-eh2018/phone_powerup__1.png b/2018/phone_protocol-eh2018/phone_powerup__1.png new file mode 100644 index 0000000..ddd76c1 Binary files /dev/null and b/2018/phone_protocol-eh2018/phone_powerup__1.png differ diff --git a/2018/phone_protocol-eh2018/phone_powerup__2.png b/2018/phone_protocol-eh2018/phone_powerup__2.png new file mode 100644 index 0000000..c9cbe7c Binary files /dev/null and b/2018/phone_protocol-eh2018/phone_powerup__2.png differ diff --git a/2018/phone_protocol-eh2018/phone_powerup__3.png b/2018/phone_protocol-eh2018/phone_powerup__3.png new file mode 100644 index 0000000..fe9b211 Binary files /dev/null and b/2018/phone_protocol-eh2018/phone_powerup__3.png differ diff --git a/2018/phone_protocol-eh2018/umts_cell_selection.png b/2018/phone_protocol-eh2018/umts_cell_selection.png new file mode 100644 index 0000000..3579fb4 Binary files /dev/null and b/2018/phone_protocol-eh2018/umts_cell_selection.png differ -- cgit v1.2.3