Bei grossen Gesetzen wie OR und ZGB kann dies bis zu 30 Sekunden dauern

Ordinance
on the Surveillance of Post and Telecommunications
(SPTO)

English is not an official language of the Swiss Confederation. This translation is provided for information purposes only and has no legal force.

of 15 November 2017 (Status as of 3 December 2019)

The Swiss Federal Council,

based on the Federal Act of 18 March 20161 on the Surveillance of Post and Telecommunications (SPTA),
on Articles 269bis paragraph 2, 269ter paragraph 4 and 445 of the Criminal Procedure Code (CrimPC)2
and on Articles 70bis paragraph 2, 70ter paragraph 4 and 218 of the Military Criminal Procedure Code of 23 March 19793 (MCPC),

ordains:

Chapter 1 General Provisions

Section 1 Introduction

Art. 1 Subject matter and scope of application  

1 This Or­din­ance reg­u­lates the or­gan­isa­tion­al as­pects of and pro­ced­ure for the sur­veil­lance of post and tele­com­mu­nic­a­tions and the pro­vi­sion of in­form­a­tion on postal and tele­com­mu­nic­a­tions ser­vices.

2 It ap­plies to:

a.
or­der­ing au­thor­it­ies and the au­thor­it­ies dir­ect­ing pro­ceed­ings;
b.
ap­prov­al au­thor­it­ies;
c.
fed­er­al, can­ton­al and com­mun­al po­lice forces;
d.
the Fed­er­al In­tel­li­gence Ser­vice (FIS);
e.
the State Sec­ret­ari­at for Eco­nom­ic Af­fairs (SECO);
f.
fed­er­al and can­ton­al au­thor­it­ies com­pet­ent to deal with ad­min­is­trat­ive crim­in­al cases;
g.
the Post and Tele­com­mu­nic­a­tions Sur­veil­lance Ser­vice (PTSS);
h.
postal ser­vice pro­viders (PSPs);
i.
tele­com­mu­nic­a­tions ser­vice pro­viders (TSPs);
j.
the pro­viders of ser­vices based on tele­com­mu­nic­a­tions ser­vices and that en­able one-way or multi-way com­mu­nic­a­tion (pro­viders of de­rived com­mu­nic­a­tion ser­vices);
k.
op­er­at­ors of in­tern­al tele­com­mu­nic­a­tions net­works;
l.
per­sons who al­low third parties to use their ac­cess to a pub­lic tele­com­mu­nic­a­tions net­work;
m.
pro­fes­sion­al re­tail­ers of cards and sim­il­ar means of gain­ing ac­cess to a pub­lic tele­com­mu­nic­a­tions net­work.
Art. 2 Terms and abbreviations  

The terms and ab­bre­vi­ations used in this Or­din­ance are defined in the An­nex.

Section 2 Surveillance Order

Art. 3 Submissions to the PTSS  

1 The or­der­ing au­thor­ity shall use one of the fol­low­ing trans­mis­sion chan­nels to sub­mit sur­veil­lance or­ders and or­ders for their ex­ten­sion or ter­min­a­tion to the PTSS and to no­ti­fy it of the ac­cess rights to be es­tab­lished:

a.
a se­cure means of trans­mis­sion au­thor­ised by the PTSS;
b.
post or fax, if a means of trans­mis­sion in ac­cord­ance with let­ter a is un­avail­able for tech­nic­al reas­ons; or
c.
tele­phone in ur­gent cases, provided the sur­veil­lance or­der is sub­mit­ted in ac­cord­ance with let­ter a or b with­in 24 hours.

2 The PTSS may re­place the means of trans­mis­sion of sub­mis­sions in ac­cord­ance with para­graph 1 let­ter a with on­line-ac­cess to the Ser­vice’s pro­cessing sys­tem.

Art. 4 Conduct of surveillance  

1 The PTSS shall de­term­ine in spe­cif­ic cases the tech­nic­al and or­gan­isa­tion­al meas­ures for con­duct­ing sur­veil­lance, un­less these are dir­ectly spe­cified in the ap­plic­able reg­u­la­tions, in par­tic­u­lar for stand­ard­ised types of in­form­a­tion and sur­veil­lance.

2 If as a res­ult of op­er­a­tion­al prob­lems a per­son or en­tity re­quired to co­oper­ate is un­able to meet its ob­lig­a­tions for the sur­veil­lance of post or tele­com­mu­nic­a­tions, it shall re­port this to the PTSS without delay and there­after sub­mit a writ­ten state­ment of the reas­ons. The PTSS shall in­form the per­son or en­tity re­quired to co­oper­ate without delay if sur­veil­lance can­not be car­ried out be­cause of op­er­a­tion­al prob­lems on its side.

3 Ir­re­spect­ive of where the cause of the er­ror lies, the per­son or en­tity re­quired to co­oper­ate must tem­por­ar­ily store at least the un­delivered sec­ond­ary tele­com­mu­nic­a­tions data from real-time sur­veil­lance and de­liv­er it without delay. If the sec­ond­ary tele­com­mu­nic­a­tions data from real-time sur­veil­lance is no longer avail­able or in­com­plete, the per­son or en­tity re­quired to co­oper­ate must de­liv­er without delay the sec­ond­ary tele­com­mu­nic­a­tions data from ret­ro­act­ive sur­veil­lance in ac­cord­ance with the in­struc­tions of the PTSS.

Art. 5 Protection of official or professional secrecy  

If the PTSS es­tab­lishes that the sur­veil­lance relates to a hold­er of of­fi­cial or pro­fes­sion­al secrets but that the stat­utory meas­ures to pro­tect these secrets have not been taken, it shall in the fol­low­ing situ­ations no­ti­fy the or­der­ing au­thor­ity and the ap­prov­al au­thor­ity without delay and ini­tially shall not al­low the former and the per­sons named in the sur­veil­lance or­der ac­cess to the sur­veil­lance data:

a.
if sur­veil­lance has been ordered by a ci­vil­ian pro­sec­u­tion au­thor­ity: in the case of per­sons from the pro­fes­sion­al groups spe­cified in Art­icles 170–173 Crim­PC un­less meas­ures have been taken in ac­cord­ance with Art­icle 271 Crim­PC;
b.
if sur­veil­lance has been ordered by a mil­it­ary pro­sec­u­tion au­thor­ity: in the case of per­sons from the pro­fes­sion­al groups spe­cified in Art­icle 75 let­ter b MCPC un­less meas­ures in ac­cord­ance with Art­icle 70b MCPC have been taken;
c.
if sur­veil­lance has been ordered by the FIS: in the case of per­sons from the pro­fes­sion­al groups spe­cified in Art­icles 171–173 Crim­PC un­less meas­ures have been taken in ac­cord­ance with Art­icle 58 para­graph 3 of the In­tel­li­gence Ser­vice Act of 25 Septem­ber 20154 in con­junc­tion with Art­icle 23 of the In­tel­li­gence Ser­vice Or­din­ance of 16 Au­gust 20175.
Art. 6 Duty of confidentiality  

The sur­veil­lance or the pro­vi­sion of in­form­a­tion shall be car­ried out so that neither the per­son con­cerned nor un­au­thor­ised third parties are aware of it.

Art. 7 Technical data sorting (filtering)  

The PTSS shall at the re­quest of the or­der­ing au­thor­ity carry out auto­mated fil­ter­ing if it is tech­nic­ally able to so and the cost and work­load in­volved is not dis­pro­por­tion­ate.

Art. 8 Recording telephone calls as evidence  

1 The PTSS shall re­cord as evid­ence the tele­phone calls made in con­nec­tion with its du­ties.

2 Any eval­u­ations of the re­cord­ing shall be car­ried out by Data Pro­tec­tion Com­mis­sion­er or the PTSS Data Pro­tec­tion Com­mis­sion­er.

3 The PTTS shall re­tain the re­cor­ded tele­phone calls for two years and there­after des­troy the re­cord­ings.

Art. 9 Surveillance file  

1 The PTSS shall open a file in the pro­cessing sys­tem for each sur­veil­lance or­der.

2 The file con­tains all the doc­u­ments on the case con­cerned, namely:

a.
the sur­veil­lance or­der and its at­tach­ments;
b.
the sur­veil­lance as­sign­ment or as­sign­ments is­sued to the rel­ev­ant per­son or en­tity re­quired to co­oper­ate;
c.
the con­firm­a­tion or con­firm­a­tions of when the as­sign­ment was is­sued to the per­son or en­tity re­quired to co­oper­ate;
d.
the writ­ten ac­know­ledg­ment from the per­son or en­tity re­quired to co­oper­ate that the sur­veil­lance as­sign­ment or as­sign­ments has or have been car­ried out;
e.
the rul­ings from the ap­prov­al au­thor­ity on the ap­prov­al or non-ap­prov­al of the sur­veil­lance or­der to­geth­er with any ap­peal de­cisions;
f.
any ex­ten­sion or­ders and rul­ings from the ap­prov­al au­thor­ity;
g.
the ter­min­a­tion or­der;
h.
the cor­res­pond­ence re­lat­ing to the meas­ure;
i.
the pro­tec­tion meas­ures spe­cially ordered;
j.
the ac­count­ing re­cords.

3 The sur­veil­lance data shall be stored in ac­cord­ance with Art­icle 11 SPTA and des­troyed in ac­cord­ance with Art­icle 14 of the Or­din­ance of 15 Novem­ber 20176 on the Pro­cessing Sys­tem for the Sur­veil­lance of Post and Tele­com­mu­nic­a­tions (PSO-PTSS).

Section 3 Working Hours and On-Call Arrangements

Art. 10 Normal working hours and public holidays  

1 Nor­mal work­ing hours for the PTSS and the per­sons or en­tit­ies re­quired to co­oper­ate are Monday to Fri­day con­tinu­ously from 8am to 5pm.

2 Nor­mal work­ing hours do not ap­ply on pub­lic hol­i­days. These are 1 and 2 Janu­ary, Good Fri­day, East­er Monday, As­cen­sion Day, Whit Monday, 1 Au­gust, 24 Decem­ber from noon, 25 and 26 Decem­ber and New Year’s Eve (31 Decem­ber) from noon.

Art. 11 Services outside the normal working hours  

1 Out­side nor­mal work­ing hours and on pub­lic hol­i­days, the PTSS shall provide the fol­low­ing on-call ser­vices:

a.
the for­ward­ing of re­quests for in­form­a­tion spe­cified in Art­icles 35–43;
b.
is­su­ing as­sign­ments for the ac­tiv­a­tion of real-time sur­veil­lance in ac­cord­ance with Art­icles 54–59;
c.
is­su­ing as­sign­ments for the con­duct of ret­ro­spect­ive ur­gent sur­veil­lance activ­it­ies in ac­cord­ance with Art­icles 60–63, 65 and 66;
d.
is­su­ing as­sign­ments for miss­ing and wanted per­son searches in ac­cord­ance with Art­icles 67 and 68, with the ex­cep­tion of the net­work cov­er­age ana­lys­is in pre­par­a­tion for an an­tenna search in ac­cord­ance with Art­icle 64;
e.
the rec­ti­fic­a­tion of faults.

2 The TSPs, with the ex­cep­tion of those with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51, and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 must be able to sup­port the PTSS so that it may provide the ser­vices in ac­cord­ance with para­graph 1 at any time. The PTSS must be able to con­tact them at any time.

3 The or­der­ing of spe­cial sur­veil­lance activ­it­ies and re­quests for spe­cial in­form­a­tion (Art. 25) shall not be ac­cep­ted or pro­cessed out­side nor­mal work­ing hours.

Section 4 Statistics

Art. 12 Statistics on surveillance measures and information  

1 The PTSS shall pub­lish stat­ist­ics every year about the sur­veil­lance activ­it­ies ordered in the pre­vi­ous cal­en­dar year and the in­form­a­tion provided. These shall in­dic­ate in par­tic­u­lar the num­ber:

a.
of sur­veil­lance meas­ures in real time;
b.
of ret­ro­act­ive sur­veil­lance meas­ures;
c.
of in­stances in which in­form­a­tion was provided;
d.
of miss­ing per­son searches;
e.
of wanted per­son searches.

2 The stat­ist­ics in ac­cord­ance with para­graph 1 shall in­dic­ate:

a.
the type of of­fence;
b.
the can­ton of the or­der­ing au­thor­ity, the or­der­ing fed­er­al au­thor­ity or, in the case of miss­ing per­son searches, also an au­thor­ity from the Prin­cip­al­ity of Liecht­en­stein, and in the case of in­form­a­tion, the com­pet­ent can­ton­al or fed­er­al au­thor­ity (Art. 1 para. 2 lets c–f);
c.
the type of in­form­a­tion, sur­veil­lance, miss­ing per­son search or wanted per­son search;
d.
the dur­a­tion of sur­veil­lance, if ap­plic­able;
e.
the fees;
f.
the com­pens­a­tion.
Art. 13 S tatistics on surveillance measures with special technical devices and special IT programs  

1 Pub­lic pro­sec­utor’s of­fices and mil­it­ary ex­amin­ing ma­gis­trates shall keep an­nu­al stat­ist­ics on the spe­cial tech­nic­al devices and spe­cial in­form­a­tion tech­no­logy pro­grams used in the pre­vi­ous cal­en­dar year for sur­veil­lance activ­it­ies (Art. 269bis para. 2 and 269ter para. 4 Crim­PC and Art. 70bis para. 2 and 70ter para. 4 MCPC re­spect­ively). The stat­ist­ics shall in­dic­ate the type of of­fence.

2 Pub­lic pro­sec­utor’s of­fices and the Of­fice of the Mil­it­ary At­tor­ney Gen­er­al at the DDPS shall sub­mit the stat­ist­ics to the PTSS in the first quarter of the fol­low­ing year. The stat­ist­ics shall in­dic­ate only as­sign­ments con­cluded in the year con­cerned.

3 The PTSS shall pub­lish con­sol­id­ated stat­ist­ics every year. These do not con­tain any de­tails of the can­ton of the or­der­ing au­thor­ity or the fed­er­al or­der­ing au­thor­ity.

Chapter 2 Postal Deliveries

Art. 14 Obligations of PSPs  

1 Each PSP must be able to provide the in­form­a­tion spe­cified in Art­icle 20 SPTA and con­duct the types of sur­veil­lance spe­cified in Art­icle 16 in­so­far as the in­form­a­tion and sur­veil­lance activ­it­ies re­late to ser­vices that the PSP provides.

2 Each PSP must en­sure that it can ac­cept and ex­ecute the re­quests for in­form­a­tion and sur­veil­lance or­ders dur­ing nor­mal work­ing hours.

Art. 15 Order to conduct surveillance of postal deliveries  

The sur­veil­lance or­der sub­mit­ted to the PTSS shall con­tain the fol­low­ing in­form­a­tion:

a.
con­tact de­tails for the or­der­ing au­thor­ity;
b.
con­tact de­tails for the per­sons au­thor­ised to be the re­cip­i­ents of the sur­veil­lance data;
c.
if known, the sur­name, first name, date of birth, ad­dress and oc­cu­pa­tion of the per­son to be placed un­der sur­veil­lance;
d.
ref­er­ence num­bers and case names for the sur­veil­lance activ­it­ies;
e.
the reas­on for sur­veil­lance, in par­tic­u­lar the crim­in­al of­fence to be in­vest­ig­ated by means of sur­veil­lance;
f.
the name of the PSP;
g.
the types of sur­veil­lance ordered;
h.
if ne­ces­sary, ad­di­tion­al in­form­a­tion on a per­son’s postal traffic;
i.
the start and dur­a­tion of sur­veil­lance;
j.
in the case of per­sons bound by pro­fes­sion­al secrecy in ac­cord­ance with Art­icle 271 Crim­PC or Art­icle 70b MCPC: a note on this as­pect;
k.
if need be, the meas­ures to pro­tect per­sons hold­ing pro­fes­sion­al secrets and fur­ther pro­tec­tion meas­ures that the au­thor­it­ies, the PSP and the PTSS must take.
Art. 16 Types of surveillance  

The fol­low­ing types of sur­veil­lance may be ordered:

a.
the in­ter­cep­tion of postal de­liv­er­ies (real time-sur­veil­lance; Sur­veil­lance Type PO_1_RT_IN­TER­CEP­TION);
b.
the pro­vi­sion of the fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data (real-time sur­veil­lance; Sur­veil­lance Type PO_2_RT_DE­LIV­ERY), in­so­far as they are avail­able:
1.
the ad­dress­ee,
2.
the sender,
3.
the type,
4.
the mail­ing loc­a­tion,
5.
the de­liv­ery status,
6.
the re­cip­i­ent’s sig­na­ture;
c.
the pro­vi­sion of the fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data (ret­ro­act­ive sur­veil­lance; Sur­veil­lance Type PO_3_HD):
1.
for postal de­liv­er­ies with proof of de­liv­ery: the re­cip­i­ent and the sender as well as the type, the mail­ing loc­a­tion and the de­liv­ery status of the postal de­liv­ery, if avail­able,
2.
if the PSP has re­cor­ded any ad­di­tion­al sec­ond­ary tele­com­mu­nic­a­tions data: all avail­able data.

Chapter 3 Telecommunications

Section 1 General Provisions on Information and Surveillance Activities

Art. 17 Requests for information  

1 Re­quests for in­form­a­tion from the au­thor­it­ies spe­cified in Art­icle 15 SPTA to TSPs, pro­viders of de­rived com­mu­nic­a­tion ser­vices and op­er­at­ors of in­tern­al tele­com­mu­nic­a­tions net­works as well as the in­form­a­tion re­turned to the au­thor­it­ies are trans­mit­ted in the on­line re­quest pro­ced­ure or via the in­ter­faces us­ing the pro­cessing sys­tem spe­cified in the PSO-PTSS7.

2 If the on­line re­quest pro­ced­ure us­ing the pro­cessing sys­tem is un­avail­able for tech­nic­al reas­ons, re­quests for in­form­a­tion and the in­form­a­tion re­turned to the au­thor­it­ies may be sub­mit­ted to the PTSS by post or fax.

3 In ur­gent cases, the au­thor­it­ies may sub­mit re­quests for in­form­a­tion by tele­phone to the PTSS, and sub­mit the re­quest for in­form­a­tion spe­cified in para­graph 1 or 2 sub­sequently.

4 The re­quest for in­form­a­tion must in­dic­ate, in ad­di­tion to the de­tails re­quired for the type of in­form­a­tion con­cerned, the max­im­um num­ber of data re­cords to be sup­plied and, if avail­able, the ref­er­ence num­bers and case names.

Art. 18 Obligations for the supply of information  

1 TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion in ac­cord­ance with Art­icle 22 must be able to provide the in­form­a­tion spe­cified in Art­icles 35–37 and 40–48 as well as in Art­icle 27 in con­junc­tion with Art­icles 35, 40, 42 and 43 that relates to ser­vices that they provide. They may en­list the sup­port of third parties to do so.

2 They shall provide the in­form­a­tion spe­cified in Art­icles 35–37 and 40–42 and in Art­icle 27 in con­junc­tion with Art­icles 35, 40 and 42 in an auto­mated pro­cess via the query in­ter­face of the PTSS pro­cessing sys­tem. They may also provide the in­form­a­tion spe­cified in Art­icles 43–48 and in Art­icle 27 in con­junc­tion with Art­icle 43 manu­ally.

3 TSPs with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51 may also provide in­form­a­tion of all types out­side of the pro­cessing sys­tem in writ­ing.

4 TSPs, with the ex­cep­tion of those with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51, and the pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 must be able to provide the in­form­a­tion spe­cified in Art­icles 38 and 39 that relates to ser­vices that they provide via the query in­ter­face of the PTSS pro­cessing sys­tem. They may en­list the sup­port of third parties to do so.

5 Pro­viders of de­rived com­mu­nic­a­tion ser­vices without more ex­tens­ive du­ties to provide in­form­a­tion and con­duct sur­veil­lance and op­er­at­ors of in­tern­al tele­com­mu­nic­a­tions net­works are not re­quired to provide in­form­a­tion of the types spe­cified in Art­icles 35–48 and in Art­icle 27 in con­junc­tion with Art­icles 35, 40, 42 and 43. They shall sup­ply the in­form­a­tion avail­able to them via the pro­cessing sys­tem or by a dif­fer­ent meth­od in writ­ten form.

6 If the num­ber the data re­cords found ex­ceeds the max­im­um value spe­cified in the re­quest, the pro­vider shall only dis­close their num­ber.

Art. 19 Identification of the participants  

1 TSPs, pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion in ac­cord­ance with Art­icle 22, pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 and re­tail­ers in ac­cord­ance with Art­icle 2 let­ter f SPTA must en­sure that sub­scribers are iden­ti­fied by suit­able means.

2 In the case of pro­fes­sion­ally op­er­ated pub­lic WLAN ac­cess points, TSPs must en­sure that all end users are iden­ti­fied by suit­able means.

Art. 20 Recording personal details in the case of mobile services  

1 In the case of mo­bile ser­vices, TSPs and re­tail­ers in ac­cord­ance with Art­icle 2 let­ter f SPTA must, on sup­ply­ing the means of ac­cess or on the ini­tial ac­tiv­a­tion of the ser­vice, veri­fy the iden­tity of the sub­scriber by means of a pass­port, an iden­tity card or a for­eign na­tion­al iden­tity card in ac­cord­ance with Art­icle 71 and 71a of the Or­din­ance of 24 Oc­to­ber 20078 on Ad­mis­sion, Peri­od of Stay and Em­ploy­ment. They must re­tain an eas­ily legible copy of the iden­tity doc­u­ment.

2 In the case of the nat­ur­al per­sons, the fol­low­ing de­tails must be re­cor­ded:

a.
sur­names and fore­names;
b.
date of birth;
c.
type of iden­tity doc­u­ment, iden­tity doc­u­ment num­ber and the is­su­ing coun­try or is­su­ing or­gan­isa­tion;
d.
ad­dress;
e.
if known, oc­cu­pa­tion;
f.
na­tion­al­ity.

3 In the case of leg­al en­tit­ies, the fol­low­ing de­tails must be re­cor­ded:

a.
name, re­gistered of­fice and con­tact de­tails for the leg­al en­tity;
b.
busi­ness iden­ti­fic­a­tion num­ber (UID) in ac­cord­ance with the Fed­er­al Act of 18 June 20109 on the Busi­ness Iden­ti­fic­a­tion Num­ber;
c.
if avail­able, the names and fore­names of the per­sons who will use the pro­vider’s ser­vices.

4 In the case of cus­tom­er re­la­tion­ships that are not based on a sub­scrip­tion con­tract, the fol­low­ing de­tails must also be re­cor­ded:

a.
the time at which the means of ac­cess was sup­plied;
b.
the point of sup­ply (name and com­plete ad­dress);
c.
the name of the per­son sup­ply­ing the means of ac­cess.
Art. 21 Retention periods  

1 TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion and con­duct sur­veil­lance (Art. 22 and 52) must re­tain and be able to sup­ply the in­form­a­tion about the tele­com­mu­nic­a­tions ser­vices and the in­form­a­tion re­cor­ded for the pur­pose of iden­ti­fic­a­tion for the dur­a­tion of the cus­tom­er re­la­tion­ship and for 6 months after its ter­min­a­tion. TSPs must re­tain and be able to sup­ply iden­ti­fic­a­tion data in ac­cord­ance with Art­icle 19 para­graph 2 for as long as the right to ac­cess the pub­lic WLAN ac­cess point ap­plies and for 6 months after its ex­piry.

2 TSPs, with the ex­cep­tion of those with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51, and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 must re­tain and be able to sup­ply the fol­low­ing data for the pur­pose of iden­ti­fic­a­tion for 6 months:

a.
the sec­ond­ary tele­com­mu­nic­a­tions data re­lat­ing to the device iden­ti­fi­ers ac­tu­ally used, in or­der to be able to provide the in­form­a­tion spe­cified in Art­icle 36 para­graph 1 let­ter d and Art­icle 41 para­graph 1 let­ter d; and
b.
the sec­ond­ary tele­com­mu­nic­a­tions data re­lat­ing to the as­sign­ment and trans­la­tion of IP ad­dresses and port num­bers, in or­der to be able to provide the in­form­a­tion spe­cified in Art­icles 37, 38 and 39.

3 The sec­ond­ary tele­com­mu­nic­a­tions data un­der para­graph 2 must be des­troyed as soon as the re­ten­tion peri­od has ex­pired, un­less oth­er le­gis­la­tion re­quires or per­mits such data to be re­tained for longer.

Art. 22 Providers of derived communication services with more extensive duties to provide information  

1 The PTSS shall de­clare a pro­vider of de­rived com­mu­nic­a­tion ser­vices to be a pro­vider with more ex­tens­ive du­ties to provide in­form­a­tion (Art. 22 para. 4 SPTA), if it has met one of the fol­low­ing cri­ter­ia:

a.
100 re­quests for in­form­a­tion in the past 12 months (ef­fect­ive date: 30 June);
b.
an­nu­al turnover in Switzer­land of CHF 100 mil­lion in two suc­cess­ive fin­an­cial years, provided a large part of its busi­ness op­er­a­tions provides de­rived com­mu­nic­a­tion ser­vices and 5,000 sub­scribers use the pro­vider’s ser­vices.

2 If a pro­vider con­trols one or more un­der­tak­ings re­quired to file fin­an­cial re­ports as defined in Art­icle 963 para­graph 2 of the Code of Ob­lig­a­tions10, the pro­vider and the con­trolled un­der­tak­ings must be re­garded as a single unit when cal­cu­lat­ing the val­ues in ac­cord­ance with para­graph 1.

3 Pro­viders that ex­ceed or fail to meet the cri­ter­ia in para­graph 1 let­ter b must no­ti­fy the PTSS of this in writ­ing with­in three months of the end of their fin­an­cial year and sub­mit re­lated sup­port­ing doc­u­ments.

4 Pro­viders must on re­quest provide the PTSS with the in­form­a­tion and sup­port­ing doc­u­ments for as­sess­ing the cri­ter­ia un­der para­graph 1 let­ter b. The PTSS may rely on data ob­tained in im­ple­ment­ing the le­gis­la­tion re­lat­ing to the sur­veil­lance of post and tele­com­mu­nic­a­tions or by oth­er au­thor­it­ies in im­ple­ment­ing fed­er­al law.

5 A pro­vider that is de­clared to have more ex­tens­ive du­ties to provide in­form­a­tion must en­sure that it can store the data re­quired for provid­ing in­form­a­tion with­in 2 months and provide the in­form­a­tion with­in 12 months of the de­clar­a­tion.

Art. 23 Assistance in providing information and conducting surveillance activities  

If third parties are en­gaged by the pro­vider to as­sist in provid­ing in­form­a­tion or con­duct­ing sur­veil­lance activ­it­ies, they shall be sub­ject to the same re­quire­ments as the pro­vider. The pro­vider re­mains re­spons­ible for provid­ing in­form­a­tion and con­duct­ing the sur­veil­lance activ­it­ies ordered to the ex­tent spe­cified; in par­tic­u­lar it shall take the meas­ures re­quired to en­sure that suit­able con­tact per­sons for provid­ing in­form­a­tion and con­duct­ing the sur­veil­lance activ­it­ies ordered are avail­able to the PTSS at all times. Both the pro­vider as­signed the task by the PTSS and its as­sist­ants serve as con­tact points for the PTSS.

Art. 24 Standardisation of types of information and surveillance  

1 The Fed­er­al Justice and Po­lice De­part­ment (FD­JP) shall stand­ard­ise the types of in­form­a­tion and sur­veil­lance that are defined in this Or­din­ance.

2 If, based on the in­ter­na­tion­al stand­ards and the en­quir­ies made of the per­sons or en­tit­ies re­quired to co­oper­ate, it proves im­possible or un­reas­on­able to stand­ard­ise a type of in­form­a­tion or sur­veil­lance, the FD­JP shall dis­pense with do­ing so.

Art. 25 Special information and surveillance activities  

In the case of in­form­a­tion and sur­veil­lance activ­it­ies that do not cor­res­pond to a stand­ard­ised type of in­form­a­tion or sur­veil­lance, TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices shall provide the PTSS with all already avail­able in­ter­faces and con­nec­tions to the PTSS pro­cessing sys­tem. The con­tent and the sec­ond­ary tele­com­mu­nic­a­tions data of the tele­com­mu­nic­a­tion of the per­son un­der sur­veil­lance must be sup­plied as far as pos­sible in ac­cord­ance with Art­icle 26 para­graph 1 SPTA. The PTSS shall de­term­ine the mod­al­it­ies in spe­cif­ic cases.

Art. 26 Types of information in general  

1 The pro­viders con­cerned shall provide the fol­low­ing types of in­form­a­tion on tele­com­mu­nic­a­tions ser­vices or de­rived com­mu­nic­a­tions ser­vices:

a.
in­form­a­tion on sub­scribers (Art. 35, 40, 42 and 43 to­geth­er with Art. 27 in con­junc­tion with Art. 35, 40, 42 and 43);
b.
in­form­a­tion on ser­vices (Art. 36–39 and 41);
c.
oth­er in­form­a­tion:
1.
in­form­a­tion on the meth­od of pay­ment (Art. 44),
2.
re­quests for cop­ies of iden­tity doc­u­ments (Art. 45),
3.
re­quests for cop­ies of in­voices (Art. 46),
4.
re­quests for cop­ies of con­tracts (Art. 47),
5.
in­form­a­tion on tech­nic­al data re­lat­ing to tele­com­mu­nic­a­tions sys­tems and net­work ele­ments (Art. 48).

2 The au­thor­it­ies may only re­quest the in­form­a­tion that pro­viders are re­quired to provide in ac­cord­ance with the pro­ced­ures defined in this Or­din­ance.

Art. 27 Obtaining information with a flexible name search  

1 Re­quests for types of in­form­a­tion spe­cified in Art­icles 35, 40, 42 and 43 may be com­plied with by car­ry­ing out a search that tol­er­ates er­rors and finds phon­et­ic matches (flex­ible name search). In this case, the suf­fix “FLEX” shall be ad­ded to the ab­bre­vi­ation for the rel­ev­ant in­form­a­tion re­quest type: IR_5_N­A_FLEX, IR_11_TEL_FLEX, IR_14_e­mail _FLEX and IR_16_­COM_FLEX.

2 The re­quest for in­form­a­tion shall in each case con­tain the first and at least one ad­di­tion­al query cri­terion for the un­der­ly­ing in­form­a­tion re­quest type.

Art. 28 Types of surveillance  

1 The pro­viders con­cerned must con­duct the fol­low­ing types of real-time sur­veil­lance for tele­com­mu­nic­a­tions ser­vices and de­rived com­mu­nic­a­tions ser­vices:

a.
real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices (Art. 54);
b.
real-time sur­veil­lance of con­tent and sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices (Art. 55);
c.
real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data in the case of ap­plic­a­tions (Art. 56 and 58);
d.
real-time sur­veil­lance of con­tent and sec­ond­ary tele­com­mu­nic­a­tions data in the case of ap­plic­a­tions (Art. 57 and 59).

2 The pro­viders con­cerned must con­duct the fol­low­ing types of ret­ro­act­ive sur­veil­lance activ­it­ies for tele­com­mu­nic­a­tions ser­vices and de­rived com­mu­nic­a­tions ser­vices:

a.
ret­ro­act­ive sur­veil­lance in the case of net­work ac­cess ser­vices (Art. 60);
b.
ret­ro­act­ive sur­veil­lance in the case of ap­plic­a­tions (Art. 61 and 62);
c.
loc­at­ing the last act­ive po­s­i­tion of the mo­bile ter­min­al device (Art. 63);
d.
an an­tenna search (Art. 66) and the cor­res­pond­ing pre­par­a­tions (Art. 64 or 65).

3 The pro­viders con­cerned must con­duct the fol­low­ing types of miss­ing per­son searches (Art. 67):

a.
loc­at­ing the last act­ive po­s­i­tion of the mo­bile ter­min­al device (Art. 67 let. a);
b.
real-time sur­veil­lance of con­tent and sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices and tele­phony and mul­ti­me­dia ser­vices (Art. 67 let. b);
c.
real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices and tele­phony and mul­ti­me­dia ser­vices (Art. 67 let. c);
d.
ret­ro­act­ive sur­veil­lance in the case of net­work ac­cess ser­vices and tele­phony and mul­ti­me­dia ser­vices (Art. 67 let. d).

4 The pro­viders con­cerned must con­duct the fol­low­ing types of searches (Art. 68):

a.
loc­at­ing the last act­ive po­s­i­tion of the mo­bile ter­min­al device (Art. 68 let. a);
b.
real-time sur­veil­lance of con­tent and sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices or ap­plic­a­tions (Art. 68 let. b);
c.
real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data in the case of net­work ac­cess ser­vices or ap­plic­a­tions (Art. 68 let. c);
d.
ret­ro­act­ive sur­veil­lance in the case of net­work ac­cess ser­vices or ap­plic­a­tions (Art. 68 let. d).

Section 2 Quality Assurance

Art. 29 Quality of the data transmitted  

1 The qual­ity of the data trans­mit­ted is ac­cept­able if:

a.
the data de­liv­ery meets the re­quire­ments spe­cified by the FD­JP;
b.
the data is de­livered without loss of data and without in­ter­rup­tions; and
c.
the trans­mit­ted sur­veil­lance data or in­form­a­tion data cor­res­pond to that spe­cified in the sur­veil­lance or­der or re­quest for in­form­a­tion.

2 The per­sons or en­tit­ies re­quired to co­oper­ate are re­spons­ible for the qual­ity of the trans­mit­ted in­form­a­tion and sur­veil­lance data up to the point of de­liv­ery.

3 If a pro­vider or the PTSS iden­ti­fies any de­fects in the qual­ity of the data trans­mit­ted, they shall in­form each oth­er without delay. The PTSS shall de­term­ine the ser­i­ous­ness of the de­fects and the pro­ced­ure for their rec­ti­fic­a­tion after con­sult­ing the pro­vider. The pro­vider and the PTSS shall in­form each oth­er reg­u­larly and promptly about the status of the rec­ti­fic­a­tion of de­fects.

Art. 30 Test surveillance  

1 The PTSS may con­duct test sur­veil­lance; in do­ing so, it may work with the pro­sec­u­tion au­thor­it­ies and the FIS. The tests serve the fol­low­ing pur­poses in par­tic­u­lar:

a.
as­sur­ing the qual­ity of the data di­ver­ted to the PTSS and the pro­sec­u­tion au­thor­it­ies by the per­sons or en­tit­ies re­quired to co­oper­ate;
b.
veri­fy­ing the abil­ity of the per­sons or en­tit­ies re­quired to co­oper­ate to provide in­form­a­tion and con­duct sur­veil­lance;
c.
test­ing the PTSS pro­cessing sys­tem;
d.
train­ing pur­poses;
e.
gen­er­at­ing ref­er­ence data.

2 The PTSS may in­struct the per­sons or en­tit­ies re­quired to co­oper­ate to par­ti­cip­ate in gen­er­at­ing the test data. The PTSS shall draw up a test plan after con­sult­ing the per­sons or en­tit­ies re­quired to co­oper­ate.

3 The per­sons or en­tit­ies re­quired to co­oper­ate shall provide the PTSS with the re­quired test tar­gets and the re­quired tele­com­mu­nic­a­tions ser­vices or de­rived com­mu­nic­a­tions ser­vices at its re­quest free of charge and per­man­ently.

4 The pro­sec­u­tion au­thor­it­ies and the FIS may also con­duct cir­cuit tri­als at their own ex­pense for the pur­pose of qual­ity as­sur­ance and the train­ing. To this end, they shall sub­mit or­ders to the PTSS and pay fees.

Section 3 Ensuring Ability to provide Information and conduct Surveillance

Art. 31 Verifying ability to provide information and conduct surveillance  

1 TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive in­form­a­tion (Art. 22) or sur­veil­lance du­ties (Art. 52) shall in ac­cord­ance with Art­icle 33 para­graph 1 SPTA provide proof of their abil­ity to provide in­form­a­tion and con­duct sur­veil­lance.

2 Proof is provided if:

a.
the tests that must be con­duc­ted in ac­cord­ance with PTSS re­quire­ments have been suc­cess­fully com­pleted; and
b.
the pro­vider con­firms in a ques­tion­naire drawn up by the PTSS it meets the re­quire­ments in re­la­tion to stand­ard­ised in­form­a­tion and sur­veil­lance activ­it­ies that can­not be proven by test­ing.

3 The PTSS shall en­sure that it con­ducts the veri­fic­a­tion pro­cess promptly and does not cause any delay in mar­ket in­tro­duc­tion. To do so, it shall carry out the fol­low­ing tasks:

a.
It shall check the res­ults of the tests in ac­cord­ance with para­graph 2 let­ter a.
b.
It shall eval­u­ate the ques­tion­naire in ac­cord­ance with para­graph 2 let­ter b.
c.
It shall keep a re­cord of the test pro­ced­ures.
d.
It shall is­sue the pro­viders with con­firm­a­tion in ac­cord­ance with Art­icle 33 para­graph 6 SPTA.
e.
It shall re­tain the re­cords for as long as the con­firm­a­tion re­mains val­id and for ten years after its ex­piry.

4 The PTSS shall state in the con­firm­a­tion that the pro­vider has proven its abil­ity to provide cer­tain types of in­form­a­tion and con­duct cer­tain types of sur­veil­lance activ­it­ies.

Art. 32 Term of validity of the confirmation  

1 The con­firm­a­tion of abil­ity to provide in­form­a­tion and con­duct sur­veil­lance is val­id for three years.

2 On ex­piry of the term of valid­ity, the PTSS may ex­tend the con­firm­a­tion by a fur­ther three years if the per­son or en­tity re­quired to co­oper­ate cer­ti­fies that since con­firm­a­tion was gran­ted no modi­fic­a­tions have been car­ried out that in­flu­ence data de­liv­ery or the abil­ity to provide in­form­a­tion or con­duct sur­veil­lance.

3 If a pro­vider can no longer provide in­form­a­tion or con­duct sur­veil­lance, it shall no­ti­fy the PTSS im­me­di­ately.

Art. 33 Acceptance procedure  

The FD­JP shall reg­u­late the pro­ced­ure for veri­fy­ing abil­ity to provide in­form­a­tion and con­duct sur­veil­lance.

Art. 34 Declaration of invalidity of the confirmation of ability to provide information and conduct surveillance  

The PTSS shall im­me­di­ately de­clare a con­firm­a­tion of abil­ity to provide in­form­a­tion and con­duct sur­veil­lance that has already been is­sued to be in­val­id for the rel­ev­ant types of in­form­a­tion or sur­veil­lance if:

a.
the pro­vider gives no­tice that it can no longer provide in­form­a­tion or con­duct sur­veil­lance;
b.
the pro­vider is un­able on two or more oc­ca­sions to de­liv­er data, provide in­form­a­tion or con­duct sur­veil­lance;
c.
the in­form­a­tion on the pro­vider that un­der­lies the con­firm­a­tion is un­true.

Section 4 Types of Information Requests for Network Access Services

Art. 35 Information Request Type IR_4_NA: Information on subscribers to network access services  

1 In­form­a­tion Re­quest Type IR_4_NA com­prises the fol­low­ing in­form­a­tion about sub­scribers to net­work ac­cess ser­vices:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
in the case of mo­bile ser­vices, the de­tails of the nat­ur­al per­son or leg­al en­tity in ac­cord­ance with Art­icle 20 and, if known, fur­ther con­tact de­tails and the sex of the nat­ur­al per­son;
c.
in the case of the oth­er net­work ac­cess ser­vices, the iden­ti­fic­a­tion in­form­a­tion spe­cified in Art­icle 19 and, if known, the de­tails of the nat­ur­al or leg­al en­tity, fur­ther con­tact de­tails and the sex of the nat­ur­al per­son;
d.
the fol­low­ing in­form­a­tion about each net­work ac­cess ser­vice that the sub­scriber ob­tains from the pro­vider:
1.
the unique iden­ti­fi­er for the pro­vider (e.g. TSP num­ber),
2.
the unique ser­vice iden­ti­fi­er (e.g. user name, MS­ISDN, DSL iden­ti­fi­er),
3.
the peri­od over which the ser­vice was used (start, first ac­tiv­a­tion and, if ap­plic­able, ter­min­a­tion),
4.
if ap­plic­able, fur­ther in­form­a­tion about ad­di­tion­al op­tions or re­stric­tions on the net­work ac­cess ser­vice,
5.
if ap­plic­able, the in­stall­a­tion ad­dresses of the fixed loc­a­tion ac­cess to the net­work and their peri­od of valid­ity in each case,
6.
the statuses of the ser­vice as des­ig­nated in­tern­ally by the pro­vider (e.g. act­ive, sus­pen­ded, blocked) and their peri­od of valid­ity in each case,
7.
if ap­plic­able, all stat­ic IP ad­dresses, IP pre­fixes, IP ad­dress ranges and net masks or pre­fix lengths as­signed to net­work ac­cess ser­vice con­cerned and their peri­od of valid­ity in each case,
8.
in the case of cus­tom­er re­la­tion­ships that are not based on a sub­scrip­tion con­tract, the time and the point of sup­ply (name and com­plete ad­dress) for the means of ac­cess and the name of the per­son who made the sup­ply,
9.
if ap­plic­able, the SIM num­ber (IC­CID) at the time of its sup­ply,
10.
if ap­plic­able, the IM­SI,
11.
the type of the ser­vice (e.g. pre­paid, sub­scrip­tion),
12.
if ap­plic­able, the al­tern­at­ive sub­scriber iden­ti­fi­er for the net­work ac­cess ser­vice.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia. If let­ters a–e are used, a second query cri­terion must be ad­ded. If search­ing for char­ac­ter strings (lets a, c, d and f), the pro­vider must search only for the spe­cified spelling of the term in ac­cord­ance with the ap­plic­able FD­JP reg­u­la­tions:

a.
sur­name(s), first name(s);
b.
date of birth;
c.
coun­try and post­code or coun­try and place;
d.
street and, if pos­sible, house num­ber;
e.
iden­tity doc­u­ment num­ber and, op­tion­ally, the type of iden­tity doc­u­ment;
f.
name and, op­tion­ally, the re­gistered of­fice of the leg­al en­tity;
g.
busi­ness iden­ti­fic­a­tion num­ber (UID);
h.
sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
i.
ser­vice iden­ti­fi­er oth­er than IP ad­dresses (e.g. user name, MS­ISDN, DSL iden­ti­fi­er);
j.
IM­SI;
k.
SIM num­ber (IC­CID).
Art. 36 Information Request Type IR_6_NA: Information on network access services  

1 In­form­a­tion Re­quest Type IR_6_NA com­prises the fol­low­ing in­form­a­tion about net­work ac­cess ser­vices. For in­form­a­tion spe­cified in let­ters b, c and e, de­tails of the com­mon peri­od of valid­ity shall be provided:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the unique ser­vice iden­ti­fi­er (e.g. user name, DSL iden­ti­fi­er);
c.
if ap­plic­able, the IM­SI and MS­ISDN;
d.
the list of unique device iden­ti­fi­ers in ac­cord­ance with in­ter­na­tion­al stand­ards (e.g. IMEI, MAC ad­dress) of the devices used in con­nec­tion with this ser­vice from the pro­vider as well as, if avail­able, their name in text form;
e.
if ap­plic­able, the SIM num­bers (IC­CID);
f.
if ap­plic­able, the PUK and PUK2 codes.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia:

a.
the ser­vice iden­ti­fi­er, oth­er than IP ad­dresses (e.g. user name, MS­ISDN, DSL iden­ti­fi­er);
b.
the IM­SI;
c.
the unique device iden­ti­fi­er in ac­cord­ance with in­ter­na­tion­al stand­ards (e.g. IMEI, MAC ad­dress);
d.
the in­stall­a­tion ad­dress of the fixed loc­a­tion ac­cess to the net­work.
Art. 37 Information Request Type IR_7_IP: Identification of the users in the case of uniquely assigned IP addresses  

1 In­form­a­tion Re­quest Type IR_7_IP com­prises the fol­low­ing in­form­a­tion about the iden­ti­fied sub­scriber if this per­son was as­signed a unique IP ad­dress at the time in ques­tion:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. user name);
b.
the unique ser­vice iden­ti­fi­er (e.g. user name, MS­ISDN, DSL iden­ti­fi­er) of the net­work ac­cess ser­vice;
c.
the unique iden­ti­fi­er that des­ig­nates the pro­vider of the net­work ac­cess ser­vice (e.g. TSP num­ber).

2 The re­quest for in­form­a­tion shall con­tain the fol­low­ing in­form­a­tion:

a.
the IP ad­dress;
b.
the date and time.
Art. 38 Information Request Type IR_8_IP (NAT): Identification of the users in the case of IP addresses that are not uniquely assigned (NAT)  

1 In­form­a­tion Re­quest Type IR_8_IP (NAT) com­prises the fol­low­ing in­form­a­tion about the iden­ti­fied sub­scriber if this per­son was not as­signed a unique IP ad­dress (NAT) at the time in ques­tion:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. user name);
b.
the unique ser­vice iden­ti­fi­er (e.g. user name, MS­ISDN, DSL iden­ti­fi­er) of the net­work ac­cess ser­vice.

2 The re­quest for in­form­a­tion shall con­tain in­form­a­tion about the NAT trans­la­tion pro­ced­ure for the pur­pose of iden­ti­fic­a­tion:

a.
the pub­lic source IP ad­dress;
b.
if re­quired for iden­ti­fic­a­tion, the pub­lic source port num­ber;
c.
if re­quired for iden­ti­fic­a­tion, the pub­lic des­tin­a­tion IP ad­dress;
d.
if re­quired for iden­ti­fic­a­tion, the des­tin­a­tion port num­ber;
e.
if re­quired for iden­ti­fic­a­tion, the type of trans­port pro­tocol;
f.
the date and time.
Art. 39 Information Request Type IR_9_NAT: Information on NAT translation procedures 11  

1 In­form­a­tion Re­quest Type IR_9_N­AT com­prises the fol­low­ing in­form­a­tion for the pur­pose of iden­ti­fic­a­tion in con­nec­tion with NAT trans­la­tion pro­ced­ures if re­quired for iden­ti­fic­a­tion:

a.
the source IP ad­dress be­fore or after the NAT trans­la­tion pro­ced­ure, as the case may be;
b.
the source port num­ber be­fore or after the NAT trans­la­tion pro­ced­ure, as the case may be.

2 The re­quest for in­form­a­tion shall con­tain the fol­low­ing in­form­a­tion about the NAT trans­la­tion pro­ced­ure:

a.
the source IP ad­dress after or be­fore the NAT trans­la­tion pro­ced­ure, as the case may be;
b.
the source port num­ber after or be­fore the NAT trans­la­tion pro­ced­ure, as the case may be;
c.
if re­quired for iden­ti­fic­a­tion, the pub­lic des­tin­a­tion IP ad­dress;
d.
if re­quired for iden­ti­fic­a­tion, the des­tin­a­tion port num­ber;
e.
the type of the trans­port pro­tocol;
f.
the date and time of the NAT trans­la­tion pro­ced­ure.

11 The cor­rec­tion of 9 April 2019 relates to the French text only (AS 2019 1201).

Section 5 Types of Information on Applications

Art. 40 Information Request Type IR_10_TEL: Information on subscribers to telephony and multimedia services  

1 In­form­a­tion Re­quest Type IR_10_TEL com­prises the fol­low­ing in­form­a­tion about sub­scribers to tele­phony and mul­ti­me­dia ser­vices:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.12
in the case of mo­bile ser­vices, de­tails of the nat­ur­al per­son or leg­al en­tity in ac­cord­ance with Art­icle 20 and, if known, fur­ther con­tact de­tails and the sex of the nat­ur­al per­son;
c.
in the case of the oth­er tele­phony and mul­ti­me­dia ser­vices, the iden­ti­fic­a­tion in­form­a­tion spe­cified in Art­icle 19 and, if known, de­tails of the nat­ur­al per­son or leg­al en­tity, fur­ther con­tact de­tails and the sex of the nat­ur­al per­son;
d.
the fol­low­ing in­form­a­tion about each tele­phony and mul­ti­me­dia ser­vice ob­tained by the sub­scriber from the pro­vider:
1.
the unique iden­ti­fi­er des­ig­nat­ing the pro­vider (e.g. TSP num­ber),
2.
the unique ser­vice iden­ti­fi­er (e.g. tele­phone num­ber, SIP URI),
3.
the peri­od over which the ser­vice was used (start, first ac­tiv­a­tion and if ap­plic­able, ter­min­a­tion),
4.
the type of the ser­vice (e.g. private tele­com­mu­nic­a­tions in­stall­a­tion, pub­lic call sta­tion, fixed loc­a­tion or mo­bile loc­a­tion ser­vice),
5.
if ap­plic­able, the in­stall­a­tion ad­dresses of the fixed loc­a­tion net­work ac­cess to the ser­vice and their peri­od of valid­ity in each case,
6.
the statuses of the ser­vice as des­ig­nated in­tern­ally by the pro­vider (e.g. act­ive, sus­pen­ded, blocked),
7.
if ap­plic­able, the list or range of oth­er ad­dress­ing ele­ments or iden­ti­fi­ers re­gistered in con­nec­tion with this ser­vice (e.g. tele­phone num­bers, IM­PU),
8.
in the case of cus­tom­er re­la­tion­ships that are not based on a sub­scrip­tion con­tract, the time and the point of sup­ply (name and com­plete ad­dress) of the means of ac­cess and the name of the per­son who made the sup­ply,
9.
if ap­plic­able, de­tails of pre­de­ter­mined free choice of ser­vice pro­vider for con­nec­tions,
10.
if ap­plic­able, the IM­SI,
11.
if ap­plic­able, the SIM num­ber (IC­CID) at the time of sup­ply.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia. If us­ing let­ters a–d, a second query cri­terion must be ad­ded. If search­ing for char­ac­ter strings (let. a, c, d and f), the pro­vider must search only for the spe­cified spelling of the term in ac­cord­ance with the ap­plic­able FD­JP reg­u­la­tions:

a.
sur­name(s), first name(s);
b.
date of birth;
c.
coun­try and post­code or coun­try and place;
d.
street and, if pos­sible, house num­ber;
e.
iden­tity doc­u­ment num­ber and op­tion­ally, the type of iden­tity doc­u­ment;
f.
name and op­tion­al re­gistered of­fice the leg­al en­tity;
g.
busi­ness iden­ti­fic­a­tion num­ber (UID);
h.
sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
i.
ad­dress­ing ele­ments or iden­ti­fi­ers (e.g. tele­phone num­ber, SIP URI, TEL URI, IM­PU);
j.
IM­SI;
k.
SIM num­ber (IC­CID).

12 The cor­rec­tion of 3 Dec. 2019 relates to the French text only (AS 2019 4085).

Art. 41 Information Request Type IR_12_TEL: Information on telephony and multimedia services  

1 In­form­a­tion Re­quest Type IR_12_TEL com­prises the fol­low­ing in­form­a­tion about tele­phony and mul­ti­me­dia ser­vices. . For in­form­a­tion spe­cified in let­ters b, c and e, de­tails of the com­mon peri­od of valid­ity shall be provided:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the ad­dress­ing ele­ments or iden­ti­fi­ers re­gistered for this ser­vice (e.g. tele­phone num­bers, SIP URI, IMPI);
c.
if ap­plic­able, the IM­SI;
d.
for the pur­pose of iden­ti­fic­a­tion, the list of unique device iden­ti­fi­ers in ac­cord­ance with in­ter­na­tion­al stand­ards (e.g. IMEI, MAC ad­dress) of the devices user in con­nec­tion with this ser­vice from the pro­vider as well as, if avail­able, their des­ig­na­tion in text form;
e.
if ap­plic­able, the SIM num­bers (IC­CID);
f.
if ap­plic­able, the PUK and PUK2 codes.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia:

a.
the ad­dress­ing ele­ment (e.g. tele­phone num­ber, SIP URI, MS­ISDN, TEL URI);
b.
the IM­SI;
c.
the unique device iden­ti­fi­er in ac­cord­ance with in­ter­na­tion­al stand­ards (e.g. IMEI, MAC ad­dress);
d.
the in­stall­a­tion ad­dresses of the fixed loc­a­tion ac­cess to the net­work;
e.
the ser­vice iden­ti­fi­er (e.g. IMPI).
Art. 42 Information Request Type IR_13_EMAIL: Information on subscribers to E‑Mail-services  

1 In­form­a­tion Re­quest Type IR_13_E­MAIL com­prises the fol­low­ing in­form­a­tion about sub­scribers to email ser­vices:

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the iden­ti­fic­a­tion in­form­a­tion spe­cified in Art­icle 19 and, if known, the de­tails of the nat­ur­al per­son or leg­al en­tity, ad­di­tion­al con­tact de­tails and the sex of the nat­ur­al per­son;
c.
the fol­low­ing in­form­a­tion about each email ser­vice that the sub­scriber ob­tains from the pro­vider:
1.
the unique iden­ti­fi­er that in­dic­ates the pro­vider of the ser­vice,
2.
the unique ser­vice iden­ti­fi­er (e.g. email ad­dress, user name),
3.
the peri­od over which the ser­vice was used (start, first ac­tiv­a­tion and if ap­plic­able, ter­min­a­tion),
4.
if ap­plic­able, the list of all ad­di­tion­al ad­dress­ing ele­ments (e.g. ali­as ad­dress) that per­tain to this ser­vice,
5.
if ap­plic­able, the list of all ad­dresses, to which mes­sages ad­dressed to the re­ques­ted ad­dress are for­war­ded (e.g. mail­ing list);
d.
if ap­plic­able, the ad­di­tion­al ad­dress­ing ele­ments re­cor­ded by the pro­vider in con­nec­tion with this ser­vice (e.g. email ad­dress, MS­ISDN).

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia. If us­ing let­ters a–d, a second query cri­terion must be ad­ded. If search­ing for char­ac­ter strings (let. a, c, d and f), the pro­vider must search only for the spe­cified spelling of the term in ac­cord­ance with the ap­plic­able FD­JP reg­u­la­tions:

a.
sur­name(s), first name(s);
b.
date of birth;
c.
coun­try and post­code or coun­try and place;
d.
street and if pos­sible house num­ber;
e.
iden­tity doc­u­ment num­ber and, op­tion­ally, the type of iden­tity doc­u­ment;
f.
name and, op­tion­ally, re­gistered of­fice of the leg­al en­tity;
g.
busi­ness iden­ti­fic­a­tion num­ber (UID);
h.
sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
i.
ser­vice iden­ti­fi­er (e.g. email ad­dress, user name).
Art. 43 Information Request Type IR_15_COM: Information on subscribers to other telecommunications or derived communications services  

1 In­form­a­tion Re­quest Type IR_15_­COM com­prises the fol­low­ing in­form­a­tion about sub­scribers to oth­er tele­com­mu­nic­a­tions or de­rived com­mu­nic­a­tions ser­vices (e.g. mes­saging ser­vices, com­mu­nic­a­tions ser­vices in so­cial net­works, cloud and proxy ser­vices):

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the iden­ti­fic­a­tion in­form­a­tion spe­cified in Art­icle 19 and, if known, de­tails of the nat­ur­al per­son or leg­al en­tity, ad­di­tion­al con­tact de­tails and the sex of the nat­ur­al per­son;
c.
the fol­low­ing in­form­a­tion about each ad­di­tion­al tele­com­mu­nic­a­tions ser­vice or de­rived com­mu­nic­a­tions ser­vice that the sub­scriber ob­tains from the pro­vider:
1.
the unique iden­ti­fi­er that des­ig­nates the pro­vider,
2.
the unique ser­vice iden­ti­fi­er (e.g. user name),
3.
the peri­od over which the ser­vice was used (start, first ac­tiv­a­tion and if ap­plic­able, ter­min­a­tion),
4.
the statuses of the ser­vice as des­ig­nated in­tern­ally by the pro­vider (e.g. act­ive, sus­pen­ded, blocked) and their peri­od of valid­ity in each case,
5.
the list of oth­er ad­dress­ing ele­ments or iden­ti­fi­ers re­gistered in con­nec­tion with this ser­vice.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia. If us­ing let­ters a–d, a second query cri­terion must be ad­ded. If search­ing for char­ac­ter strings (let. a, c, d and f), the pro­vider must search only for the spe­cified spelling of the term in ac­cord­ance with the ap­plic­able FD­JP reg­u­la­tions:

a.
sur­name(s), first name(s);
b.
date of birth;
c.
coun­try and post­code or coun­try and place;
d.
street and, if pos­sible, house num­ber;
e.
iden­tity doc­u­ment num­ber and, op­tion­ally, the type of iden­tity doc­u­ment;
f.
name and, op­tion­ally, the re­gistered of­fice of the leg­al en­tity;
g.
busi­ness iden­ti­fic­a­tion num­ber (UID);
h.
sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
i.
ad­dress­ing ele­ment or iden­ti­fi­er (e.g. user name).

Section 6 Further Types of Information

Art. 44 Information Request Type IR_17_PAY: Information on the method of payment used by subscribers to telecommunications and derived communications services  

1 In­form­a­tion Re­quest Type IR_17_PAY com­prises the fol­low­ing in­form­a­tion about the meth­od of pay­ment used by sub­scribers to tele­com­mu­nic­a­tions and de­rived com­mu­nic­a­tions ser­vices:

a.
the unique iden­ti­fi­er that des­ig­nates the pro­vider;
b.
the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
c.
the unique iden­ti­fi­er that the pro­vider has as­signed to the sub­scriber for ac­count­ing or billing pur­poses;
d.
the unique ser­vice iden­ti­fi­er (e.g. tele­phone num­ber, SIP URI, user name);
e.
the meth­od of pay­ment (deb­it, bank trans­fer or pre­paid);
f.
the ac­count in­form­a­tion that the sub­scriber has giv­en to the pro­vider, con­sist­ing of the name of the bank, ac­count hold­er and IBAN (or BIC and ac­count num­ber) or na­tion­al bank num­ber and ac­count num­ber;
g.
the billing ad­dresses (house num­ber, street, PO box, post­code, place, coun­try) and their peri­od of valid­ity (start and if ap­plic­able, ter­min­a­tion).

2 The in­form­a­tion spe­cified in with para­graph 1 must be sup­plied if the pro­vider has it.

3 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia:13

a.
the sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the ser­vice iden­ti­fi­er (e.g. tele­phone num­ber, SIP URI, user name);
c.
the iden­ti­fi­er that the pro­vider has as­signed to the sub­scriber for ac­count­ing or billing pur­poses;
d.
the sub­scriber’s bank ac­count in­form­a­tion: IBAN (or BIC and ac­count num­ber) or na­tion­al bank num­ber and ac­count num­ber;
e.
the billing ad­dress (house num­ber, street, PO box, post­code, place, coun­try).

13 The cor­rec­tion of 6 March 2018 relates to the French text only (AS 2018 989).

Art. 45 Information Request Type IR_18_ID: Copy of official ID  

1 In­form­a­tion Re­quest Type IR_18_ID com­prises the pro­vi­sion of an elec­tron­ic copy of the sub­scriber’s iden­ti­fic­a­tion doc­u­ment re­cor­ded in ac­cord­ance with Art­icle 20.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od and sub­scriber or ser­vice iden­ti­fi­er, SIM num­ber (IC­CID) or IM­SI or, if ap­plic­able, device iden­ti­fi­er to which it relates.

Art. 46 Information Request Type IR_19_BILL: Copy of invoice  

1 In­form­a­tion Re­quest Type IR_19_­BILL com­prises the pro­vi­sion of elec­tron­ic cop­ies of all avail­able billing re­cords per­tain­ing to the sub­scriber, not in­clud­ing sec­ond­ary tele­com­mu­nic­a­tions data on tele­com­mu­nic­a­tions ser­vices and de­rived com­mu­nic­a­tions ser­vices.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od and unique sub­scriber or ser­vice iden­ti­fi­er or unique iden­ti­fi­er for ac­count­ing or billing to which it relates.

Art. 47 Information Request Type IR_20_CONTRACT: Copy of contract  

1 In­form­a­tion Re­quest Type IR_20_­CON­TRACT com­prises the pro­vi­sion of elec­tron­ic cop­ies of all avail­able con­tract doc­u­ments per­tain­ing to the sub­scriber to tele­com­mu­nic­a­tions ser­vices and de­rived com­mu­nic­a­tions ser­vices.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od and sub­scriber or ser­vice iden­ti­fi­er, the SIM num­ber (IC­CID) or IM­SI or, if ap­plic­able, the device iden­ti­fi­er to which it relates.

Art. 48 Information Request Type IR_21_TECH: Technical data  

1 In­form­a­tion Re­quest Type IR_21_TECH com­prises the pro­vi­sion of tech­nic­al data re­lat­ing to tele­com­mu­nic­a­tions sys­tems and net­work ele­ments, in par­tic­u­lar the loc­a­tion data for mo­bile ra­dio cells and pub­lic WLAN ac­cess points.

2 The loc­a­tion data com­prise:

a.
the iden­ti­fi­ers of net­work ele­ments (e.g. CGI, ECGI, SAI, RAI, TAI, BSSID) and the geo­graph­ic­al co­ordin­ates or oth­er de­tails of the loc­a­tion in ac­cord­ance with in­ter­na­tion­al stand­ards;
b.
if ap­plic­able, the postal ad­dress of the loc­a­tion;
c.
if ap­plic­able, the main dir­ec­tions of emis­sion of the an­ten­nae; and
d.
if ap­plic­able, oth­er avail­able loc­a­tion fea­tures.

3 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia:

a.
the geo­graph­ic­al co­ordin­ates of the loc­a­tion of the net­work ele­ment;
b.
the iden­ti­fi­er of the net­work ele­ment (e.g. CGI, ECGI, BSSID).

Section 7 General Provisions on the Surveillance of Telecommunications

Art. 49 Order to conduct surveillance of telecommunications  

1 The sur­veil­lance or­der sub­mit­ted to the PTSS shall con­tain the fol­low­ing in­form­a­tion:

a.
the con­tact de­tails of the or­der­ing au­thor­ity;
b.
the con­tact de­tails of the au­thor­ised per­sons en­vis­aged as re­cip­i­ents of the sur­veil­lance data;
c.
if known, the sur­name, first name, date of birth, ad­dress and oc­cu­pa­tion of the per­son to be placed un­der sur­veil­lance;
d.
the ref­er­ence num­bers and case names for the sur­veil­lance activ­it­ies;
e.
the reas­on for sur­veil­lance, in par­tic­u­lar the of­fence to be in­vest­ig­ated by means of sur­veil­lance;
f.
the names of the per­sons or en­tit­ies re­quired to co­oper­ate;
g.
the types of sur­veil­lance ordered or the type of spe­cial sur­veil­lance;
h.
the iden­ti­fi­ers sub­ject to sur­veil­lance (tar­get ID);
i.
if ne­ces­sary, an ap­plic­a­tion for gen­er­al au­thor­isa­tion for the sur­veil­lance of sev­er­al con­nec­tions without au­thor­isa­tion in spe­cif­ic cases (Art. 272 para. 2 and 3 Crim­PC or Art. 70c para. 2 and 3 MCPC);
j.
the start­ing date and the dur­a­tion of the sur­veil­lance;
k.
in the case of per­sons bound by pro­fes­sion­al secrecy in ac­cord­ance with Art­icle 271 Crim­PC or Art­icle 70b MCPC: a note to this ef­fect;
l.
if need be, meas­ures to pro­tect per­sons hold­ing pro­fes­sion­al secrets and fur­ther pro­tec­tion meas­ures that the au­thor­it­ies and the PTSS must take.

2 If con­duct­ing the sur­veil­lance so re­quires, the FD­JP may provide that the sur­veil­lance or­der sub­mit­ted to the PTSS must in­clude fur­ther tech­nic­al de­tails.

Art. 50 Surveillance duties  

1 Each TSP and each pro­vider of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 must be able to con­duct the sur­veil­lance activ­it­ies in ac­cord­ance with Sec­tions 8–12 of this Chapter (Art. 54–69) that re­late to ser­vices that they provide, or they must be able to ar­range for third parties to con­duct the sur­veil­lance. The fore­go­ing does not ap­ply to TSPs with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51.

2 The pro­vider shall en­sure its abil­ity to con­duct sur­veil­lance of tele­com­mu­nic­a­tions from the com­mer­cial launch of a ser­vice provided to cus­tom­ers.

3 It shall en­sure that it can ac­cept sur­veil­lance as­sign­ments out­side nor­mal work­ing hours in ac­cord­ance with Art­icle 10 and can con­duct them or ar­range for third party to do so in ac­cord­ance with the FD­JP re­quire­ments.

4 It shall guar­an­tee that with­in the peri­od spe­cified in the sur­veil­lance as­sign­ment sur­veil­lance will be con­duc­ted of all tele­com­mu­nic­a­tions traffic car­ried on the in­fra­struc­tures un­der its con­trol provided the traffic is part of the ser­vices un­der sur­veil­lance and can be as­signed to the iden­ti­fi­er un­der sur­veil­lance (tar­get ID).

5 It shall sup­port the PTSS, if ne­ces­sary, in or­der to en­sure that the trans­mit­ted sur­veil­lance data ac­tu­ally cor­res­ponds to the tele­com­mu­nic­a­tions traffic spe­cified in the sur­veil­lance as­sign­ment.

6 If ad­di­tion­al iden­ti­fi­ers are as­so­ci­ated with the iden­ti­fi­er un­der sur­veil­lance (tar­get ID) (e.g. IMPI with IM­PU, email ad­dress with ali­as ad­dress), the pro­vider shall en­sure that these iden­ti­fi­ers are also mon­itored as part of the type of sur­veil­lance.

Art. 51 TSP with reduced surveillance duties  

1 At the re­quest of a TSP, the PTSS shall de­clare it to be a TSP with re­duced sur­veil­lance du­ties (Art. 26 para. 6 SPTA) if it:

a.
only of­fers its tele­com­mu­nic­a­tions ser­vices in the field of edu­ca­tion and re­search; or
b.
meets neither of the fol­low­ing cri­ter­ia:
1.
sur­veil­lance as­sign­ments for 10 dif­fer­ent sur­veil­lance tar­gets in the past 12 months (ef­fect­ive date: 30 June),
2.
an­nu­al turnover in Switzer­land from tele­com­mu­nic­a­tions ser­vices and de­rived com­mu­nic­a­tions ser­vices of CHF 100 mil­lion in two suc­cess­ive fin­an­cial years.

2 Art­icle 22 para­graph 2 ap­plies to the cal­cu­la­tion of the val­ues spe­cified in para­graph 1 let­ter b.

3 TSPs with re­duced sur­veil­lance du­ties are re­quired to give writ­ten no­tice to the PTSS with sup­port­ing doc­u­ments if they:

a.
no longer of­fer their ser­vices ex­clus­ively in the field of edu­ca­tion and re­search; or
b.
achieve the value spe­cified in para­graph 1 let­ter b num­ber 2 for a second suc­cess­ive fin­an­cial year; no­tice must be giv­en with­in three months of the end of the fin­an­cial year.

4 The PTSS may rely on data ob­tained in im­ple­ment­ing the le­gis­la­tion re­lat­ing to the sur­veil­lance of post and tele­com­mu­nic­a­tions or by oth­er au­thor­it­ies in im­ple­ment­ing fed­er­al law.

5 A pro­vider that is de­clared to have more ex­tens­ive du­ties to provide in­form­a­tion must en­sure that it can store the data re­quired for provid­ing in­form­a­tion and provide the in­form­a­tion with­in 2 months and 12 months of the de­clar­a­tion re­spect­ively.

Art. 52 Providers of derived communication services with more extensive surveillance duties  

1 The PTSS shall in a rul­ing de­clare a pro­vider of de­rived com­mu­nic­a­tion ser­vices to have more ex­tens­ive sur­veil­lance du­ties (Art. 27 para. 3 SPTA) if it has met one of the fol­low­ing cri­ter­ia:

a.
sur­veil­lance as­sign­ments for 10 dif­fer­ent sur­veil­lance tar­gets in the past 12 months (ef­fect­ive date: 30 June);
b.
an­nu­al turnover in Switzer­land of CHF 100 mil­lion in two suc­cess­ive fin­an­cial years, provided a large part of its busi­ness op­er­a­tions is provid­ing de­rived com­mu­nic­a­tion ser­vices, and 5000 sub­scribers use the pro­vider’s ser­vices.

2 Art­icle 22 para­graphs 2–5 ap­ply mu­tatis mutandis.

Art. 53 Access to the installations  

1 The per­sons or en­tit­ies re­quired to co­oper­ate that must al­low the PTSS or the third parties that it in­structs ac­cess to its in­stall­a­tions shall al­low the PTSS ac­cess to build­ings, devices, lines, sys­tems, net­works and ser­vices to the ex­tent re­quired for sur­veil­lance.

2 They shall make ex­ist­ing means of net­work ac­cess to pub­lic tele­com­mu­nic­a­tions net­works avail­able free of charge. In con­sulta­tion with the PTSS or the third parties that it in­structs they shall provide new means of net­work ac­cess at the ex­pense of the PTSS to the ex­tent that this is re­quired for sur­veil­lance.

Section 8 Types of Real-Time Monitoring of Network Access Services

Art. 54 Surveillance Type RT_22_NA_IRI: Real-time monitoring of secondary telecommunications data in the case of network access services  

1 Sur­veil­lance Type RT_22_N­A_IRI com­prises the real-time sur­veil­lance of a net­work ac­cess ser­vice in the mo­bile com­mu­nic­a­tions sec­tor.

2 The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data of tele­com­mu­nic­a­tions traffic sent or re­ceived via the net­work ac­cess ser­vice un­der sur­veil­lance must be trans­mit­ted in real time:

a.
when ac­cess to the net­work is es­tab­lished or dis­con­nec­ted: the date, the time, the type of event and the reas­on for dis­con­nec­tion;
b.
the type of cur­rent ac­cess to the net­work;
c.
the AAA in­form­a­tion used by the net­work ac­cess ser­vice un­der sur­veil­lance, in par­tic­u­lar the sub­scriber iden­ti­fi­er and the IM­SI in the case of mo­bile com­mu­nic­a­tions;
d.
the IP ad­dresses or ad­dress ranges as­signed to the net­work ac­cess ser­vice un­der sur­veil­lance and the date and time of each as­sign­ment;
e.
the avail­able ad­dress­ing ele­ments of the net­work ac­cess ser­vice un­der sur­veil­lance, in the case of mo­bile com­mu­nic­a­tions, for ex­ample, the MS­ISDN or the IM­SI;
f.
the unique device iden­ti­fi­ers in ac­cord­ance with in­ter­na­tion­al stand­ards for the cur­rent ter­min­al devices of the net­work ac­cess ser­vice un­der sur­veil­lance (e.g. IMEI, MAC ad­dress);
g.
the type, date and time of the start and if ap­plic­able the end of tech­nic­al modi­fic­a­tions of ac­cess to the net­work (e.g. loc­a­tion up­date, change in mo­bile com­mu­nic­a­tions tech­no­logy) and, if known, its causes;
h.
the tar­get’s avail­able cur­rent loc­a­tion data or the cell used by the tar­get or of the WLAN ac­cess point used by the tar­get in ac­cord­ance with para­graph 3.

3 The loc­a­tion data com­prise:

a.
the iden­ti­fi­ers or a com­bin­a­tion of iden­ti­fi­ers (e.g. CGI, ECGI, SAI, RAI, TAI, BSSID) and the geo­graph­ic­al co­ordin­ates, and, if ap­plic­able, the main dir­ec­tion of emis­sion of the cell or of the WLAN ac­cess point, and, if avail­able, the type of mo­bile com­mu­nic­a­tions tech­no­logy used;
b.
the po­s­i­tion of the tar­get de­term­ined by the net­work, for ex­ample in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value, or in the form of poly­gons with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point, and, if avail­able, the type of mo­bile com­mu­nic­a­tions tech­no­logy used; or
c.
if avail­able, oth­er de­tails in ac­cord­ance with in­ter­na­tion­al stand­ards of the loc­a­tion of the tar­get or of the cell or of the WLAN ac­cess point, and, if avail­able, the type of mo­bile com­mu­nic­a­tions tech­no­logy used.
Art. 55 Surveillance Type RT_23_NA_CC_IRI: Real-time monitoring of content and secondary telecommunications data in the case of network access services  

Sur­veil­lance Type RT_23_N­A_C­C_IRI in­volves the real-time sur­veil­lance of a net­work ac­cess ser­vice. The con­tent of the tele­com­mu­nic­a­tion sent or re­ceived via the net­work ac­cess ser­vice un­der sur­veil­lance, and the re­lated sec­ond­ary tele­com­mu­nic­a­tions data in ac­cord­ance with Art­icle 54 para­graphs 2 and 3 must be trans­mit­ted in real time.

Section 9 Types of Real-Time Monitoring of Applications

Art. 56 Surveillance Type RT_24_TEL_IRI: Real-time monitoring of secondary telecommunications data for telephony and multimedia services  

1 Sur­veil­lance Type RT_24_TEL_IRI com­prises the real-time sur­veil­lance of a tele­phony and mul­ti­me­dia ser­vice and, if ap­plic­able, con­ver­ging ser­vices, in par­tic­u­lar SMS, voice mail and RCS. The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data of the tele­com­mu­nic­a­tion that is sent, pro­cessed or re­ceived via the ser­vices un­der sur­veil­lance must be trans­mit­ted in real time:

a.
the date and the time of log­ging-in and log­ging-out pro­cesses and their res­ult;
b.
the AAA in­form­a­tion used by the ser­vices un­der sur­veil­lance and the in­form­a­tion on re­gis­tra­tion and sub­scrip­tion events and the cor­res­pond­ing re­sponses, in par­tic­u­lar the sub­scriber iden­ti­fi­er (e.g. SIP URI, IMPI), the IM­SI in the case of mo­bile com­mu­nic­a­tions and – if ap­plic­able – the cus­tom­er’s and serv­er’s IP ad­dresses and port num­bers as well as de­tails of the pro­tocol used;
c.
the sig­nalling in­form­a­tion, in par­tic­u­lar on the serving sys­tem, on sub­scriber status and on ser­vice qual­ity;
d.
if ap­plic­able, the pres­ence in­form­a­tion;
e.
in the case of com­mu­nic­a­tions, com­mu­nic­a­tion at­tempts and tech­nic­al modi­fic­a­tions (e.g. in­clu­sion of ad­di­tion­al ser­vices, in­clu­sion of or change to con­ver­ging ser­vices, changes in mo­bile com­mu­nic­a­tions tech­no­logy, loc­a­tion up­dates), if ap­plic­able:
1.
their type, the date and the time of their start and if ap­plic­able their end,
2.
the ad­dress­ing ele­ments (e.g. MS­ISDN, E.164-num­ber, SIP URI, IM­PU) of all sub­scribers in com­mu­nic­a­tion and their role,
3.
the ac­tu­al known des­tin­a­tion ad­dress and the avail­able in­ter­me­di­ate ad­dresses where the com­mu­nic­a­tion or the com­mu­nic­a­tion at­tempt is di­ver­ted or for­war­ded,
4.
the unique device iden­ti­fi­ers in ac­cord­ance with in­ter­na­tion­al stand­ards for the ter­min­al devices of the ser­vices un­der sur­veil­lance (e.g. IMEI, MAC ad­dress),
5.
the oth­er avail­able iden­ti­fi­ers,
6.
the reas­ons for the ter­min­a­tion of com­mu­nic­a­tion or its non-ma­ter­i­al­isa­tion or for the tech­nic­al modi­fic­a­tion,
7.
the sig­nalling in­form­a­tion on ad­di­tion­al ser­vices (e.g. con­fer­ence calls, call for­ward­ing, DTMF),
8.
the status of the com­mu­nic­a­tion or of the com­mu­nic­a­tion at­tempt,
9.
and in the case of mo­bile loc­a­tion ser­vices, the avail­able cur­rent loc­a­tion data for the tar­get or the cell used by the tar­get or for the WLAN ac­cess point used by the tar­get in ac­cord­ance with para­graph 2.

2 The loc­a­tion data com­prise:

a.
the iden­ti­fi­ers or a com­bin­a­tion of iden­ti­fi­ers (e.g. CGI, ECGI, SAI, RAI, TAI, BSSID) and the geo­graph­ic­al co­ordin­ates of the cell or the WLAN ac­cess point and, if avail­able, the type of mo­bile com­mu­nic­a­tions tech­no­logy used;
b.
the po­s­i­tion of the tar­get de­term­ined by the net­work, for ex­ample in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value, or in the form of poly­gons, with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point as well as the type of mo­bile com­mu­nic­a­tions tech­no­logy used; or
c.
if avail­able, oth­er de­tails in ac­cord­ance with in­ter­na­tion­al stand­ards rel­ev­ant to the loc­a­tion of the tar­get or the cell or of the WLAN ac­cess point, and the type of mo­bile com­mu­nic­a­tions tech­no­logy used.
Art. 57 Surveillance Type RT_25_TEL_CC_IRI: Real-time surveillance of content and secondary telecommunications data in the case of telephony and multimedia services  

Sur­veil­lance Type RT_25_TEL_C­C_IRI com­prises the real-time sur­veil­lance of a tele­phony and mul­ti­me­dia ser­vice and, if ap­plic­able, con­ver­ging ser­vices, in par­tic­u­lar SMS, voice mail and RCS. The con­tent of the tele­com­mu­nic­a­tions traffic sent, pro­cessed or re­ceived via the ser­vices un­der sur­veil­lance, as well as the re­lated sec­ond­ary tele­com­mu­nic­a­tions data in ac­cord­ance with Art­icle 56 must be trans­mit­ted in real time.

Art. 58 Surveillance Type RT_26_EMAIL_IRI: Real-time monitoring of secondary telecommunications data on email services  

Sur­veil­lance Type RT_26_E­MAIL_IRI com­prises the real-time sur­veil­lance of an email ser­vice. The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data on the tele­com­mu­nic­a­tions traffic sent, pro­cessed or re­ceived via the ser­vice un­der sur­veil­lance must be trans­mit­ted in real time:

a.
the date and the time of log­ging-in and log­ging-out pro­cesses and their status;
b.
the AAA in­form­a­tion used by the ser­vice un­der sur­veil­lance, in par­tic­u­lar the sub­scriber iden­ti­fi­er and, if ap­plic­able, the ali­as ad­dress;
c.
the cus­tom­er’s and serv­er’s IP ad­dresses and port num­bers as well as de­tails of the pro­tocol used;
d.
the date, time, volume of data, email ad­dresses of the sender and the re­cip­i­ent of the mes­sage and the IP ad­dresses and port num­bers of the send­ing and re­ceiv­ing email serv­ers for the fol­low­ing events:
1.
send­ing or for­ward­ing of a mes­sage,
2.
re­ceipt of a mes­sage,
3.
pro­cessing of a mes­sage in the mail­box,
4.
down­load­ing of a mes­sage from the mail­box,
5.
up­load­ing of a mes­sage to the mail­box.
Art. 59 Surveillance Type RT_27_EMAIL_CC_IRI: Real-time monitoring of content and secondary telecommunications data on email services  

Sur­veil­lance Type RT_27_E­MAIL_C­C_IRI com­prises the real-time sur­veil­lance of an email -ser­vice. The con­tent of the tele­com­mu­nic­a­tions traffic sent, pro­cessed or re­ceived via the ser­vice un­der sur­veil­lance, as well as the re­lated sec­ond­ary tele­com­mu­nic­a­tions data in ac­cord­ance with Art­icle 58 must be trans­mit­ted in real time.

Section 10 Types of Retroactive Surveillance

Art. 60 Surveillance Type HD_28_NA: Retroactive surveillance of secondary telecommunications data in the case of network access services  

Sur­veil­lance Type HD_28_NA in­cludes the ret­ro­act­ive sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data of a net­work ac­cess ser­vice. The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data of the past tele­com­mu­nic­a­tion that has been sent or has been re­ceived via the net­work ac­cess ser­vice un­der sur­veil­lance must be trans­mit­ted:

a.
the date and the time of the start and if ap­plic­able the end or the dur­a­tion or the ses­sion;
b.
the type and status of the net­work ac­cess;
c.
the iden­ti­fi­er that was used for au­then­tic­at­ing the user at the ac­cess point un­der sur­veil­lance, for ex­ample the user name;
d.
the IP ad­dresses or ad­dress ranges as­signed to the tar­get and their type;
e.
if avail­able, the unique device iden­ti­fi­er of the ter­min­al device used by the tar­get in ac­cord­ance with in­ter­na­tion­al stand­ards (e.g. MAC ad­dress, IMEI in the case of mo­bile com­mu­nic­a­tions);
f.
if avail­able, the volumes of data that were up­loaded and down­loaded dur­ing the ses­sion;
g.
in the case of ac­cess to the net­work via mo­bile com­mu­nic­a­tions: the GPRS or EPS in­form­a­tion (in par­tic­u­lar IM­SI or MS­ISDN) and the fol­low­ing loc­a­tion data at the be­gin­ning and the end of the ses­sion as well as dur­ing the ses­sion if avail­able; if known, ad­di­tion­al loc­a­tion in­form­a­tion from mari­time nav­ig­a­tion or avi­ation must be trans­mit­ted:
1.
the cell and re­gion iden­ti­fi­ers as well as the geo­graph­ic­al co­ordin­ates, the postal ad­dresses and if ap­plic­able the main dir­ec­tions of emis­sion the cells used by the tar­get, or
2.
the po­s­i­tions of the tar­get de­term­ined by the net­work (e.g. in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value, or in the form of poly­gons with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point) as well as the re­lated postal ad­dresses, or
3.
oth­er de­tails in ac­cord­ance with in­ter­na­tion­al stand­ards of the tar­get’s loc­a­tions or the cells that he or she used, as well as the re­lated postal ad­dresses;
h.
in the case of ac­cess to the net­work via a pub­lic WLAN: the BSSID, and, if avail­able, the SSID and the loc­a­tion data in the form of geo­graph­ic­al co­ordin­ates and the postal ad­dress of the WLAN ac­cess point used by the tar­get; the user name, the type of au­then­tic­a­tion, the avail­able ad­di­tion­al in­form­a­tion on user au­then­tic­a­tion (tele­phone num­ber, MAC ad­dress, IM­SI, user iden­ti­fi­er and pass­word used for au­then­tic­a­tion) and the IP ad­dress of the WLAN ac­cess point. If avail­able, ad­di­tion­al loc­a­tion in­form­a­tion from mari­time nav­ig­a­tion or avi­ation must be trans­mit­ted;
i.
in the case of fixed net­work ac­cess: the ad­dress­ing ele­ments of the ac­cess to the net­work and. if avail­able, the postal ad­dress.
Art. 61 Surveillance Type HD_29_TEL: Retroactive surveillance of secondary telecommunications data relating to telephony and multimedia services  

Sur­veil­lance Type HD_29_TEL com­prises the ret­ro­act­ive sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data of a tele­phony and mul­ti­me­dia ser­vice and, if ap­plic­able, con­ver­ging ser­vices, in par­tic­u­lar SMS, MMS and voice mail. The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data of the past tele­com­mu­nic­a­tions traffic in com­mu­nic­a­tions and com­mu­nic­a­tion at­tempts us­ing the ser­vices un­der sur­veil­lance must be trans­mit­ted:

a.
their type, the date and time of the start and, if ap­plic­able, the end or their dur­a­tion;
b.
the ad­dress­ing ele­ments (e.g. MS­ISDN, E.164-num­ber, SIP URI, IM­PU) of all sub­scribers in com­mu­nic­a­tion and their roles;
c.
the reas­on for the end of the com­mu­nic­a­tion or the com­mu­nic­a­tion at­tempt;
d.
in the case of mo­bile com­mu­nic­a­tions (mul­ti­me­dia ser­vices if avail­able): the IMEI of the ter­min­al device used by the tar­get and the IM­SI of the tar­get;
e.
if ap­plic­able, the type of car­ri­er ser­vice;
f.
in the case of SMS and MMS: the in­form­a­tion on the event, the type (only in the case of SMS) and the status;
g.
in the case of mo­bile com­mu­nic­a­tions: the loc­a­tion data for the cell used by the tar­get at the be­gin­ning and at the end of the com­mu­nic­a­tion or of the com­mu­nic­a­tion at­tempt. If known, ad­di­tion­al loc­a­tion in­form­a­tion from mari­time nav­ig­a­tion or avi­ation must be trans­mit­ted:
1.
the cell and re­gion iden­ti­fi­ers, the geo­graph­ic­al co­ordin­ates and if ap­plic­able the main dir­ec­tions of emis­sion and the postal ad­dress, or
2.
the po­s­i­tions of the tar­get de­term­ined by the net­work (e.g. in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value or in the form of poly­gons with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point) as well as the re­lated postal ad­dresses, or
3.
oth­er de­tails in ac­cord­ance with in­ter­na­tion­al stand­ards of the tar­get’s loc­a­tions or the cells that he or she used, as well as the re­lated postal ad­dresses;
h.
in the case of mul­ti­me­dia ser­vices:
1.
the cus­tom­er’s IP ad­dress and its type and the port num­ber,
2.
the com­mu­nic­a­tion cor­rel­a­tion iden­ti­fi­er,
3.
the types of mul­ti­me­dia con­tent,
4.
in­form­a­tion on the mul­ti­me­dia com­pon­ents (time, name, de­scrip­tion, ini­ti­at­or, ac­cess-cor­rel­a­tion iden­ti­fi­er), and
5.
if ap­plic­able, in­form­a­tion on the IMS ser­vices (type of IMS ser­vice used, role of the net­work ele­ment from which the sec­ond­ary tele­com­mu­nic­a­tions data come); and
i.
in the case of mul­ti­me­dia ser­vices: in­form­a­tion on the tar­get’s net­work ac­cess:
1.
the ac­cess type,
2.
the ac­cess class,
3.
wheth­er the in­form­a­tion on ac­cess to the net­work comes from the net­work, and
4.
the loc­a­tion data re­lat­ing to the net­work ac­cess at the be­gin­ning and the end of the mul­ti­me­dia ses­sion, and, if avail­able, dur­ing the mul­ti­me­dia ses­sion:
in the case of ac­cess to the net­work via mo­bile com­mu­nic­a­tions: the loc­a­tion data for the cell used by the tar­get in ac­cord­ance with let­ter g, or
in the case of ac­cess to the net­work via WLAN: the avail­able loc­a­tion data of the WLAN ac­cess point used by the tar­get (geo­graph­ic­al co­ordin­ates, postal ad­dress), or
in the case of fixed net­work ac­cess: the avail­able postal ad­dress of the ac­cess used by the tar­get.
Art. 62 Surveillance Type HD_30_EMAIL: retroactive surveillance of secondary telecommunications data in the case of email services  

Sur­veil­lance Type HD_30_E­MAIL com­prises the ret­ro­act­ive sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data of an email -ser­vice. The fol­low­ing sec­ond­ary tele­com­mu­nic­a­tions data of the past tele­com­mu­nic­a­tion sent, pro­cessed or re­ceived via the ser­vice un­der sur­veil­lance must be trans­mit­ted:

a.
the date, the time, the type of event, the sub­scriber iden­ti­fi­ers, if ap­plic­able the ali­as ad­dress, the sender and re­cip­i­ent ad­dresses, the pro­tocol used, the IP ad­dresses of the serv­er and the cli­ent, and, if ap­plic­able, the de­liv­ery status of the mes­sage in the case of the fol­low­ing events: send­ing, re­ceipt, mail­box log-in, mail­box log-out and in the case of the fol­low­ing events, if avail­able: down­load­ing, up­load­ing, de­le­tion, pro­cessing, ad­di­tion of a mes­sage;
b.
the IP ad­dresses and names of the send­ing and re­ceiv­ing email serv­ers.
Art. 63 Surveillance Type HD_31_PAGING: Identifying most recent activity on the mobile terminal device of the person under surveillance  

Sur­veil­lance Type HD_31_PA­GING com­prises the iden­ti­fic­a­tion of the most re­cent activ­ity de­tec­ted by the mo­bile tele­phony pro­vider (net­work ac­cess ser­vices, tele­phony and mul­ti­me­dia ser­vices) on the mo­bile ter­min­al device of the per­son un­der sur­veil­lance and provid­ing the MS­ISDN, IM­SI, IMEI (if avail­able), the type of mo­bile com­mu­nic­a­tions tech­no­logy, the fre­quency band, the unique iden­ti­fi­er of the mo­bile net­work, the date and time of most re­cent activ­ity de­tec­ted, as well as one of the fol­low­ing de­tails re­quired to de­term­ine the loc­a­tion:

a.
in­form­a­tion about the cell used: the iden­ti­fi­er or a com­bin­a­tion of iden­ti­fi­ers (e.g. CGI, ECGI, SAI, RAI, TAI), the postal ad­dress, the main dir­ec­tion of emis­sion or, in the case of com­plex cells, the main dir­ec­tions of emis­sion and the type of cell, the geo­graph­ic­al co­ordin­ates;
b.
the postal ad­dress and de­tails of the po­s­i­tion of the ter­min­al device dur­ing its most re­cent activ­ity as de­term­ined by the net­work, for ex­ample in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value or in the form of a poly­gon to­geth­er with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point; or
c.
the postal ad­dress and oth­er stand­ard­ised de­tails de­term­ined by the net­work of the po­s­i­tion of the ter­min­al device dur­ing its most re­cent activ­ity or of the loc­a­tion of the cell used.
Art. 64 Surveillance Type AS_32_PREP_COV: Network coverage analysis in preparation for an antenna search  

1 Sur­veil­lance Type AS­_32_­PREP_­COV com­prises the net­work ana­lys­is in pre­par­a­tion for an an­tenna search in ac­cord­ance with Art­icle 66. It is car­ried out by the TSPs and serves to identi­fy the mo­bile ra­dio cells or pub­lic WLAN ac­cess points that most prob­ably cov­er the loc­a­tion de­scribed by the or­der­ing au­thor­ity in the form of geo­graph­ic­al co­ordin­ates or by means of postal ad­dress, if ap­plic­able tak­ing ac­count of ad­di­tion­al in­form­a­tion (e.g. time of day, weath­er, day of the week, loc­a­tion with­in or out­side of a build­ing).

2 The TSPs shall sup­ply the PTSS with a list of cell iden­ti­fi­ers (e.g. CGI, ECGI) or the BSSID for the mo­bile ra­dio cells or pub­lic WLAN ac­cess points iden­ti­fied.

Art. 65 Surveillance Type AS_33_PREP_REF: Reference communications or instances of reference network access in preparation for an antenna search  

1 Sur­veil­lance Type AS­_33_­PREP_REF com­prises the iden­ti­fic­a­tion of mo­bile ra­dio cells or pub­lic WLAN ac­cess points on the basis of ref­er­ence com­mu­nic­a­tions and in­stances of ref­er­ence net­work ac­cess in pre­par­a­tion for an an­tenna search in ac­cord­ance with Art­icle 66.

2 The or­der­ing au­thor­ity shall it­self ar­range for ref­er­ence com­mu­nic­a­tions to be made and the ref­er­ence net­work to be ac­cessed at the loc­a­tion con­cerned and shall send the PTSS a list with the fol­low­ing re­lated de­tails:

a.
the type of com­mu­nic­a­tion or of ac­cess to the net­work;
b.
the date and the time of the com­mu­nic­a­tion or ac­cess to the net­work;
c.
the ad­dress­ing ele­ment of the tele­phony and mul­ti­me­dia ser­vice used or of the net­work ac­cess ser­vice;
d.
if ap­plic­able, the name of the mo­bile net­work used.

3 The PTSS shall in­struct the TSPs, on the basis of the sec­ond­ary tele­com­mu­nic­a­tions data re­lat­ing to pre­vi­ous tele­com­mu­nic­a­tions traffic, to identi­fy the mo­bile ra­dio cells or pub­lic WLAN ac­cess points used in each case base at the be­gin­ning and at the end of the ref­er­ence com­mu­nic­a­tions and in­stances of ref­er­ence net­work ac­cess in ac­cord­ance with para­graph 2 and to provide it with a list of the cor­res­pond­ing cell iden­ti­fi­ers (e.g. CGI, ECGI) or BSSID com­pleted in ac­cord­ance with para­graph 2.

Art. 66 Surveillance Type AS_34: Antenna search  

1 Sur­veil­lance Type AS­_34 com­prises the ret­ro­act­ive sur­veil­lance of all com­mu­nic­a­tions, com­mu­nic­a­tion at­tempts and in­stances of net­work ac­cess that have taken place via a spe­cif­ic mo­bile ra­dio cell or a spe­cif­ic pub­lic WLAN ac­cess point over a peri­od of up to two hours.14

2 The TSP shall sup­ply the sec­ond­ary tele­com­mu­nic­a­tions data res­ult­ing from para­graph 1 re­lat­ing to pre­vi­ous tele­com­mu­nic­a­tions traffic in ac­cord­ance with Art­icle 60 and 61.

14 The cor­rec­tion of 3 Ju­ly 2018 relates to the Itali­an text only (AS 2018 2551).

Section 11 Missing Person and Wanted Person Searches

Art. 67 Types of surveillance EP: Missing person search  

The fol­low­ing types of sur­veil­lance may be ordered for a miss­ing per­son search in ac­cord­ance with Art­icle 35 SPTA:

a.
Type EP_35_PA­GING: de­term­in­ing the most re­cent activ­ity de­tec­ted by the mo­bile tele­phony pro­vider (net­work ac­cess ser­vices and tele­phony and mul­ti­me­dia ser­vices) of the mo­bile ter­min­al device be­long­ing to the miss­ing per­son or a third party and pro­vi­sion of the MS­ISDN, the IM­SI, the IMEI (if avail­able), the type of mo­bile com­mu­nic­a­tions tech­no­logy, the fre­quency band, the unique iden­ti­fi­er of the mo­bile net­work, the date and the time of the most re­cent activ­ity de­tec­ted as well as any one of the fol­low­ing de­tails re­quired to de­term­ine the loc­a­tion:
1.
in­form­a­tion about the cell used: the iden­ti­fi­er or a com­bin­a­tion of iden­ti­fi­ers (e.g. CGI, ECGI, SAI, RAI, TAI), the postal ad­dress, the main dir­ec­tion of emis­sion or, in the case of com­plex cells, the main dir­ec­tions of emis­sion and the type of cell, the geo­graph­ic­al co­ordin­ates,
2.
the postal ad­dress and the de­tails of the po­s­i­tion of the ter­min­al device de­term­ined by the net­work dur­ing its most re­cent activ­ity, for ex­ample in the form of geo­graph­ic­al co­ordin­ates and the re­lated un­cer­tainty value or in the form of a poly­gon to­geth­er with de­tails of the geo­graph­ic­al co­ordin­ates of each poly­gon point, or
3.
the postal ad­dress and oth­er stand­ard­ised de­tails de­term­ined by the net­work of the po­s­i­tion of the ter­min­al device dur­ing its most re­cent activ­ity or of the loc­a­tion of the cell used;
b.
Type EP_36_RT_C­C_IRI (real-time sur­veil­lance of con­tent and sec­ond­ary tele­com­mu­nic­a­tions data): the com­bin­a­tion of types of sur­veil­lance in ac­cord­ance with Art­icle 55 (net­work ac­cess ser­vices) and in ac­cord­ance with Art­icle 57 (tele­phony and mul­ti­me­dia ser­vices);
c.
Type EP_37_RT_IRI (real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data): the com­bin­a­tion of types of sur­veil­lance in ac­cord­ance with Art­icle 54 (net­work ac­cess ser­vices) and in ac­cord­ance with Art­icle 56 (tele­phony and mul­ti­me­dia ser­vices);
d.
Type EP_38_HD (ret­ro­act­ive sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data): the com­bin­a­tion of types of sur­veil­lance in ac­cord­ance with Art­icle 60 (net­work ac­cess ser­vices) and in ac­cord­ance with Art­icle 61 (tele­phony and mul­ti­me­dia ser­vices).
Art. 68 Wanted person search  

The fol­low­ing types of sur­veil­lance may be ordered for a search for con­victed per­sons in ac­cord­ance with Art­icle 36 SPTA; “wanted per­son search” must be in­dic­ated in the sur­veil­lance or­der as the reas­on for sur­veil­lance (Art. 49 para. 1 let. e):

a.
one of the types of real-time sur­veil­lance of the con­tent and sec­ond­ary tele­com­mu­nic­a­tions data of net­work ac­cess ser­vices or ap­plic­a­tions in ac­cord­ance with Art­icles 55, 57 or 59;
b.
one of the types of real-time sur­veil­lance of sec­ond­ary tele­com­mu­nic­a­tions data of net­work ac­cess ser­vices or ap­plic­a­tions in ac­cord­ance with Art­icles 54, 56 or 58;
c.
one of the types of ret­ro­act­ive sur­veil­lance in ac­cord­ance with Art­icles 60–63;
d.
an an­tenna search in ac­cord­ance with Art­icle 66 and the cor­res­pond­ing pre­par­a­tions in ac­cord­ance with Art­icle 64 and 65.

Section 12 Off-Network Identifiers

Art. 69  

Sur­veil­lance in ac­cord­ance with Art­icles 56–59, 61 and 62 also in­cludes tele­com­mu­nic­a­tion car­ried out via the ser­vices un­der sur­veil­lance that can be as­signed to the iden­ti­fi­er un­der sur­veil­lance (tar­get ID) even if the iden­ti­fi­er un­der sur­veil­lance is not ad­min­istered by the pro­vider giv­en the as­sign­ment.

Chapter 4 Final Provisions

Art. 70 Organisational, administrative and technical regulations  

The FD­JP shall is­sue the or­gan­isa­tion­al, ad­min­is­trat­ive and tech­nic­al reg­u­la­tions on con­duct­ing sur­veil­lance of post and tele­com­mu­nic­a­tions. In par­tic­u­lar, it shall de­term­ine the dead­lines with­in which the rel­ev­ant data must be sup­plied.

Art.71 Implementation  

1 The PTSS shall provide elec­tron­ic forms and in­ter­faces to be used by those con­cerned. The forms and in­ter­faces shall make it pos­sible in par­tic­u­lar for:

a.
the or­der­ing au­thor­it­ies:
1.
to sub­mit a sur­veil­lance or­der to the PTSS,
2.
to in­struct the PTSS to grant or amend rights of ac­cess;
b.
the PTSS:
1.
to in­struct the per­sons or en­tit­ies re­quired to co­oper­ate with the con­duct of a sur­veil­lance meas­ure,
2.
to pass on a re­quest for in­form­a­tion to the per­sons or en­tit­ies re­quired to co­oper­ate and to for­ward their an­swers to the re­quest­ing au­thor­ity;
c.
the au­thor­ised au­thor­it­ies to sub­mit a re­quest for in­form­a­tion to the PTSS.

2 The PTSS may at the ap­pro­pri­ate time re­place the elec­tron­ic forms with on­line ac­cess to the Ser­vice’s pro­cessing sys­tem and in­tro­duce an elec­tron­ic ap­prov­al pro­cess for or­ders re­quir­ing ap­prov­al. The elec­tron­ic forms may con­tin­ue to be used if on­line ac­cess to the pro­cessing sys­tem is im­possible for tech­nic­al reas­ons or if the pro­cessing sys­tem fails.

Art.72 Repeal of another enactment  

The Or­din­ance of 31 Oc­to­ber 200115 on the Sur­veil­lance of Post and Tele­com­mu­nic­a­tions is re­pealed.

15 [AS 2001 3111; 2004 1431, 2021Art. 7, 3383; 2006 4705No II 77; 2007 4029; 2011 5955; 2016 4337No II; 2017 4151 An­nex 4 No II 11]

Art.73 Amendment of other enactments  

The or­din­ances be­low are amended as fol­lows:

1. and 2.16

16 The amend­ments may be con­sul­ted un­der AS 2018 147.

Art. 74 Transitional provisions  

1 Sur­veil­lance activ­it­ies ordered be­fore this Or­din­ance comes in­to force shall con­tin­ue un­changed. These activ­it­ies shall be ex­ten­ded or ter­min­ated in ac­cord­ance with the pre­vi­ous law ap­plic­able to those types of sur­veil­lance.

2 Cir­cuit tri­als on­go­ing in ac­cord­ance with the pre­vi­ous prac­tice when this Or­din­ance comes in­to force shall be ter­min­ated.

3 TSPs that sub­mit an ap­plic­a­tion to the PTSS for cat­egor­isa­tion as a TSP with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51 with­in three months of this Or­din­ance com­ing in­to force shall be deemed to be such from the date on which this Or­din­ance comes in­to force and for the dur­a­tion of the pro­ced­ure. The PTSS may re­voke this cat­egor­isa­tion for the dur­a­tion of the pro­ced­ure if ap­prov­al of the ap­plic­a­tion is un­likely. Art­icle 51 para­graph 5 does not ap­ply to TSPs pre­vi­ously re­quired to re­port.

4 With­in 3 months of this Or­din­ance com­ing in­to force, TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion in ac­cord­ance with Art­icle 22 shall modi­fy their sys­tems in or­der to im­ple­ment the new re­quire­ments on the iden­ti­fic­a­tion the sub­scribers (Art. 19) and re­cord­ing per­sons’ de­tails in the case of mo­bile ser­vices (Art. 20).

5 With­in 6 months of this Or­din­ance com­ing in­to force, TSPs, with the ex­cep­tion of those with re­duced sur­veil­lance du­ties in ac­cord­ance with Art­icle 51, and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive sur­veil­lance du­ties in ac­cord­ance with Art­icle 52 shall modi­fy their sys­tems in or­der to be able to sup­ply the in­form­a­tion spe­cified in Art­icles 38 and 39.

6 With­in 24 months of this Or­din­ance com­ing in­to force:

a.
it must be pos­sible to sup­ply the sec­ond­ary tele­com­mu­nic­a­tions data on com­mu­nic­a­tion at­tempts in the case of ret­ro­act­ive sur­veil­lance activ­it­ies;
b.
TSPs must make tech­nic­al modi­fic­a­tions to the sys­tems they have avail­able in or­der to be able to sup­ply the data on email ser­vices spe­cified in Art­icles 58, 59 and 62. Be­fore then, they must sup­ply the data on email ser­vices in the same way as be­fore.

7 Un­til the new pro­cessing sys­tem pro­cured un­der the tele­com­mu­nic­a­tions sur­veil­lance17 pro­gramme comes in­to op­er­a­tion:

a.
the PTSS may con­tin­ue to com­pile stat­ist­ics (Art. 12) in ac­cord­ance with the pre­vi­ous law;
b.
in­form­a­tion pro­vi­sion (Art. 35–48) and sur­veil­lance activ­it­ies (Art. 54–68) shall con­tin­ue to be car­ried out with the ex­ist­ing sys­tem, the pre­vi­ous formats and the cor­res­pond­ing forms. They shall be trans­mit­ted us­ing a se­cure means of trans­mis­sion au­thor­ised by the PTSS, by post or fax; Art­icle 17 para­graphs 1–2 does not ap­ply;
c.
in­form­a­tion pro­vi­sion based on a flex­ible name search in ac­cord­ance with Art­icle 27 in con­junc­tion with Art­icles 35, 40, 42 and 43 is not pos­sible; from the date on which the new sys­tem comes in­to op­er­a­tion, it will only be car­ried out by TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion in ac­cord­ance with Art­icle 22 that have mod­i­fied their sys­tems ac­cord­ingly.

8 With­in 12 months of the new pro­cessing sys­tem com­ing in­to op­er­a­tion, TSPs and pro­viders of de­rived com­mu­nic­a­tion ser­vices with more ex­tens­ive du­ties to provide in­form­a­tion in ac­cord­ance with Art­icle 22 shall modi­fy their sys­tems in or­der to sup­ply the in­form­a­tion spe­cified in Art­icles 35–37 and 40–42 and in Art­icle 27 in con­junc­tion with Art­icles 35, 40 and 42 auto­mat­ic­ally via the query in­ter­face of the pro­cessing sys­tem (Art. 18 para. 2) and in or­der to be able to carry out the flex­ible name search in ac­cord­ance with Art­icle 27 in con­junc­tion with Art­icles 35, 40, 42 and 43.

Art. 75 Commencement  

This Or­din­ance comes in­to force on 1 March 2018.

Annex

(Art. 2)

Terms and abbreviations

1.
IP address (internet protocol address): address that identifies all devices connected to a network that communicate using the internet protocol; there are Version 4 (IPv4) and the Version 6 (IPv6) IP addresses;
2.
Subscribers: persons who have entered into a contract with a provider of telecommunications or derived communications services on using its services or who have registered for its services or received a means of access to its services;
3.
Multimedia services: communications services which in addition to speech integrate other types of media and functions, such as video, file transfer, images, audio, parts of content, presence information (examples: video telephony, unified communication, RCS, multimedia telephony device);
4.
Identifier: addressing element, identification number or other unique indicator of a specific subscriber, a specific service or a specific device;
5.
MSISDN (Mobile Subscriber Integrated Services Digital Network Number):unique telephone number on which subscribers to a mobile network can be called;
6.
DSL identifier (Digital Subscriber Line Identifier): identifier of a digital subscriber line, i.e. of a broadband access to the network by means of which data can be sent and received via copper wires;
7.
IP prefix: part of the IPv6 address that identifies network concerned;
8.
IP address range:a number of successive IP addresses;
9.
Net mask:in internet protocol Version 4 (IPv4), describes how many bits at the start of the IP address displayed identify the network concerned;
10.
Prefix length:in internet protocol Version 6 (IPv6), describes how many bits at the start of the IP address displayed identify the network concerned;
11.
SIM (Subscriber Identity Module): smart card or chip permanently built into to the terminal device on which the IMSI and the related key are securely stored; the SIM is used to authenticate the subscribers to a mobile network, and includes the USIM (Universal Subscriber Identity Module), UICC (Universal Integrated Circuit Card)andeSIM (embedded SIM);
12.
ICCID (Integrated Circuit Card Identifier):series-number of a built-in chip (e.g. eSIM) or of a smart card (e.g. SIM card) that uniquely identifies the chip;
13.
IMSI (International Mobile Subscriber Identity): number that allows the unique international identification of mobile communication subscribers;
14.
IMEI (International Mobile Equipment Identity): number that allows the unique international identification of mobile communication terminals;
15.
MAC address (Media Access Control Address): hardware address that is stored in a network card or a network adapter and that is used as the unique address at the level of OSI layer 2;
16.
PUK code (Personal Unblocking Key): unchangeable PIN assigned to the SIM used to unblock the SIM if the PIN code has been entered incorrectly on several occasions;
17.
PUK2-Code (Personal Unblocking Key 2): same as the PUK code, but assigned to the PIN2 code;
18.
NAT (Network Address Translation): procedure for translating network addresses. The address information in IP packages is automatically replaced with other address information by a network element (e.g. router);
19.
Source IP address:IP address that is assigned to the communication end point (normally the client) that establishes the connection;
20.
Port number: address of a port; a port is the logical end point for communications with or within a computer system. A port is linked to an IP address and the communication protocol type;
21.
Source port number: port number that is assigned to the communication end point (normally the client) that establishes the connection;
22.
Destination IP address: IP address that is assigned to the communication end point (normally the server) with which the connection is established;
23.
Destination port number: port number that is assigned to the communication end point (normally the server) with which the connection is established;
24.
SIP (Session Initiation Protocol):communication protocol that is used for signalling and maintaining multimedia communication sessions;
25.
SIP URI (SIP Uniform Resource Identifier): URI scheme for addressing the SIP. The SIP URI are addressing elements in the format user@domain.tld;
26.
IMPU (IP Multimedia Public Identity): in addition to the IMPI, a subscriber to the IMS has one or more IMPUs that are used to communicate with other subscribers. One IMPI may be assigned several IMPUs. Conversely an IMPU may also be shared with other subscribers;
27.
TEL URI (Telephone Uniform Resource Identifier): URI scheme for telephone numbers. The TEL URI are addressing elements in the format tel:number, e.g.tel:+41-868-868-868;
28.
IMPI (IP Multimedia Private Identity): globally unique identifier, assigned by providers to their subscribers, which is used inter alia for registration and AAA events. Every subscriber to IP Multimedia Subsystems (IMS) has an IMPI. The IMS is telecommunications system based on the internet protocol that integrates mobile voice services and internet functions;
29.
Alias address:additional email address that the subscriber can set up, change and delete at will. The email provider determines the maximum number of alias addresses and their structure. The alias addresses are linked to the email account. An email sent to an alias address is delivered to the same email box as used for the subscriber’s related main email address;
30.
Mailing list: list of email addresses, also known as a distribution list or distribution group. The list has its own email address. The messages that are sent to the mailing list address are forwarded on to the email addresses of its members;
31.
Messaging services:message transmitting services that are independent of from telephony and multimedia services. They include instant messaging, IMS messaging and messaging applications (apps) and SMS services from third-party providers (i.e. SMS services not provided by the subscriber’s TSP). These services may also include additional functions such as multimedia communication, data transmission and presence information (e.g. a subscriber can see the current status and potentially the location of the other subscribers);
32.
Cloud-services:derived communications services such as storage services and applications that are available online and hosted in data centres around the world depending on the need for resources;
33.
Proxy services:communication interface in a network. It works as an intermediary that accepts requests on one side in order to establish a connection via its own address with the other side. Proxy services are therefore relevant for the purposes of identification;
34.
Public WLAN access point: public wireless access point to a public telecommunications network that can be found both in public and in private spaces;
35.
CGI (Cell Global Identity): unmodified cell identifier in second and third generation mobile networks (2G and 3G) (see 3GPP TS 23.003, Clause 4.3.1);
36.
ECGI (E-UTRAN Cell Global Identity):unmodified cell identifier in fourth generation mobile networks (4G) (see 3GPP TS 23.003, Clause 19.6);
37.
SAI (Service Area Identity):unmodified identifier for a service area that is used in mobile networks for mobility management (see 3GPP TS 23.003, Clause 12.5);
38.
RAI (Routing Area Identity): unmodified identifier for a routing that is used in mobile networks for mobility Management related to packet-switched data transmission (see 3GPP TS 23.003, Clause 4.2);
39.
TAI (Tracking Area Identity):unmodified identifier for a tracking area that is used for mobility management in fourth generation mobile networks (see 3GPP TS 23.003, Clause 19.4.2.3);
40.
BSSID (Basic Service Set Identifier): unique identifier (MAC address) of the WLAN access point;
41.
Target ID: identifier under surveillance, i.e. the identifier of the target of the surveillance;
42.
AAA (authentication, authorisation and accounting) information:information on which subscribers are allowed to use which services and which is used to bill subscribers for service usage. For the purposes of this Ordinance, passwords are not regarded as AAA information. Authentication is the process by which a subscriber is identified before the access is granted. Authorisation determines which rights of access to resources or services that a subscriber holds and also guarantees access control. The subscriber’s use of resources is measured for accounting purposes;
43.
SMS (Short Message Service): messaging service for transmitting short text messages;
44.
Voice mail: storage devices used in telecommunication networks that offer answering services (e.g. receiving, forwarding and storing voice messages). There are also extensions for various types of media and services, such as SMS, email, fax or video messages as well as function extensions such as converting from one type of media to another and the sending of messages;
45.
RCS (Rich Communications Services): (originally: Rich Communication Suite) specification of the international industry organisation for mobile telephony providers (GSM Association, GSMA) for the IMS based provision of interoperable (i.e. cross-provider and cross-terminal) multimedia services with extended functional scope. Various types of media (e.g. language, music, photographs, videos) and services (e.g. chat, chat groups, calls, multimedia messages, short messages, instant messages, presence information, transmission of files, address books) can be combined; the RCS services are provided to subscribers by their mobile telephony provider;
46.
E.164 number: telephone number in accordance with international numbering plan E.164 of the ITU-T;
47.
DTMF (Dual-Tone Multi-Frequency): a signalling procedure, i.e. during a telephone conversation, signals can be sent by pressing the telephone keypad, for example to interact with answering machines or automatic voice response systems;
48.
MMS (Multimedia Messaging Service):messaging service for transmitting messages in different types of media (multimedia) in mobile networks.

Diese Seite ist durch reCAPTCHA geschützt und die Google Datenschutzrichtlinie und Nutzungsbedingungen gelten.

Feedback
Laden