Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4   5…   5A…   6…   7…   7A…   8…   9…   10…   11…   12…   12.2…   12.3…   12.4…   12.5…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…   B…   C…   D…   E…   F…   G…   H…   I…   J…   L…

 

17  Interception for Proximity Services |R12|

17.1  ProSe Direct Discovery

17.1.1  General

Proximity Service (ProSe) are specified in TS 23.303. This includes Direct Discovery where two UEs may discover that they are in proximity using direct signalling between the UEs, where such signalling both controlled by and reported to the ProSe Function.
[not reproduced yet]
Figure 17.1-1: ProSe Direct Discovery Intercept configuration
Up
Figure 17.1-1 shows the IRI interception configuration for ProSe Direct Discovery. The HI2 interface represents the interface between the LEA and the delivery function. The delivery function is used to distribute the Intercept Related Information (IRI) to the relevant LEA(s) via HI2. See Clause 4 for more information on the ADMF and other interfaces.
The target identity for ProSe Direct Discovery interception is the IMSI. The activation, deactivation, and interrogation of interception regarding the ProSe Function shall follow the requirements of Clause 5.
Up

17.1.2  Provision of Inteception of Call ContentWord‑p. 193
Interception of direct discovery does not have a call content component as all the information useful to the LEA is provided as part of the IRI interception.

17.1.3  Provision of Intercept Related Information

17.1.3.1  General

Figure 17.1.3.1-1 shows the transfer of intercept related information (IRI) to the DF2. If an event involving a target occurs, the ProSe Function shall send the relevant data to the DF2. A UE always contacts the ProSe Function in its HPLM, which then contacts the other relevant ProSe Functions to complete the UEs request.In the case of Match Report event, it is possible that a non-target monitoring UE will tigger interception of a target UE when it reports a code announced by that target UE.
This is illustrated in the following figure where it should be noted that only one subcriber to HPLMN ProSe Function interaction is needed to trigger an interception event.
[not reproduced yet]
Figure 17.1.3.1-1: Provision of Intercept Related Information for discovery
Up

17.1.3.2  X2-interface

The following information needs to be transferred from the ProSe Function to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI);
  • events and associated parameters, as defined in section 17.1.3.3;
The IRI should be sent to DF2 using a reliable transport mechanism.

17.1.3.3  ProSe LI Events and Event Information

17.1.3.3.1  ProSe LI Events
The following events are applicable to the interception of direct discovery:
  • Discovery Request
  • Match Report
Interception of these events is mandatory in the ProSe Function of the PLMN that is used for direct discovery.
17.1.3.3.2  ProSe LI Event InformationWord‑p. 194
A set of possible elements as shown below is used to generate the events.
Element
Description

Observed IMSI
IMSI of the target
Event type
Description which type of event is delivered:- Discovery Request, Match Report
Event date
Date of the event generation in the ProSe Function
Event time
Time of the event generation in the ProSe Function. Timestamp shall be generated relative to the ProSe Function internal clock.
Role of the target
Whether the target is an announcing or a monitoring UE
Discovery PLMN identity
PLMN used or to be used for the discovery
ProSe Application ID Name
Identity of a user within the context of a specific application
Metadata
Metadata relating to a ProSe Application ID Name of the announcing UE
Network Element Identifier
Unique identifier for the element reporting the ICE.
Timer
The "Validity Timer" or "Time to Live" value assigned by the network to a specific ProSe Application Code or Filter, that controls how long the UE can announce/monitor it
Identity of the other UE
In Match reports, there is a second UE involved.
ProSe Application Code
Bitstring that is actually announced over the air or included in a discovery filter applied by UE
ProSe App Mask
Bitmask that allows the monitoring UE to perform full or partial matching. Multiple Masks may be included in a Discovery Filter. The length of the mask is the same as the length of ProSe Application Code

Up
17.1.3.3.3  Structure of ProSe EventsWord‑p. 195
17.1.3.3.3.1  Discovery Request |R14|
For ProSe Discovery Requests, a Discovery Request event is generated. The elements shown in Table 17.1.3.3.1-1 will be delivered by the ProSe Function to the DF2, if available. A new Discovery Request Event shall be generated for each individual ProSe Discovery Request received by the ProSe Function.
Information Element

Observed IMSI
Event Type
Event Time
Event Date
Role of the target
Network Element Identifier
Discovery PLMN identity
ProSe Application ID Name
Timer
Metadata
(If Applicable)
ProSe Application Code
ProSe App Mask
(If Applicable)

Up
17.1.3.3.3.2  Match Report |R14|
For ProSe Match Report, a Match Report event is generated. The elements shown in Table 17.1.3.3.2-1 will be delivered by the ProSe Function to the DF2, if available. A new Match Report Event shall be generated for each individual ProSe Match Report received by the ProSe Function.
Information Element

Observed IMSI
Event Type
Event Time
Event Date
Role of the target
Network Element Identifier
Discovery PLMN identity
ProSe Application ID Name
Timer
Metadata
(If Applicable)
Identity of the other UE
(If Available)
ProSe Application Code

Up

17.2  ProSe One To Many Communications

17.2.1  General

Proximity Service (ProSe) are specified in TS 23.303. This includes one to many communications among Public Safety ProSe UEs with such communication occuring while the UEs are in proximity. There are several procedures that takes place with network elements as part of a typical one-to-many commuication. The UE needs to be authorised by the ProSe Function, and receive keys from the ProSe Key Management Function (PKMF - see TS 33.303, TS 23.228). After such a communication, the UE reports the relevant usage information to the ProSe Function. This subclause details the interception at the ProSe Function and ProSe Key Management Function.
Editor's note: Interception of ProSe one-to-many communication with the group as the target is FFS.
[not reproduced yet]
Figure 17.2-1: ProSe One To Many Communications Intercept configuration
Up
Figure 17.2-1 shows the IRI interception configuration for ProSe one to many communications. The HI2 interface represents the interface between the LEMF and the delivery function. The delivery function is used to distribute the Intercept Related Information (IRI) to the relevant LEMF(s) via HI2. See clause 4 for more information on the ADMF and other interfaces.
The target identity for interception is the IMSI. The activation, deactivation, and interrogation of interception regarding the ProSe Function shall follow the requirements of clause 5.
Up

17.2.2  Provision of Intercept Product - One-To-Many CommunicationsWord‑p. 196

17.2.2.1  General

Figure 17.2.2.1-1 shows the transfer of IRI relating to the one to many communications from the ProSe Function and ProSe Key Management Function to the DF2 and to the LEMF. If a target UE interacts with the ProSe Function or ProSe Key Management Function relating to one-to-many communications, a One-To-Many IRI event, is generated and sent via the Delivery Function 2 to the LEMF.
If an event involving an target occurs, the ProSe Function or ProSe Key Management Function shall send the relevant data to the DF2 for formatting and delivery to the LEMF.
[not reproduced yet]
Figure 17.2.2.1-1: Provision of Intercept Product for Public Safety One-To-Many Communications
Up

17.2.2.2  X2-interfaceWord‑p. 197
The following information needs to be transferred from the ProSe Function or ProSe Key Management Function to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI);
  • events and associated parameters, as defined in section 17.2.2.3;
  • the target location (if available) or the IAs in case of location dependent interception;
  • Quality of Service (QoS) identifier;
  • Encryption parameters (keys and associated parameters for decrypting CC), if available and necessary.
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

17.2.2.3  ProSe LI One-To-Many Events and Event Information

17.2.2.3.1  Overview of ProSe LI One-To-Many Events
The following event are applicable to the interception of one to many communications:
  • ProSe Function sends authorisation to perform one-To-many communications to the target UE.
  • ProSe Key Management Function sends keys to use in one-to-may commuications to the target UE.
  • ProSe Function receives a one-to-many communications usage information report from the target UE.
Interception of these events is mandatory.
17.2.2.3.2  Structure of ProSe LI One-To-Many Event Information |R13|
A set of possible elements as shown below is used to generate the events.
Element
Description

Observed IMSI
IMSI of the target
Event date
Date of the event generation.
Event time
Time of the event generation. Timestamp shall be generated relative to the intercepting node's internal clock.
PLMN Identity
The PLMN that the UE is being authorised to perform one-to-many communication in.
Sender ID
Identifies the sender of the One-To-Many Communications - also known as the ProSe UE ID or the Group member identity.
ProSe Layer-2 Group ID
Identifies the group of the One-To-Many Communications - also known as the destination ID.
Network Identifier
Operator ID plus unique identifier for the element reporting the ICE.
IP address type
The type of IP address, i.e IPv4 or IPv6, used for this one-to-many communication.
IP multicast address
The IP address to be used when doing one-to-many communication
PKMF address
The IP address of the ProSe Key Management Function that will provides keys for this one-to-may communication
Source IP address
The IP source address to be used by the UE as a source address
Communication Authorisation Validity timer
Indicates in minutes how long the authorisation is valid for
Confidentiality algorithm
The confidentiality algorithm used with this group
PGK
ProSe Group Key that can be used to protect data for this group
PGK ID
The identity of the PGK within this group
PGK lifetime
The lifetime of the PGK
Location list
List of locations of the UE when in coverage and the corresponding timestamps
E-UTRAN coverage timestamps
List of timestamps when the UE goes in/out of E-UTRAN coverage
First communication timestamp
Timestamp of the first one-to-may communication transmission/reception
Transmitter identities
Identities of the transmitters in the one-to-many communication session
Data transmitted in coverage
List of amount of data transmitted by UE when in E-UTRAN coverage at each location, with ECGI and the corresponding timestamps
Data transmitted out of coverage
List of amount of data transmitted by UE for each E-UTRAN out of coverage and the corresponding timestamps
Data received in coverage
List of amount of data received by UE when in E-UTRAN coverage at each location, with ECGI and the corresponding timestamps
Data received out of coverage
List of amount of data received by UE for each out of E-UTRAN coverage period and the corresponding timestamps

Up
17.2.2.3.3  ProSe LI One-To-Many EventsWord‑p. 199
If ProSe Function sends authorisation to use ProSe one-to-many communication to the target UE, a One-To-Many-Auth Event shall be generated. These elements if available will be delivered to the DF2 (see TS 24.333 for more information on the elements):
Information Element

Observed IMSI
Event type
Event Time
Event Date
Network Identifier (including network element identifier)
PLMN Identity
Communication Authorisation Validity timer
ProSe Layer-2 Group ID
IP address type
IP multicast address
PKMF address (if applicable)
Source IP address (if applicable)

If a ProSe Key Management Function sends keys for one-to-many communication to a target UE, a One-To-Many-Keys Event shall be generated. These elements if available will be delivered to the DF2 (see TS 33.303 for more information on the elements):
Information Element

Observed IMSI
Event type
Event Time
Event Date
Network Identifier (including network element identifier)
ProSe Layer-2 Group ID
Sender ID
Confidentiality algorithm
PGK
PGK ID
PGK lifetime

If a ProSe Function receives a usage information report for ProSe one-to-many communication to a ProSe Function from a target UE, a One-To-Many-Usage Event shall be generated. These elements if available will be delivered to the DF2 (see TS 32.277 for more information on the elements):
Information Element

Observed IMSI
Event type
Event Time
Event Date
Network Identifier (including network element identifier)
Location list
E-UTRAN coverage timestamps
Sender ID
ProSe Layer-2 Group ID
IP address type
IP multicast address
Source IP address (if applicable)
First communication timestamp
Transmitter identities
Data transmitted in coverage
Data transmitted out of coverage
Data received in coverage
Data received out of coverage

Editor's note: The above table is based on the stage 2 of the PC3ch interface as decribed in TS 32.277. Some of the above information may need to be changed once the stage 3 for PC3ch is complete.
Editor's note: The application of LI requirements in TS 33.106 to the CTF (TS 32.277) within the ProSe function when it is physically separated from the ProSe Function is FFS.
Up

17.3  ProSe Remote UE Communications |R13|Word‑p. 200

17.3.1  General

A ProSe Remote UE can initiate communications via a ProSe UE-to-NW Relay and the core network as described in TS 23.303.
From LI perspective, the following scenarios can be identified:
  1. The ProSe Remote UE is a target for interception
  2. The ProSe UE-to-NW Relay is a target for interception
  3. Both the ProSe Remote UE and the ProSe UE-to-NW Relay are target for interception.
In the following subclauses, scenarios 1 and 2 are addressed, scenario 3 is covered by using both scenario 1 and 2.
Interception in the PDN-GW is a national option.
Up

17.3.2  The ProSe Remote UE is a target for interception

When a ProSe Remote UE connects to the ProSe UE-to-NW Relay, the core network (MME, S-GW, PDN-GW) receives the related information from the ProSe UE-to-NW Relay. If the ProSe Remote UE is a target, a ProSe Remote UE start of communication event shall be generated by the S-GW, PDN-GW.
If the warrant requires to intercept also CC, considering that the PDN connection used by the ProSe UE-to-NW Relay can be used also for other, non-target, ProSe Remote UEs, the S-GW/PDN-GW shall isolate the target ProSe remote UE's communication from any content of communication not associated to the remote UE under interception. CC related to the target ProSe Remote UE shall be sent over X3 interface.
When a target ProSe Remote UE disconnects from the ProSe UE-to-NW Relay, a ProSe Remote UE end of communication event shall be generated by the S-GW, PDN-GW. CC interception for the target ProSe Remote UE shall be stopped.
In both cases of connection and disconnection of a target ProSe Remote UE, the MME shall generate a ProSe Remote UE Report event.
In case the whole PDN connection used by the ProSe UE-to-NW Relay is closed for any reason while a target Remote UE is connected to the ProSe UE-to-NW relay, a ProSe Remote UE end of communication event shall be generated by the S-GW/PDN-GW and sent to the DF2.
If interception is started after that the ProSe remote UE is already connected to the network through a ProSe UE-to-NW Relay, a Start of interception with ProSe Remote UE ongoing communication event shall be provided by the S-GW/PDN-GW. The same event shall also be sent by the new S-GW in case, due to ProSe UE-to-NW Relay mobility, there is a change of S-GW. The ICEs shall than start intercepting the target UEs communication by extracting it from the PDN connection used by the ProSe UE-to-NW Relay UE.
Up

17.3.3  The ProSe UE-to-NW Relay is a target for interceptionWord‑p. 201
The ProSe UE-to-NW Relay uses one or more PDN connections for any activity/communication which is not related to relaying. In such case all the requirements specified for EPS interception in clause 12 apply. In addition, IRIs related specified in clause 12 are also applicable to the PDN connection used for relay.
This clause specifies additional functional requirements which are applicable to the PDN connection(s) established by the ProSe UE-to-NW Relay.
PDN connection(s) used for relaying only carry communications for the ProSe remote UEs. So, unless any of them is also a target for interception (for which clause 17.3.2 apply), no content of communication shall be intercepted from such PDN connection(s), unless required by national regulation, in which case all requirements specified in clause 12 apply also to these PDN connection(s).
In case ProSe remote UEs are connected to or disconnected from the target ProSe UE-to-NW Relay, the ICEs (MME, S-GW, PDN-GW) shall provide a ProSe Remote UE Report event, including the identities and IP info of ProSe remote UE(s) being connected/ disconnected.
In case interception is activated for a ProSe UE-to-NW Relay with already connected ProSe remote UE(s), the ICEs shall provide a Start of interception for ProSeUE-to-NW Relay, including the identities and IP info of ProSe remote UEs already connected to the relay. The same event shall also be sent by the new S-GW in case, due to ProSe UE-to-NW Relay mobility, there is a change of S-GW.
In case a Tracking Area/EPS Location Update event is provided for a target ProSe UE-to-NW Relay, it shall carry also information related to the connected ProSe remote UE(s).
Up

17.3.4  X2-interface

The following information needs to be transferred from the EPS nodes (MME, S-GW, PDN-GW) to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI, MSISDN, IMEI);
  • events and associated parameters as defined in clause 17.3.4.1.

17.3.4.1  Structure of the events

There are several different events in which the information is sent to the DF2 if this is required. Details are described in the following clauses. The events for interception are configurable (if they are sent to DF2) in the EPC nodes.
The following event is applicable to the MME:
  • ProSe Remote UE Report;
The following events are applicable to the S-GW and PDN-GW:
  • ProSe Remote UE start of communication;
  • ProSe Remote UE end of communication;
  • Start of interception with ProSe Remote UE ongoing communication;
  • Start of interception for ProSe UE-to-NW Relay.
A set of possible elements as shown below is used to generate the events.
Element
Description

Observed MSISDN
MSISDN of the target
Observed IMSI
IMSI of the target
Observed IMEI
IMEI of the target
Event type
Indicates which type of event is delivered: ProSe Remote UE Report, ProSe Remote UE start of communication, ProSe Remote UE end of communication, Start of interception with ProSe Remote UE ongoing communication, Start of interception for ProSe UE-to-NW Relay.
Event date
Date of the event generation in the ICE
Event time
Time of the event generation in the ICE. Timestamp shall be generated relative to the ICE internal clock.
Target type
Indicates whether the target is a ProSe Remote UE or a ProSe UE-to-NW Relay
ProSe Remote UE IDs
The identities of the connected or disconnected ProSe remote UEs.
ProSe Remote UE IP info
The IP address(es) of the connected or disconnected ProSe Remote UE(s) provided by the ProSe UE-to-NW Relay.
APN
The Access Point Name used by the ProSe UE-to-NW Relay for the connection
MSISDN of the Prose UE-to-NW Relay
(only applicable when the ProSe Remote UE is the target)
IMSI of the Prose UE-to-NW Relay
(only applicable when the ProSe Remote UE is the target)
IMEI of the Prose UE-to-NW Relay
(only applicable when the ProSe Remote UE is the target)
PDN address(es)
The ProSe UE-to-NW Relay IP address(es) for the PDN connection.
Network Element Identifier
Unique identifier for the element reporting the ICE.
Correlation number
The correlation number is used to correlate CC and IRI (in case the target is a ProSe remote UE) or IRIs (in case the target is a ProSe UE-to-NW Relay).
Location information
The location of the ProSe UE-to-NW Relay.
National regulations may require to provide the E-CGI of the ProSe UE-to-NW Relay when the target is the ProSe Remote UE.

Up

17.3.5  ProSe UE-to-NW Relay eventsWord‑p. 202

17.3.5.1  ProSe Remote UE Report

This event shall be sent by the MME, S-GW and PDN-GW when the node detects that a ProSe Remote UE has been connected to or disconnected from the ProSe UE-to-NW Relay and the ProSe Remote UE or the ProSe UE-to-NW Relay is a target for interception. The following parameters shall be provided if available.
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Target type
  • ProSe Remote UE(s) connected IDs
  • ProSe Remote UE(s) connected IP info
  • ProSe Remote UE(s) disconnected IDs
  • ProSe Remote UE(s) disconnected IP info
  • MSISDN of the Prose UE-to-NW Relay
  • IMSI of the Prose UE-to-NW Relay
  • IMEI of the Prose UE-to-NW Relay
  • APN
  • PDN Address(es)
  • Location information
Up

17.3.5.2  ProSe Remote UE Start of CommunicationWord‑p. 203
This event shall be sent by the S-GW and PDN-GW when the node detects that a target ProSe Remote UE has been connected to a ProSe UE-to-NW Relay. The following parameters shall be provided if available.
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Correlation number
  • MSISDN of the Prose UE-to-NW Relay
  • IMSI of the Prose UE-to-NW Relay
  • IMEI of the Prose UE-to-NW Relay
  • APN
  • PDN Address(es)
  • Location information

17.3.5.3  ProSe Remote UE End of Communication

This event shall be sent by the S-GW and PDN-GW when the node detects that a target ProSe Remote UE has been disconnected from a ProSe UE-to-NW Relay. The event shall also be sent in case the PDN connection used for relay used by the target ProSe remote UE is closed. The following parameters shall be provided if available.
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Correlation number
  • Location information

17.3.5.4  Start of interception with ProSe Remote UE ongoing communication

This event shall be sent by the S-GW and PDN-GW when interception is started for a ProSe Remote UE which is already connected to a ProSe UE-to-NW Relay. The event shall also be sent by the new S-GW in case, due to ProSe UE-to-NW Relay mobility, there is a S-GW change. The following parameters shall be provided if available.
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Correlation number
  • MSISDN of the Prose UE-to-NW Relay
  • IMSI of the Prose UE-to-NW Relay
  • IMEI of the Prose UE-to-NW Relay
  • APN
  • PDN Address(es)
  • Location information
Up

17.3.5.5  Start of interception for ProSe UE-to-NW RelayWord‑p. 204
This event shall be sent by the S-GW and PDN-GW when interception is started on a UE which is already acting as ProSe UE-to-NW Relay for any Remote UE. The event shall also be sent by the new S-GW in case, due to ProSe UE-to-NW Relay mobility, there is a S-GW change. The following parameters shall be provided if available.
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Target type
  • ProSe Remote UE(s) connected IDs
  • ProSe Remote UE(s) connected IP info
  • APN
  • PDN Address(es)
  • Location information
Up

17.3.6  X3-interface

Functional requirements specified in clause 12.3.2 are applicable. Interception of CC is subjected to conditions specified in clauses 17.3.2 and 17.3.3.


Up   Top   ToC