Projet 2a
Consultation 2017/22: Projets d'ordonnances pour la mise en œuvre de la nouvelle loi fédérale sur la surveillance de la correspondance par poste et télécommunication · 194 pages
Fedlex · Projet · Page 161Fedlex · Projet
Technical requirements for the handover interfaces for the execution of telecommunications surveillance
8.4.1.10 Network access: Network access translation information response elements and structure
This section covers the information response elements and fields of the Network access subscriber records according to ETSI TS 102 657 V1.17.1 Annex E.
Network access Service Usage Element or Description Example attribute
recordNumber Structure 0, 1, 2, ...
recordPayload structure
networkAccess Service = networkAccess
naServiceUsage Category = naServiceUsage
naServiceUsage structure
privateIPAddress Source IP address before the NAT
instance.
IPAddress CHOICE
iPTextAddress The private IP address of the host. 192.168.0.24
privatePort The source port before the NAT25871
instance.
publicIPAddress Source IP address after the NAT
instance.
IPAddress CHOICE
iPTextAddress The translated IP address of the 203.0.113.45
host, i.e. the address known by the
remote host in text format.
publicPort Source port after the NAT instance.
singlePort The translated port of the host.32658
Depending on the Network Address Translation instance configuration and capabilties, either the "privateIPAddress" and "privatePort" before the NAT instance or the "publicIPAddress" and "publicPort" after the NAT instance shall be reported.
8.4.2 Multimedia and telephony information requests and responses
The encoding and formats of the parameters for the network access information requests and responses relate to ETSI TS 102 657 V1.17.1 Annexes A and B and D.
8.4.2.1 Multimedia and telephony: subscription information request criteria elements and structure
This section covers the request criteria contained in the requestParameters
RequestConstraints sequence sent in the XML request for the telephony and multimedia subscription information. It uses the "multmediaSubscriber" structure as telephony is considered as a subset of multimedia services.
Multimedia Subscriber Element or attribute Description Example
equals Request constraint