Switzerland is implementing NG112 to modernize its emergency communications system. Key aspects include routing emergency calls through network-based caller location, handling device-based location data from systems like eCall and AML, and ensuring accessibility across languages and networks. While many goals align with EU standards, some aspects vary due to Switzerland's federalist system and independent regulation. Close cooperation between public safety authorities, regulators, and telecom operators will be important for a successful transition, with lessons around testing, central coordination, and a flexible approach to standards.

1. How Switzerland is
implementing NG112
Beat Egger
V 1.1
22.09.2021
Sicherheitsklassifizierung C1 public

2. • Population approx. 8.6 Mio
• Topology complicated: high mountainous, valleys, lakes, plains, towns in a small space
• Four languages / regions
• 26 Cantons with 2'172 Communities with a lot of autonomy and decision-making power
• 3 Mobile Network Operator (MNO), > 60 Fixed Net Provider (VSP), > 150 Access Network Provider (ANP)
• 54 PSAPs
− Police, fire brigade and ambulance are cantonal organised and funded
− Swiss poisons information centre - Nationwide organised
− Air Rescue is topology dependent and organised
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
2
Key data on Switzerland
(Confoederatio Helvetica)

3. Requirements
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
3

4. Content and topics concerned:
• Network based caller location
• Handset derived caller location info
• Zero-rating for emergency calls
• Accessibility for people with disabilities
• Access from Online platforms (OTTs e.g. Skype-out, Apps)
• Transnational emergency calls
• Access from private networks
• Emergency calls in different languages
Directive from Dez. 2018 to all EU regulators
affects Switzerland as well
EU-Direktive Regulation changes
14.12.2018 31.12.2020

5. Routing of emergency calls due to net-based localization
Cell based or IP based
Network-based localisation
solutions are highly valued
because they are
absolutely tamper-proof as
well as terminal and
technology-neutral.
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
5
Cable an IP
Access-ID & Adrress-ID
Cell
CGI & TA/RTT

6. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
6
New handling of device-based location and data
PSAP
2021
• eCall (precise additional location, vehicle infos, participents, …)
• AML (precise additional location, localzation infos, speed, direction …)
Later
• Accessibility for people with disabilities
• OTT
ANP, VSP, ECSP, PSP
Access
Cable

7. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
7
Everthing according "new" NG112 standards but no regulation of AccessNetProviders
(ANP) > Centralised LIS is required
LIS-Proxy
LIS
Interconn
ection
Interface for
VSP & PSAP
Call
Data
Architecture ESTI ES 203 178

8. New regulation in Switzerland
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
8

9. NG112 (including AML & eCall ) must be implemented at each MNO by
the end of 2021. The regulation of Fixnet will follow in 2022.
Regulation, three levels of legislation
FMG, FDV, TAV
FernMeldeGesetz (FMG)
FernmeldeDienstVerordnung (FDV)
TechnischAdminstrativeVorschrift (TAV)
• Network based caller location > Cell localization
• Handset derived caller location info > AML & eCall
• Free of charge emergency calls > at CH consisting
• Emergency calls in different languages > at CH consisting
• Localisation available in LIS & LIS-Proxy

10. • AccessNetworkProvider (ANP) not regulated > There is no LS in every access net
• Centralised LIS is required > Not according standards
• Only the VoiceServiceProvider (VSP) are regulated
− In regulation version 2021 only the MobileNetworkOperator
− In regulation version 22/23 also FixnetOperator & Private Networks (Swisscom has had a solution since 2012)
• Integration of AML at one VSP (MobileNetworkOperator) > Not according to standard
• Integration of eCall at VSPs (MobileNetworkOperator) > Not according to standard
• Writing information (net-based & device-based location) in the centralised LIS over <ic> > Not according to standard
• The PSAP required one interface, so LIS-Proxy and HELD is needed
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
10
CH regulation vs. ETSI standards
Some topics do not fully meet the standard but are best practice in the current situation

11. Consequences
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
11

12. • Cooperation between PSAP, Regulator and VSP is absolute important for the success. We are together at this congress!
• Migration of all VSPs and all PSAPs to NG112
• Parallel operation; existing localisation database SOSDB and the NG112 components LIS/LIS-Proxy
− The existing protocol (emerep/MLP) can only handle net-based localisation
− With the new NG112 protocol (HELD, PIDF-LO and MSD-XML) we can handle net-based and device-based (eCall, AML) data
• Transport of additional geographic data and informations -> AML, eCall
− Transport of net-based and device-based localizations
− Handling of SIP Header Geolocation and Call-info over Interconnection (BCF)
− Additional data comes offset to the emergency call -> 10 – 60sec.
• A "NG112" approved, hardened LS is required -> e.g. LIS/LIS-Proxy from Intersys AG
− The VSP writes data over <ic> into the LIS. It’s possible but not standardized
− Request's and LocationUpdates have to do with HELD
• Adaptations within the PSAP for NG112 are required. Standards of EENA are missing!
− Information (SIP-INVITE) from telephony (SBC/PBX) must be transferred to the emergency call centres (e.g. AVANTI). Meaning, product
adaption for PBX's and emergency call centres for NG112 are s prerequisite. “Location by Reference” or “Location by Value” have to be
handled.
− Multiple queries over a period of time from PSAP for one emergency call is needed. E.g. all 10 sec.
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
12
Consequences
We are rebuilding Switzerland's entire emergency communications!

13. 13
Reality and needed migration for VSP und PSAP > LIS, LIS-Proxy, SOSDB
The new NG112-VoIP-Interfaces
ETSI ES 203 178 & 203 283
• <ic> -> https, HELD
• <ij> -> SIP
• <im> -> https, HELD
• HELD ist gem. RFC5985
• LIS for netbased und
Devicebased location
• LIS-Proxy
• The existing interfaces OMA
• EMEREP (MLP)
• emelir, emelia
• Existing SOSDB for,
static net based Fixnet location
and dynamic net based location for
mobile and privat networks.
• File for Fixnet
• EMEREP for Mobile
• EMEREP for VoIP
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
SOSDB

14. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
14
Integration of NG112 more in detail
ECSP
CH-LIS
LIS
SOSDB
LIS-
Proxy
AML Service
AML@SMS
Routing
DLWL@SIP
<ic>
PSAP
SBC / PBX
OCS
<ia> <ie>
<ij>
<SMS>
<ic>
<ic>
<im>
VSP
2G
3G
SMSC
eCall
TDM
Fixnet
AML@
SIP <ic>
<SMS>
Mobile
<ic>
VOIP
5G
4G
Interconnection
SIP -IC
UE
SMSC
<if>
<if>
Device send Location by value
<ia/sms/invoice>
Location by reference <ie & ij>
SIP Header Geolocation & Call-info
Write Net based location <ic>
Write Device based location <ic>
Request Net based and device based
location <im>
with Location by reference or SIP-URI
Location by reference
(Geolocation & Call-info)
forward to OCS
Write Device based location <ic>
Location by reference <ie & ij>
SIP Header Geolocation & Call-info

15. Requirements
NG112 interface
definition Switzerland
for <ic> and <im>
15
Basics for NG112 Interfaces <ic> & <im> are DIN-/ETSI-/IETF- standards + requirements
of PSAPs + regulation > CH needed a detailed definition
NG112-CH_XSD-V3.0.zip
NG112_Interfaces_V3.0.pdf
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
https://swisscom.com/emergencylocalization
§
PSAP requirements
NG112 architecture
Swiss regulation
Standards
V3.0 01.06.2021

16. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
16
Supported geographic objects & address elements by the VSP over <ic>
•
Point Circle Ellipse Polygon
NAM Name (First name, last name OR company name)
RD Street name
HNO House number (number and text e.g. 12a)
BLD House name (instead of RD and HNO)
PC Postcode
A3 Village
ADDCODE Address number from public register
Addresselements
geographic objectelements

17. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
17
Structure of HELD for LIS <ic> an LIS-Proxy <im>
Geographical objects and address elements, MSD is capsolatet in HELD
HTTPs Post
HELD Response (im), Request (ic)
PIDF-LO
tuple (Net based location)
device (Device based location)
msd-xer (eCall information)

18. Net- & Device-based
Device-based
Net-based
AML as PIDF-LO
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
18
PSAP-HELD-Request examples > net-based and device-based location/data
eCall as MSD-XER V3
Civic address as PIDF-LO
Cell Location as PIDF-LO Cell Location & AML as PIDF-LO

19. Measures for cooperation
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
19

20. For testing purpose, dedicated test equipment (ref LIS and ref LIS-Proxy) is available. On the LIS there are pre-
defined test cases for PSAP and VSP implemented for validating functionality. The predefined test cases can be
called up via the interfaces <ic> and <im>.
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
20
Test and reference Infrastructure for VSP and PSAP developments
ECSPSwisscom
HELD
<ic>
HELD
<im>
VSP
FDA/ MNO
PSAP
LIS
LIS-Proxy
Notruf
Neu Data
sscom
er Local
eraor
PSAP
HELD
<if>

21. Swisscom (Schweiz) AG
VSP -> ECSP -> PSP
PSAP
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
21
Find solution with PBX (e.g. Unify) & OCS manufacturer (e.g. AVANTI)
New: Information out of telefonie have send to Operation Control System
SIP INVITE
• TO
• FROM
• PAI
• LbyR (Geolocation)
• LbyR (Call-Info)
Location & data
• PIDF-Lo
• MSD
• Link of chat & video server
4
Location request
• SIP-URI out of PAI
• OR LbyR
1
3
IP-PBX
Telefonie
SBC
OCS
AS Application Server
LbyR Location By Reference
PBX Private Branch Exchange
SBC Session Board Controller
OCS Operation Control System
AS
Listener
SOSDB
SIP-INVITE
Data out of SIP-INVITE
over https to OCS
LIS
LIS-Proxy
2
5
6

22. NG112
Timeline for Switzerland
T, regulation,
Start NG112
1.1.21 FDV
T + 6 Mnt
NG112 Interfaces
definition
T + 18 Mnt
First NG112-PSAP
T + 9 Mnt
Test reference
LIS / LIS-Proxy online
T + 12 Mnt
Finish according
regulation
T + 48 Mnt
Last PSAP migrated
EoL old SOSDB
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
22

23. Lessons learnt
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
23

24. • The detailed definition of protocol elements for the country and a review with the involved parts (regulator, VSP and PSAP) is
purposeful. It results in a common understanding of the address elements used in civicaddr or supported geographical objects
• As operator of a central LIS & LS-Proxy, providing reference test cases for VSP (input) and PSAP (output) simplifies the development.
It helps to prevent errors and problems.
• Handling net- and device-based location is complex. To make it simpler for PSAPs, we deliver both together.
• Restrictions in regulation (only VSP are regulated) lead to adaptations of standards
• Centralised LIS
• VSP deliver data in LIS over <ic> interface
• There is no standard defining "inside PSAP”: how the information’ is handled and forwarded from the PBX to the Operations
Control Centre.
• A service is end2end working, when the last PSAP have migrated and implemented the new protocols
• LocationByValue – data of a network, device or App can be very large. If the VSP writes these into the LIS and sends the
LocationByReference, the SIP communication is less loaded and the risk of errors is lower.
• Regulation of mobile device suppliers is a requirement to be able to guarantee the emergency call needs end to end.
Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
24
Lessons learnt
Cooperation between PSAP, regulation and telco is absolute important!

25. Beat
Egger,
07.10.2021,
How
Swizerland
is
implementing
NG112,
C1-Klassifizierung
25
Contact
Swisscom (Schweiz) AG
Beat Egger
Program manager NG112
Alte Tiefenaustrasse 6
3050 Bern
+41 79 407 88 50
Beat.Egger1@swisscom.com
Fertig! Thanks for your attention