UID:
almafu_9959797977402883
Format:
1 online resource (356 pages).
Edition:
1st ed.
ISBN:
1-000-79622-1
,
1-00-333912-3
,
1-003-33912-3
,
1-000-79345-1
,
87-93609-78-7
Series Statement:
River Publishers Series in Security and Digital Forensics Series
Content:
It can be used as a reference or textbook, with many detailed call flows and traces being included. The author, who has also 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.
Note:
Cover -- Half Title -- Series -- Title -- Copyright -- Contents -- From the Same Author -- List of Figures -- List of Tables -- 1 Introduction -- 2 LTE PMR Networks: Service, Seamless Federation of Tactical Networks, Backup by the Public Operators' Coverage, and Direct Calls -- 2.1 PMR tactical network elements -- 2.2 PMR tactical networks' federation -- 2.2.1 Operational needs' summary -- 2.2.2 Radio planning and IP addressing of the various federated tactical networks -- 2.2.3 Radio planning for mobility between tactical bubbles of a federation: Requirements and solution -- 2.2.4 Initial configuration of a user to associate with its assigned group -- 2.3 Federation method for N−1 concurrent networks with one taking the central role -- 2.3.1 Architecture description -- 2.4 Using the multicast for MCPTT and federating MBFSN areas -- 2.4.1 Introduction to eMBMS -- 2.4.1.1 Broadcast mode -- 2.4.1.2 Multicast mode -- 2.4.2 Attachment of a tactical network in an existing federation: GCS AS-centric architecture -- 2.5 MBMS extension of the radio coverage of the new joining tactical network -- 2.5.1 Crude basic federation (cross-copying) active service to another service area -- 2.5.2 Federated MCEs or central MCE? -- 2.5.2.1 MBMS LTE channels -- 2.5.2.2 Meaning of "MBMS synchronization," role of the central or coordinated MCE -- 2.5.2.3 Behavior of an MBMS-enabled UE -- 2.5.2.4 Optimization of the MBMS channel allocation between federated groups -- 2.5.2.5 Meaning of MBMS synchronization, role of the MCE -- 2.6 Overview of a PMR or local loop network architecture: Inclusion of direct calls' support -- 2.6.1 PMR HLR-HSS capabilities and architecture -- 2.6.2 Proximity services (ProSe) -- References -- 3 Geo-Localization of PMR Group Members and Monitoring of the Quality of Service with the ECID Method.
,
3.1 Operational need for a geo-localization service in PMR networks -- 3.2 Localization methods in tactical networks -- 3.2.1 Enabling the LPP protocol in the UEs -- 3.2.2 Using SUPL as main geo-localization protocol -- 3.3 ECID positioning method (LPP control plane) using a graphic interface -- 3.4 Cell database for the ECID method yielding the UE received signal level -- 3.5 Why not use GPS positioning method (LPP control plane)? -- 3.6 ECID method: Calculation of the physical measures from the measurements received from the UE -- 3.6.1 RSRP measurement → Dbm values for signal level at the UE -- 3.6.2 UE Rx-Tx → distance estimate between UE and eNodeB -- 3.6.3 Field results and coverage comparisons between various eNodeBs -- 3.6.4 Operational use and presentation of the ECID method results in PMR tactical networks -- References -- 4 Choice of the SIM Card Type for PMR or M2M Networks and Automatic Profile Switching Possibilities -- 4.1 Classical UICC, eUICC M2M, or eUICC "consumer" SIM cards -- 4.1.1 Usage difference -- 4.1.2 Difference of logical structure between UICC and eUICC -- 4.1.2.1 eUICC -- 4.1.2.2 UICC -- 4.1.2.3 Recent file additions for all card types -- 4.2 Remote provisioning system for eUICC (M2M and consumer) -- 4.2.1 Explanation of the remote provisioning figure -- 4.3 eUICC and UICC profile switching methods -- 4.3.1 Add IMSI with its own security domain in UICC by OTA -- 4.3.1.1 Logical organization of a multi-security domain UICC SIM card -- 4.3.1.2 Add a new IMSI with its own security domain -- 4.3.1.3 Summary of the applet management commands -- 4.3.2 Updating the OTA security keys KiC and Kid in multi-IMSI UICC cards -- 4.4 Is it possible to reduce the automatic network switching time VPLMN → HPLMN? -- 4.4.1 The TS 23.122 3GPP standard -- 4.4.1.1 Automatic network selection mode procedure.
,
4.4.1.2 (In VPLMN) automatic and manual network selection modes -- 4.4.1.3 Reducing the timer T -- 4.5 OTA provisioning of the SIM: "card initiated OTA SIM with IP" or "network initiated" using SMS -- 4.5.1 OTA SIM over IP -- 4.5.1.1 Legacy network initiated -- 4.5.1.2 Card initiated -- 4.5.2 Card initiated mode with a data connection to the OTA IP server -- 4.5.2.1 BIP/CAT-TP -- 4.5.2.2 OTA over https -- 4.5.3 Network initiated SMS triggering of a SIM IP connection (BIP/CAT-TP or https) to the OTA server -- 4.5.4 GSMa SP02 v3.2 -- 4.6 Profile update of the security domain and protection against the cloning of a stolen SIM -- 4.7 Application provisioning in the device (not in the SIM card) -- 4.8 Is being a full MVNO justified for an autonomous car manufacturer? -- 4.8.1 Current high latency connected applications from the car to the manufacturer -- 4.8.2 The next big thing: Autonomous vehicle with sensors -- 4.8.3 Data trafic costs comparison between local IMSI and full MVNO -- 4.8.4 Security discussion: Local IMSI compared to own IMSI as a full MVNO -- 4.8.5 Supplementary features provided by the full MVNO model -- 4.8.6 Minimum setup for a car manufacturer to manage their SIMs: OTA-IP server -- 4.8.6.1 Need to have its own OTA server for its own management of the SIMs and the SW updates -- 4.8.6.2 Consequence: The card manufacturer must be a full MVNO -- 4.8.6.3 Summary table of the 2018 solutions for car manufacturers -- References -- 5 Group Communication Provisioning by OTA, SMS 4G, and SMS IMS -- 5.1 Operational need for OTA provisioning in PMR networks -- 5.2 SMS service convergence 2G, 3G, 4G, SIP, and SMPP in other non-PMR cases -- 5.3 SMS in the EUTRAN 4G domain -- 5.4 SMS procedure to handle destinations in 4G networks -- 5.4.1 SMS procedure and call flow -- 5.4.2 Virtualized type 1 implementation example.
,
5.4.3 HLR-HSS interrogation with MAP/SS7 (3GPP TS 29.002) -- 5.4.4 HLR-HSS interrogation with S6c/diameter (3GPP TS 29.338) -- 5.4.5 SIP registration in the SM-IP-GW to receive SMS with SIP MESSAGES -- 5.4.5.1 Standard 3GP registration for SIP message reception -- 5.4.5.2 MAP traces for ANY-TIME-MODIFICATION IP-SM-GW → HLR-HSS -- 5.4.5.3 Standard 3GP deregistration for SIP message reception -- 5.4.5.4 Registration of the reachability for SMS in the IP-SM-GW with MAP NOTE SUBSCRIBER DATA MODIFIED -- 5.4.5.5 Simpler registration for SIP message reception (recommended) -- 5.5 Detailed procedure for SMS-MT and SMS-MO single segment -- 5.5.1 SMS-MT -- 5.5.2 SMS-MO -- 5.6 Long SMS with segmentation -- 5.6.1 Long SMS-MT from 3G to a 4G coverage handset -- 5.6.2 The 4G resends (SMS-MO) the long SMS received from the 3G -- 5.7 Application to OTA SIM in pure PMR 4G networks -- 5.8 Mobile and fixed number portability with Dx/diameter to send SMS to IMS networks -- 5.8.1 LIR/Cx/diameter is the equivalent IMS of a legacy 3G MAP SEND ROUTING INFO req -- 5.8.2 Principle of the use of the location-information-request/Cx diameter to resolve the portability -- 5.8.3 Fixed ↔ mobile portability -- 5.8.4 How to implement the portability of a number in the ported-out network -- 5.9 3G ↔ SIP MMS interworking -- 5.9.1 SIP receiving of 3G MMS -- 5.9.2 Sending an MMS from the SIP client to a 3G UE -- References -- 6 Multicast: MCPTT PMR, MOOC Teaching, and TV in Local Loop Networks (RTTH) -- 6.1 Operational need for multicast in PMR networks -- 6.2 Triple play, the need for multicast TV and massive open online course (MOOC) -- 6.3 Quantitative elementary modeling of the fiber vs 4G local loop choice -- 6.3.1 Average distance center - household with fibering -- 6.3.2 Cost model for the fibering solution to the home (FTTH) vs 4G Radio (RTTH) -- 6.4 3GPP multicast architecture.
,
6.5 Detailed call flow of an MBMS session -- 6.5.1 Overall call flow -- 6.5.2 M3/diameter messages MCE ↔ MME: Role of the MCE -- 6.5.3 M2/diameter messages eNodeB ↔ MCE -- 6.5.4 "Joining" (MBMS multicast activation by the user) GC1 UE → application server -- 6.6 Centralized or distributed multicast coordination entity (MCE) -- 6.7 MBMS delivery and eMBMS-capable device stack -- 6.7.1 Group communication delivery appeared in [6.7 Rel 13] -- 6.7.2 Transparent delivery appeared in [6.7 Rel 14] and other modes -- 6.8 Interoperability: Intergroup and interagency communication -- 6.9 Architecture with virtual machines -- References -- 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) -- 7.1 WiFi and VoLTE4G access to a PMR central core network -- 7.2 Operational need for VoLTE in PMR networks -- 7.3 Reminder of the VoTT architecture for a pure VoIP MNO -- 7.3.1 Public identity for VoTT VoIP vs LTE -- 7.3.2 VoTT VoIP network architecture -- 7.4 IMS-based PMR network architecture for the services -- 7.4.1 Equivalence between 3G/2G notions, VoLTE/IMS, WiFi EAPsiim/VoTT, and SIP VoTT -- 7.4.2 Equivalence between 3G/4G notions and the equivalent in IMS (mobility management of Cx/diameter) -- 7.4.3 Incoming call (protocol Cx/diameter) -- 7.4.4 IMS subscriber's services' management (protocol Sh/diameter) -- 7.5 Call flow of the IMS services -- 7.5.1 IMS registration: Voice calls -- 7.5.1.1 Authentication of the subscriber, VoLTE and OTT VoIP compatible core IMS: MAR and MAA/Cx messages -- 7.5.1.2 Registration in the HSS to be able to receive calls and SMS -- 7.5.1.3 De-registration of a subscriber -- 7.5.2 Handling of incoming calls or SMS from the PSTSN or the SS7 network -- 7.5.2.1 Emergency call handling in IMS with calling party localization -- 7.5.2.2 SMS.
,
7.5.2.3 Charging of the calls and SMS.
Additional Edition:
ISBN 87-93609-79-5
Language:
English