Atnaujinkite slapukų nuostatas

El. knyga: Practical LTE based security forces PMR networks

(Ecole Nationale des Ponts et Chaussées & Halys, France)
Kitos knygos pagal šią temą:
Practical LTE based security forces PMR networksDidesnis paveikslėlis
Kitos knygos pagal šią temą:

DRM apribojimai

  • Kopijuoti:

    neleidžiama

  • Spausdinti:

    neleidžiama

  • El. knygos naudojimas:

    Skaitmeninių teisių valdymas (DRM)
    Leidykla pateikė šią knygą šifruota forma, o tai reiškia, kad norint ją atrakinti ir perskaityti reikia įdiegti nemokamą programinę įrangą. Norint skaityti šią el. knygą, turite susikurti Adobe ID . Daugiau informacijos  čia. El. knygą galima atsisiųsti į 6 įrenginius (vienas vartotojas su tuo pačiu Adobe ID).

    Reikalinga programinė įranga
    Norint skaityti šią el. knygą mobiliajame įrenginyje (telefone ar planšetiniame kompiuteryje), turite įdiegti šią nemokamą programėlę: PocketBook Reader (iOS / Android)

    Norint skaityti šią el. knygą asmeniniame arba „Mac“ kompiuteryje, Jums reikalinga  Adobe Digital Editions “ (tai nemokama programa, specialiai sukurta el. knygoms. Tai nėra tas pats, kas „Adobe Reader“, kurią tikriausiai jau turite savo kompiuteryje.)

    Negalite skaityti šios el. knygos naudodami „Amazon Kindle“.

Security forces PMR networks are moving from proprietary technologies for their "Mission Critical Push-To-Talk" basic service, and their data services--which must provide large bandwidth real-time access--to databases. LTE Based is adopted with backup access to public MNOs to complement their own radio coverage. Specific technologies such as multicasting of visio are required so the MCPTT works within a restricted bandwidth. The need to be able to change the main MNOs to provide resilient coverage requires specific choices of SIM cards, with OTAble security domains.

Practical LTE Based Security Forces PMR Networks assumes that the reader has a basic knowledge of the 4G network architecture and services, and the book focuses on the specific features and choices required to fulfill the need of security forces PMR networks. These include tactical and centralized, including LTE based voice services VoLTE and IMS. It can be used as a reference or textbook, with many detailed call flows and traces being included.

The author, who has a long teaching career in Operations Research, provides mathematical models for the optimization of tactical network federations, multicast coverage and allocation of preemptive priorities to PMR group members. He is a pioneer in the area of Virtual Roaming, an application of graph theory and telecommunications to provide roaming without direct relations, having previously published books on SMS Hubs, SS7 Hubs, Diameter Hubs, GTP Hubs. The use of M2M (monitoring devices) for security forces with mobility is covered in detail in the book, including the new LoRa virtual roaming which goes beyond the scope of PMR.
From the Same Author xvii
List of Figures
xix
List of Tables
xxiii
1 Introduction
1(8)
2 LTE PMR Networks: Service, Seamless Federation of Tactical Networks, Backup by the Public Operators' Coverage, and Direct Calls
9(20)
2.1 PMR tactical network elements
9(1)
2.2 PMR tactical networks' federation
10(5)
2.2.1 Operational needs' summary
10(1)
2.2.2 Radio planning and IP addressing of the various federated tactical networks
11(2)
2.2.3 Radio planning for mobility between tactical bubbles of a federation: Requirements and solution
13(1)
2.2.4 Initial configuration of a user to associate with its assigned group
14(1)
2.3 Federation method for N---1 concurrent networks with one taking the central role
15(2)
2.3.1 Architecture description
15(2)
2.4 Using the multicast for MCPTT and federating MBFSN areas
17(3)
2.4.1 Introduction to eMBMS
17(2)
2.4.1.1 Broadcast mode
19(1)
2.4.1.2 Multicast mode
19(1)
2.4.2 Attachment of a tactical network in an existing federation: GCS AS-centric architecture
19(1)
2.5 MBMS extension of the radio coverage of the new joining tactical network
20(5)
2.5.1 Crude basic federation (cross-copying) active service to another service area
20(1)
2.5.2 Federated MCEs or central MCE?
21(1)
2.5.2.1 MBMS LTE channels
21(2)
2.5.2.2 Meaning of "MBMS synchronization," role of the central or coordinated MCE
23(1)
2.5.2.3 Behavior of an MBMS-enabled UE
24(1)
2.5.2.4 Optimization of the MBMS channel allocation between federated groups
24(1)
2.5.2.5 Meaning of MBMS synchronization, role of the MCE
25(1)
2.6 Overview of a PMR or local loop network architecture: Inclusion of direct calls' support
25(2)
2.6.1 PMR HLR-HSS capabilities and architecture
25(1)
2.6.2 Proximity services (ProSe)
26(1)
References
27(2)
3 Geo-Localization of PMR Group Members and Monitoring of the Quality of Service with the ECID Method
29(12)
3.1 Operational need for a geo-localization service in PMR networks
29(1)
3.2 Localization methods in tactical networks
30(1)
3.2.1 Enabling the LPP protocol in the UEs
30(1)
3.2.2 Using SUPL as main geo-localization protocol
30(1)
3.3 ECID positioning method (LPP control plane) using a graphic interface
31(1)
3.4 Cell database for the ECID method yielding the UE received signal level
31(2)
3.5 Why not use GPS positioning method (LPP control plane)?
33(2)
3.6 ECID method: Calculation of the physical measures from the measurements received from the UE
35(4)
3.6.1 RSRP measurement → Dbm values for signal level at the UE
35(1)
3.6.2 UE Rx-Tx → distance estimate between UE and eNodeB
35(2)
3.6.3 Field results and coverage comparisons between various eNodeBs
37(1)
3.6.4 Operational use and presentation of the ECID method results in PMR tactical networks
37(2)
References
39(2)
4 Choice of the SIM Card Type for PMR or M2M Networks and Automatic Profile Switching Possibilities
41(34)
4.1 Classical UICC, eUICC M2M, or eUICC "consumer" SIM cards
41(1)
4.1.1 Usage difference
41(1)
4.1.2 Difference of logical structure between UICC and eUICC
42(1)
4.1.2.1 eUICC
42(1)
4.1.2.2 UICC
43(1)
4.1.2.3 Recent file additions for all card types
44(1)
4.2 Remote provisioning system for eUICC (M2M and consumer)
44(1)
4.2.1 Explanation of the remote provisioning figure
45(1)
4.3 eUICC and UICC profile switching methods
45(1)
4.3.1 Add IMSI with its own security domain in UICC by OTA
45(1)
4.3.1.1 Logical organization of a multi-security domain UICC SIM card
45(3)
4.3.1.2 Add a new IMSI with its own security domain
48(4)
4.3.1.3 Summary of the applet management commands
52(1)
4.3.2 Updating the OTA security keys KiC and Kid in multi-IMSI UICC cards
52(1)
4.4 Is it possible to reduce the automatic network switching time VPLMN → HPLMN?
52(1)
4.4.1 The TS 23.122 3GPP standard
52(1)
4.4.1.1 Automatic network selection mode procedure
52(1)
4.4.1.2 (In VPLMN) automatic and manual network selection modes
53(1)
4.4.1.3 Reducing the timer T
54(1)
4.5 OTA provisioning of the SIM: "card initiated OTA SIM with IP" or "network initiated" using SMS
55(1)
4.5.1 OTA SIM over IP
55(1)
4.5.1.1 Legacy network initiated
56(1)
4.5.1.2 Card initiated
56(1)
4.5.2 Card initiated mode with a data connection to the OTA IP server
56(1)
4.5.2.1 BIP/CAT-TP
56(1)
4.5.2.2 OTA over https
57(5)
4.5.3 Network initiated SMS triggering of a SIM IP connection (BIP/CAT-TP or https) to the OTA server
60(2)
4.5.4 GSMa SP02 v3.2
62(1)
4.6 Profile update of the security domain and protection against the cloning of a stolen SIM
62(1)
4.7 Application provisioning in the device (not in the SIM card)
63(1)
4.8 Is being a full MVNO justified for an autonomous car manufacturer?
63(8)
4.8.1 Current high latency connected applications from the car to the manufacturer
63(2)
4.8.2 The next big thing: Autonomous vehicle with sensors
65(1)
4.8.3 Data trafic costs comparison between local IMSI and full MVNO
66(1)
4.8.4 Security discussion: Local IMSI compared to own IMSI as a full MVNO
66(1)
4.8.5 Supplementary features provided by the full MVNO model
67(1)
4.8.6 Minimum setup for a car manufacturer to manage their SDVIs: OTA-IP server
68(1)
4.8.6.1 Need to have its own OTA server for its own management of the SIMs and the SW updates
68(2)
4.8.6.2 Consequence: The card manufacturer must be a full MVNO
70(1)
4.8.6.3 Summary table of the 2018 solutions for car manufacturers
71(1)
References
71(4)
5 Group Communication Provisioning by OTA, SMS 4G, and SMS IMS
75(32)
5.1 Operational need for OTA provisioning in PMR networks
75(1)
5.2 SMS service convergence 2G, 3G, 4G, SIP, and SMPP in other non-PMR cases
76(1)
5.3 SMS in the EUTRAN 4G domain
76(2)
5.4 SMS procedure to handle destinations in 4G networks
78(10)
5.4.1 SMS procedure and call flow
78(1)
5.4.2 Virtualized type 1 implementation example
79(2)
5.4.3 HLR-HSS interrogation with MAP/SS7 (3GPP TS 29.002)
81(1)
5.4.4 HLR-HSS interrogation with S6c/diameter (3GPP TS 29.338)
82(1)
5.4.5 SIP registration in the SM-IP-GW to receive SMS with SIP MESSAGES
82(1)
5.4.5.1 Standard 3GP registration for SIP message reception
82(1)
5.4.5.2 MAP traces for ANY-TIME-MODMCATION IP-SM-GW → HLR-HSS
83(3)
5.4.5.3 Standard 3GP deregistration for SIP message reception
86(1)
5.4.5.4 Registration of the reachability for SMS in the IP-SM-GW with Map Note Subscriber Data Modified
87(1)
5.4.5.5 Simpler registration for SIP message reception (recommended)
88(1)
5.5 Detailed procedure for SMS-MT and SMS-MO single segment
88(1)
5.5.1 SMS-MT
89(1)
5.5.2 SMS-MO
89(1)
5.6 Long SMS with segmentation
89(11)
5.6.1 Long SMS-MT from 3G to a 4G coverage handset
89(6)
5.6.2 The 4G resends (SMS-MO) the long SMS received from the 3G
95(5)
5.7 Application to OTA SIM in pure PMR 4G networks
100(1)
5.8 Mobile and fixed number portability with Dx/diameter to send SMS to IMS networks
100(3)
5.8.1 LIR/Cx/diameter is the equivalent IMS of a legacy 3G MAP SEND-ROUTING JNFO req
100(1)
5.8.2 Principle of the use of the location-information-request/Cx diameter to resolve the portability
101(1)
5.8.3 Fixed → mobile portability
102(1)
5.8.4 How to implement the portability of a number in the ported-out network
102(1)
5.9 3G ↔ SIP MMS interworking
103(1)
5.9.1 SIP receiving of 3G MMS
104(1)
5.9.2 Sending an MMS from the SIP client to a 3G UE
104(1)
References
104(3)
6 Multicast: MCPTT PMR, MOOC Teaching, and TV in Local Loop Networks (RTTH)
107(20)
6.1 Operational need for multicast in PMR networks
107(1)
6.2 Triple play, the need for multicast TV and massive open online course (MOOC)
108(2)
6.3 Quantitative elementary modeling of the fiber vs 4G local loop choice
110(4)
6.3.1 Average distance center - household with fibering
111(1)
6.3.2 Cost model for the fibering solution to the home (FTTH) vs 4G Radio (RTTH)
112(2)
6.4 3GPP multicast architecture
114(1)
6.5 Detailed call flow of an MBMS session
114(7)
6.5.1 Overall call flow
115(4)
6.5.2 M3/diameter messages MCE → MME: Role of the MCE
119(2)
6.5.3 M2/diameter messages eNodeB H MCE
121(1)
6.5.4 "Joining" (MBMS multicast activation by the user) GC1 UE → application server
121(1)
6.6 Centralized or distributed multicast coordination entity (MCE)
121(1)
6.7 MBMS delivery and eMBMS-capable device stack
121(2)
6.7.1 Group communication delivery appeared in [ 6.7Rel 13]
123(1)
6.7.2 Transparent delivery appeared in [ 6.7 Rel 14] and other modes
123(1)
6.8 Interoperability: Intergroup and interagency communication
123(1)
6.9 Architecture with virtual machines
123(1)
References
124(3)
7 Integration of IMS and VoLTE in the PMR Networks and the MNOs, Details on the PCC Processing, and Access Using a Non-trusted WLAN (WiFi with an ePDG)
127(46)
7.1 WiFi and V6LTE4G access to a PMR central core network
127(2)
7.2 Operational need for VoLTE in PMR networks
129(1)
7.3 Reminder of the VoTT architecture for a pure VoIP MNO
129(2)
7.3.1 Public identity for VoTT VoIP vs LTE
129(1)
7.3.2 VoTT VoIP network architecture
129(2)
7.4 IMS-based PMR network architecture for the services
131(4)
7.4.1 Equivalence between 3G/2G notions, VoLTE/IMS, WiFi EAPsiim/VoTT, and SIP VoTT
131(1)
7.4.2 Equivalence between 3G/4G notions and the equivalent in IMS (mobility management of Cx/diameter)
131(2)
7.4.3 Incoming call (protocol Cx/diameter)
133(1)
7.4.4 IMS subscriber's services' management (protocol Sh/diameter)
133(2)
7.5 Call flow of the IMS services
135(15)
7.5.1 IMS registration: Voice calls
135(2)
7.5.1.1 Authentication of the subscriber, VoLTE and OTT VoIP compatible core IMS: MAR and MAA/Cx messages
137(2)
7.5.1.2 Registration in the HSS to be able to receive calls and SMS
139(1)
7.5.1.3 De-registration of a subscriber
140(1)
7.5.2 Handling of incoming calls or SMS from the PSTSN or the SS7 network
140(1)
7.5.2.1 Emergency call handling in IMS with calling party localization
140(2)
7.5.2.2 SMS
142(1)
7.5.2.3 Charging of the calls and SMS
142(2)
7.5.3 Outgoing SMS or voice calls to the SS7 network or the PSTN
144(1)
7.5.3.1 SMS
144(1)
7.5.3.2 Charging
145(1)
7.5.3.3 3G Voice calls to a subscriber in a mobile network: Non-IMS case
145(1)
7.5.4 Anti-tromboning of the calls to mobiles 3G: The SORTA method [ 7.16] passive camel monitoring and MAP call transfer package
145(1)
7.5.4.1 The general tromboning for outgoing calls to 3G with conditional forwarding of unsuccessful calls
145(2)
7.5.4.2 Anti-tromboning #1, 3GPP MAP method, not applicable in practice
147(1)
7.5.4.3 Anti-tromboning # 2, pure ISUP handling by the GMSC-IMS: Simple but not quite general
148(1)
7.5.4.4 Anti-tromboning # 3, the SORTA method [ 7.16]: CAMEL and use of MAP Resume Call Handling By A Camel Handling SCP: Rigorous
149(1)
7.5.4.5 Trace details CAMEL and MAP of the SORTA anti-tromboning
149(1)
7.6 What brings VoLTE, interest of IMS for the combined mobile-fixed service
150(1)
7.7 Roaming VoLTE with local break out
151(1)
7.8 Traces of user data (subscriber profile) in a server assignment answer (SAA/Cx)
151(3)
7.9 IMS files and certificates in the SIM card
154(2)
7.9.1 IMS files in an ISIM card
154(1)
7.9.2 SIM files with the root certificate
155(1)
7.10 QoS parameter mapping GTPv2 ← Gx ← Rx ← application function
156(9)
7.10.1 Dedicated bearer creation, traces Rx and Gx
156(6)
7.10.2 PCRF processing: Correspondences between the GTPv2 parameters and the AVPs Gx et Rx
162(3)
7.11 Access through a non-trusted WLAN (WiFi) to the PMR core networking
165(4)
7.11.1 Operational interest
165(1)
7.11.2 Call flow to establish the IPsec tunnel and localize a WiFi UE in the HLR-HSS
165(4)
References
169(4)
8 Lawful Interception 3GPP Architecture and PMR Network Case
173(8)
8.1 Legal interception applied to PMR networks: Use for monitoring and security
173(1)
8.2 The LI standard 3GPP architecture
173(3)
8.2.1 Proprietary interfaces of the network equipment and standardization
173(1)
8.2.2 LI management notification operation (HI 1 interface)
174(2)
8.2.3 HI2: Handover interface port 2 (ASN1 coding)
176(1)
8.2.4 HI3: Handover interface port 3
176(1)
8.3 Services concerned by the interception need
176(1)
8.4 Practical use of the content interception HI3 or X3
177(2)
8.4.1 Use of metadata
177(1)
8.4.2 Non-judiciary interception methods of security agencies
177(2)
References
179(2)
9 Diameter-Based M2M (LTE-M and NB-IoT) 3GPP Services and LoRa
181(24)
9.1 Operational need for M2M in PMR networks
181(1)
9.2 3GPP NB-IOT type of services between the AS IoT server and the M2M devices: Direct, indirect, and hybrid model implementations
181(2)
9.3 Necessary additional diameter protocols in an "IoT ready" EPC for the "indirect model"
183(4)
9.3.1 T4 interface from the application IoT to the MTC-IWF and then to the SMSC
183(2)
9.3.2 S6m and S6t interfaces with the HLR-HSS TS 29.336
185(1)
9.3.3 T6a and T6b interfaces between MME or SGSN and MTC-IWF TS 29.128
186(1)
9.3.4 Tsp interface between the SCS and the MTC-IWF (TS 29.368)
186(1)
9.3.5 Implementation strategy, what is the simplest and most general implementation for IoT
186(1)
9.4 LoRa
187(10)
9.4.1 The LoRaWAN architecture
187(1)
9.4.1.1 End-device (equivalent of combined UE +SIM card)
187(1)
9.4.1.2 Radio gateway (equivalent of an RNC 3G)
187(1)
9.4.1.3 Network server (equivalent of SGSN 3G (no GGSN equivalent used))
188(1)
9.4.1.4 Central DNS of the LoRa alliance
189(2)
9.4.1.5 Join server (equivalent of an HLR for just the authentication function)
191(2)
9.4.1.6 Application server
193(3)
9.4.1.7 Packet transmission
196(1)
9.4.2 Device classes
196(1)
9.4.3 Device addressing, LoRa roaming, and LoRa hubs
196(1)
9.5 LoRa virtual roaming hubs
197(6)
9.5.1 Architecture principles
197(1)
9.5.2 Setups between a LoRa hub operator and visited LoRa network partners
198(1)
9.5.3 Detailed explanation of the LoRa hub operation
199(1)
9.5.3.1 Commercial aims: No agreement between the visited and home LoRa networks, one-stop shopping with the LoRa hub operator
199(1)
9.5.3.2 Explanation of the control plane call flow
199(1)
9.5.3.3 User data call flow for a LoRa hub
200(1)
9.5.4 Geo-localization in LoRa and applications: TDOA is the most appropriate method
200(3)
References
203(2)
10 Advanced Policy Control and Charging (PCC), Standard Provisioning Architecture for HLR-HSS and PCRF
205(16)
10.1 Destination IP-dependent charging with an external DPI (deep packet inspection)
205(13)
10.1.1 Architecture consequence to satisfy the rerouting requirement
206(1)
10.1.2 Rating plan-dependent charging
206(1)
10.1.3 Data charging diagram
207(1)
10.1.4 Slow-down policing with an external DPI
207(6)
10.1.4.1 Gx-based slow-down policing implementation in the DPI
213(1)
10.1.4.2 Rx-Based slow-down policing implementation in the DPI
213(1)
10.1.5 Traces for the charging by an external DPI
213(1)
10.1.5.1 Data provided by the GGSN-PGW which may be used for charging
213(2)
10.1.5.2 RADIUS interface between GGSN-PGW and PCEF-DPI (which is the radius server)
215(1)
10.1.5.3 Content of the RADIUS accounting-request (start) received by the PCEF-DPI
216(1)
10.1.5.4 Content of the RADIUS accounting-request (stop) receive by the PCEF-DPI
217(1)
10.2 Standard 3GPP user data provisioning: LDAP and SOAP
218(2)
10.2.1 3GPP user data repository architecture
218(2)
References
220(1)
11 Appendix: Detailed Traces for the Different
Chapters
221(2)
11.1 Triggering the IP connection of the SIM IP to the OTA-IP server
221(2)
11.1.1 OTA-IP configuration of the SIM for TCP (HTTPs) for UDP (BIP/CAT-TP)
221(1)
11.1.2 Triggering the OTA-IP connection from the "applet for OTA pull" or with an SMS-MT
221(2)
11.1.3 Details of the SMS-MT to network initiate a forced BIP/CAT-TP (IP UDP connection to the OTA server while the SIM configuration is IP TCP (HTTPs)
223
11.1.3.1 Coding of the SMS-MT payload (ETSI TS 223 to open the BIP and CAT-TP channels
223(1)
11.1.3.2 SMS-MT parameters details (TS 23.040)
224(2)
11.1.3.3 Opening of the IP channel by the SIM card
226(1)
11.1.3.4 Confirmation of the reception of triggering SMS-MT by the SIM and of the establishment of the IP UDP channel to the OTA IP server
227(1)
11.1.3.5 OTA-IP sequence of commands (read IMSI)
227(1)
11.1.3.6 SMS-MO received by the OTA server with the PoR
228(1)
11.1.3.7 Completion and closing of the OTA-IP session
229(1)
11.2 SMS-MT with diameter SMSC → UE
230(15)
11.2.1 SMS-MO with diameter UE → SMSC
236(9)
11.3 Multicast: Traces M2AP, M3AP, Sgmb, and GTP V2
245(11)
11.3.1 M2 SETUP request eNodeB → MCE
245(1)
11.3.2 M3 SETUP request MCE → MME
245(1)
11.3.3 M3 SETUP response MME → MCE
246(1)
11.3.4 M2 SETUP response MCE → NodeB
247(1)
11.3.5 Sgmb RAR BM-SC → MBMS GW
247(2)
11.3.6 GTPV2 MBMS session start request MBMS GW → MME
249(2)
11.3.7 SGmb RAA MBMS GW → BM-SC
251(2)
11.3.8 M3 MBMS session start request MME → MCE
253(2)
11.3.9 M3 MBMS session start response MCE → MME
255(1)
11.3.10 GTPV2 MBMS session start response MME H MBMS GW
255(1)
11.4 Traces IoT
256(29)
11.4.1 Subscriber information request (SIR) and answer (SIA) MTC-IWF → HSS S6m/diameter
257(6)
11.4.2 Devices trigger request (DTR) and answer (DTA) MTC-IWF → SMSC T4/diameter
263(6)
11.4.3 Transfer forward request (TFR) and answer (TFA) SMSC → MME Sgd/diameter (SMS-MT)
269(4)
11.4.3.1 Uplink NAS transport request MME → UE and downlink NAS transport UE → MME
273(9)
11.4.4 Delivery report request (DRR) and answer (DRA) SMSC → MTC-IWF T4/diameter
282(3)
11.5 Traces of a recursive DNS request
285(4)
12 Conclusion: Full LTE for Security Forces, When?
289(4)
References
291(2)
Abbreviations and Acronyms 293(32)
Index 325(4)
About the Author 329
Arnaud Henry-Labordere is at Ecole Nationale des Ponts et Chaussées & Halys, France.
Daugiau apie elektronines knygas Daugiau apie elektronines knygas
Pastovi nuoroda: https://www.kriso.lt/db/97810007934512e.html