17 Interception of PTC
33.1083G Security3GPPHandover interface for Lawful Interception (LI)Release 17TS
17.1 Capabilities when the PTC service is supported by a CSP
17.1.0 Introduction
The capabilities defined in this clause apply when the Push to Talk over Cellular (PTC) service is supported by a CSP. The term PTC, when used in the present document, represents either a Push to talk Over Cellular (PoC) or Mission Critical Push To Talk (MCPTT) type service. PoC and MCPTT, which use similar architectures for service delivery, shall be intercepted and delivered separated from the interception of all other services for LI purposes.
This clause applies to the PTC services identified in Clause 21 of TS 33.107 [19].
When PTC events are detected the CSP shall be able to use existing intercept capabilities defined in this specification but isolatable to only deliver PTC events when specified by a lawful authorization. TS 33.107 [19] defines the PTC events to be reported. This clause will identify the set of event Records that are to be sent from the DF to the LEMF based on capabilities that already exist in this specification.
The network nodes, involved in providing the interception of PTC services, shall be determined based on the deployment configuration and the particular PTC type service scenarios.
When lawfully authorized, Law Enforcement requires access to CC and IRI for the events pertaining to the target’s authorization, access to, and use of PTC services, independent of the deployed service architecture. This includes where the communications between the target and associates are sent and received over separate channels, or may be accessed at different Intercept Control Elements (ICE) at different geographical locations in the service provider’s network.
17.1.1 Lawful interception identifier
For each target identity related to an interception measure, the authorized CSP shall assign a special Lawful Interception Identifier (LIID), which has been agreed between the LEA and the CSP.
Using an indirect identification, pointing to a target identity makes it easier to keep the knowledge about a specific target limited within the authorized CSP and the handling agents at the LEA.
The LIID is a component of the CC delivery procedure and of the IRI records. It shall be used within any information exchanged at the handover interfaces HI2 and HI3 for identification and correlation purposes.
The LIID format shall consist of alphanumeric characters. It might for example, among other information, contain a lawful authorization reference number, and the date, when the lawful authorization was issued.
The authorized CSP shall either enter a unique LIID for each target identity of the target or a single LIID for multiple target identities all pertaining to the same target.
If more than one LEA intercepts the same target identity, there shall be unique LIIDs assigned relating to each LEA.
17.1.2 Network identifier
The network identifier (NID) is a mandatory parameter; it should be internationally unique. It consists of the following two identifiers.
1) CSP identifier (mandatory):
Unique identification of the CSP.
2) Network Element IDentifier NEID (mandatory):
The purpose of the network element identifier is to uniquely identify the relevant network element carrying out the LI operations, such as LI activation, IRI record sending, etc.
A network element identifier may be an IP address or other identifier.
17.1.3 PTC IRI Events
Intercept Related Information (IRI) events are necessary at the PTC Mobile Station Attach, PTC Mobile Station Detach, PTC session Activation, Start of intercept with PTC context active, PTC Context Deactivation, PTC Serving System, and other PTC events that are defined in this clause.
TS 33.107 [19] Figure 21.1.1 shows the transfer of intercept related information to the DF2. If an event for / from a PTC MS occurs, the Shared XDMS/PTC common core servers or the Home Subscriber Service (HSS) sends the relevant data to the DF2 for delivery to the LEA.
The following report records shall be mapped to appropriate records that are sent by DF2 to the LEMF:
– PTC IRI defined events as applicable to both PoC and MCPTT service as defined in [19] (21.3.3.1).
– In addition, this clause also specifies IRI reporting from the HSS handling subscriber data. Target identities to be used for interception of IRI at the HSS are specified in TS 33.107 [19]:
– Serving System;
– Cancel location;
– Register location;
– Location information request.
– The following events are applicable to the SIP Core:
– Service Registration
The above REPORT Records and those in clause 17.2 shall be reported from DF2 to the LEMF independent of any other services that may or may not be intercepted.
17.1.4 CC for PTC-based VoIP
The CSP shall report Communication Content (CC) for all talk burst in a target’s PTC session, when authorized. The CC ICE has to intercept all PTC session content (i.e., talk burst) between the PTC LI target and associate(s) and deliver the PTC session content to the LEMF. The CSP shall deliver CC for the duration of all of the different types of PTC sessions (e.g. Pre-arranged PTC group, PTC Chat group, One-to-One, and other type group calls) that are originated by or terminated at the PTC target’s MS, facilities, or service when authorized. PTC communications are based on SIP/IP signalling within the CSP core and PTC client as per [97]. The PTC CC shall use the provisions in B.12 Contents of Communication (HI3 IMS-based VoIP) to provide PTC CC to the LEMF.
Annex B.12 provides the definitions of the data structures to be used for the delivery of CC for IMS-based VoIP (see Annex K for the detailed description). The Correlation Number received from the CC Intercept Triggering Function shall be used in the CC Data sent over the HI3.
17.1.5 IRI for PTC based Communications
The IRI event information sent to the DF2/DF3 is triggered by different PTC session related and non-call related events/reports. A set of information is used to generate the IRI records. The records used transmit the information from mediation function to LEMF. The following table gives the mapping between information received per event or report and information sent in records.
Table 17.1.5: Mapping between Events information and IRI information
|
Parameter |
Definition |
ASN.1 parameter |
|---|---|---|
|
Abandon Cause |
Identifies the reason for the abandoned PTC Session. |
abandonCause |
|
Access Policy Failure |
Reports the error code or reason for failure when Access Policy Request is unsuccessful. |
accessPolicyFailure |
|
Access Policy Type |
Identifies the type of access policy list being managed or queried by the PTC Intercept target. |
accessPolicyType |
|
Alert indicator |
Indicates an emergency alert condition was sent, received or cancelled. |
alertIndicator |
|
Associate Presence Status |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. – PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
associatePresenceStatus |
|
Bearer Capability |
Provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
bearer-capability |
|
Broadcast Indicator |
Indicates that this was a broadcast destined for the group |
broadcastIndicator |
|
Contact Identity |
Identity of the contact in the list, one contact per Contact List or Group List |
contactID |
|
Correlation |
Uniquely identifies the PTC Session, and correlates related CII as well as related CII and CC. |
correlation |
|
Event Type |
Description of which PTC type of event is delivered: Session Initiation, Session Abandon, Session Start, session end, Registration, Serving system, Start of Interception, Pre-Established Session, Instant Personal Alert, Party Join Party Drop, Party Hold, Party Retrieve, Media Modification, Group Advertisement, Floor Control, Target Presence, Associate Presence, List Management Events, Access Policy event, Media Type Notification, Encryption Parameters, Group Call Request, Group Call Cancel, Group Call Response, Group Call Interrogate, MCPTT Imminent Peril Group Call, Communication Content. |
eventType |
|
Parameter |
Definition |
ASN.1 parameter |
|
|---|---|---|---|
|
Failure Code |
The reason or code for the failure or closing of the session. |
failureCode |
|
|
Floor Activity |
The type of request granted e.g. TBCP request, TBCP deny, TBCP release etc. |
floorActivity |
|
|
Floor Speaker Identity |
Identification of the PTC Client that has been given the floor.] |
floorSpeakerID |
|
|
GroupAuthRule |
Identifies the action requested by the PTC Target to the PTC Group Authorization Rules: – Report when action requested to the PTC Group Authorization Rules by the target – Report when the PTC Target attempts a change or queries the Access Control List(s). |
groupAuthRule |
|
|
Group Ad Sender |
Identifies the group administrator who was the originator of the group call. |
groupAdSender |
|
|
Group Characteristics |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
groupCharacteristics |
|
|
Hold Retrieve Indication |
Shall indicate the PTC Session is put on hold ((deactivate Media Bursts) a PTC Session is locked for talking/listening)) or released from hold. True indication equals placed on hold, false indication was retrieved from hold. |
holdRetrieveInd |
|
|
Imminent Peril Indicator |
Indicates that the PTC call is an imminent peril notification and indicates what the imminent peril level is set to. |
imminentPerilInd |
|
|
Implicit Floor Request |
Indicates the client who has request the floor. |
implicitFloorReq |
|
|
Initiation Cause |
Shall identify the originator of the PTC Session Initiation. If an associate was the originator, the associate’s id shall be included, if known. |
initiationCause |
|
|
IPA Party Identity |
Identifies the PTC associate that receives or has sent the Instant Personal Alert to the target. |
iPAPartyID |
|
|
Lawful Interception Identifier |
Unique number for each lawful authorization. |
lawfulInterceptionIdentifer (LIID) |
|
|
List Management Action – |
Identifies the action requested by the target to the Contact Lists (i.e., individuals) or Group Lists. |
listManagementAction |
|
|
List Management Failure |
Reports the error code or reason for failure. |
listManagementFailure |
|
|
List Management Type |
Identifies the specific PTC Group lists accessed by the target or the Intercept target’s PTC Client of changes made to their PTC-specific documents stored in the network: ContactListManagementAttempt or GroupListManagementAttempt, and ContactListManagementResult or GroupListManagementResult and Whether the request was a success or failure. |
listManagementType |
|
|
Parameter |
Definition |
ASN.1 parameter |
|---|---|---|
|
Location |
Identifies the location of the target. Shall include when reporting of the PTC Intercept Target’s location information is authorized. |
location |
|
MCPTT Group Identity |
Identifies the Mission Critical Push To Talk group Identity |
mCPTTGroupID |
|
MCPTT ID |
MCPTT Identity, if available. |
mCPTTID |
|
MCPTT indicator |
Indicates direction of the emergency state, or condition, as either from the MCPPT target or from a MCPTT group to the target. |
mCPTTInd |
|
MCPTT Organization Name |
Include the name of the organization that the MCPTT device belongs to, if known. |
mCPTTOrganizationName |
|
MediaStream Availability |
Indicates if the PTC intercept target’s PTC Client is not able/willing to receive media streams immediately. Provide when Pre-established session is established. |
mediaStreamAvail |
|
Network Identifier |
Unique identifier for the network element reporting the event |
network-Identifier |
|
Observed IMPU |
Observed IMS Public User identity (IMPU) of the target. |
partyInformation/partyIdentity |
|
Observed IMPI |
Observed IMS Private User identity (IMPI) of the target. |
partyInformation/partyIdentity |
|
Pre Established Session ID |
Identifies PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
preEstSessionID |
|
Pre Established Status |
Indicates if the Pre Established Session is established (setup completed), modified, or released. |
preEstStatus |
|
Priority Level |
If more than one level of priority is supported, indicates the Talk Burst priority level of the PTC Client (OMA-PoC-AD [97]). |
priority_Level |
|
PTC CC Payload |
Includes the intercepted TALK Burst communication encapsulated in the RTP packets with media specific RTP payload formats. The PTC Payload shall contain the media at the network layer (i.e., the RTP/UDP/IP datagrams for a PTC service). |
pTCPayload |
|
PTC Group ID |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
pTCGroupID |
|
PTC Host |
Identifies the PTC participant who has the authority to initiate and administrate an PTC Session, provide if known. |
pTCHost |
|
PTC ID List |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
pTCIDList |
|
PTC Media Capability |
Identify the type of codec(s) and Media Parameters selected by the PTC Server from those contained in the original SDP offer from the PTC Target’s PTC Client. |
pTCMediaCapability |
|
PTC Originating Identity |
Shall include to Identify the originating party, when known. |
pTCOriginatingId |
|
PTC Other |
Other information that is required to decrypt the data. |
pTCOther |
|
PTC Participants |
Shall Identify all known individual PTC participants. |
pTCParticipants |
|
Parameter |
Definition |
ASN.1 parameter |
|---|---|---|
|
PTC Party |
The identity of the PTC associate who Joined a session, Dropped from a session, placed on hold, retrieved from hold, to include the identity of an MCPPT type emergency/imminent group/peril PTC associate of the Target. |
pTCParty |
|
PTC Party Drop |
Shall provide the identity of the associate that leaves the PTC Session |
pTCPartyDrop |
|
PTC Server URI |
Shall include the identity of the PTC server serving the target or the server the target is a participant of, if known. |
pTCServerURI |
|
PTC Session Info |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
pTCSessionInfo |
|
PTC User Access Policy |
Identifies the action requested by the PTC Target to the PTC user or group access policy. |
pTCUserAccessPolicy |
|
Registration Request |
Identifies the type of registration request (e.g. register, re register, de register). |
registrationRequest |
|
Registration Outcome |
Identifies success or failure of registration and the failure reason. |
registrationOutcome |
|
Retrieve Identity |
Identifies the PTC Subscriber that retrieved from hold an on-going PTC Session. |
retrieveID |
|
RTP Setting |
The IP address and port number at the PTC Server for the RTP Session. |
rTPSetting |
|
Serving system identifier |
VPLMN ID of the serving system or of the third party network interworking, included in the Diameter AVP message with the HSS. |
serving-System-Identifier |
|
SDP |
Identifies the SDP media format and any extra information that is needed for a SDP Answer, SDP offer and SDP parameter negotiations. |
sdpOffer sdpAnswer |
|
Target Presence Status |
Shall identify any PTC related presence information of the PTC target, if changed. |
targetPresenceStatus |
NOTE: LIID parameter has to be present in each record sent to the LEMF.
17.2 PTC Event Records
17.2.0 Introduction
PTC event records defined below are applicable for both types of service that may be provided by the CSP e.g. PoC or MCPTT.
17.2.1 PTC Registration
The PTC Registration Report Record shall be reported by the MF/DF to the LEMF when the target registers, re-registers, or deregisters for a PTC service, regardless of whether it is successful or unsuccessful.
Table 17.2.1: PTC Registration Report Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate registration event. |
|
LIID |
M |
Unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCServerURI |
C |
Shall include the identity of the PTC server serving the target or the server the target is a participant of, if known. |
|
RegistrationRequest |
M |
Identifies the type of registration request (register, re‑register, or de-register). |
|
RegistrationOutcome |
M |
Identifies success or failure of registration and the failure reason. |
17.2.2 PTC Start of Interception
The PTC Start of Interception Begin Record shall be reported by the MF/DF to the LEMF for two separate conditions. The first reporting of a PTC Start of Interception Begin Record is for a PTC session that has been initiated but has not been established, either from/to the target. The second conditional reporting of a PTC Start of Interception Begin Record shall be reported when LI is first started and the PTC target has at least one PTC Session active in progress. If multiple PTC Sessions are active at the start of the interception, a PTC Start of Interception Record is generated for each active PTC Session and sent to the LEMF. The PTC Start of Interception Begin Record is not reported for an Instant Personal Alert type of PTC Session.
Table 17.2.2: PTC Start of Interception Begin Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
Shall indicate a Start of Interception Begin Record event. |
|
|
LIID |
Shall include a unique number for each lawful authorization. |
|
|
TimeStamp |
Shall include the Time and date of the event generation. |
|
|
Network Identifier |
Unique identifier for the network element reporting the event. |
|
|
Correlation |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
|
PreEstSessionID |
C |
For a PTC Pre-Established Session, shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCOriginatingId |
C |
Shall include to Identify the originating party, when known. |
|
PTCSessionInfo |
C |
When not associated with a Pre-Established session, shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCHost |
C |
Shall identify the PTC participant who has the authority to initiate and administrate a PTC Session, if known. |
|
PTCParticipants |
M |
Shall Identify all known individual PTC participants. |
|
MediaStreamAvail |
C |
Shall include for a Pre-established session to indicate if the PTC intercept target’s PTC Client is not able/willing to receive media streams immediately, when the Pre-established session is established. |
|
Bearer-Capability |
C |
Shall provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
17.2.3 PTC Serving System
A PTC Serving System Report Record shall be reported by the MF/DF to the LEMF when there is a change to the CSP serving the PTC target access network (i.e. for mobility).
Table 17.2.3: PTC Serving System Report Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Serving System Report Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
serving-System-Identifier |
M |
Shall include the identity of the serving system currently serving the Target. |
17.2.4 PTC Session Initiation
A PTC Session Initiation Begin Record shall be reported by the MF/DF to the LEMF when the target initiates a session or the target receives an invitation to join a session regardless of the success or the final disposition of the invitation.
Table 17.2.4: PTC Session Initiation Begin Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Session Initiation Begin Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCServerURI |
C |
Shall include the identity of the PTC server serving the target or the server the target is a participant of, if known. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCOriginatingID |
C |
Shall identify the originating party. Provided when known. |
|
PTCParticipants |
C |
Shall identify the individual PTC participants, when known. |
|
AssociatePresenceStatus |
C |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. – PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
|
InitiationCause |
M |
Shall identify the originator of the PTC Session Initiation. If an associate was the originator, the associate’s id shall be included, if known. |
|
Bearer-Capability |
C |
Shall provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
|
PTCHost |
C |
Shall identify the PTC participant who has the authority to initiate and administrate a PTC Session, if known. |
17.2.5 PTC Session Abandon End Record
The PTC Session Abandon End Record shall be reported by the MF/DF to the LEMF when the PTC Session is not established and the request is abandoned before the PTC Session established end to end connectivity.
Table 17.2.5: PTC Session Abandon End Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Session Abandon End Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
|
AbandonCause |
M |
Shall identify the reason for the abandoned PTC Session. |
17.2.6 PTC Session Start Continue Record
A PTC Session (e.g. One-to-One, One-to-Many, or One-to-Many-to-One) Start Continue Record shall be reported by the MF/DF to the LEMF when a PTC Session is established, and communication begins.
Table 17.2.6: PTC Session Start Continue Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Session Start Continue Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCServerURI |
C |
Shall include the identity of the PTC server serving the target or the server the target is a participant of, if known. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCOriginatingID |
C |
Shall identify the originating party. Provide when known. |
|
PTCParticipants |
C |
Shall identify the individual PTC participants, when known. |
|
AssociatePresenceStatus |
C |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. – PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
|
initiationCause |
C |
Shall identify the originator of the PTC Session Initiation. If an associate was the originator, the associate’s id shall be included, if known. |
|
PTCHost |
C |
Shall identify the PTC participant who has the authority to initiate and administrate a PTC Session, if known. |
|
Bearer-Capability |
C |
Shall provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
17.2.7 PTC Session End Record
The PTC Session End Report Record shall be reported by the MF/DF to the LEMF when the PTC Session is released for any reason (i.e. normal or abnormal release) and voice communications ends.
Table 17.2.7: PTC Session End Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Session End Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCServerURI |
C |
Shall include the identity of the PTC server serving the target or the server the target is a participant of, if known. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PreEstStatus |
C |
When a Pre-Established Session is used for a PTC session being released, shall indicate a Pre-Established Session remains established or released. |
|
PTCOriginatingID |
C |
Shall identify the originating party. Provide when known. |
|
PTCParticipants |
C |
Shall identify the individual PTC participants, when known. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
|
AbandonCause |
M |
Shall identify the reason for the abandoned PTC Session. |
17.2.8 PTC Instant Personal Alert
The PTC Instant Personal Alert Report Record shall be sent from the MF/DF to the LEMF when an Instant Personal Alert (IPA) (i.e. a request for one PTC subscriber to initiate a one-to-one PTC Session) is initiated or sent to the PTC target.
Table 17.2.8: PTC Instant Personal Alert Report Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate an Instant Personal Alert Report Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
IPAPartyID |
M |
Identifies the PTC associate that receives or has sent the Instant Personal Alert to the target. |
|
IPADirection |
M |
Identifies the direction (TO PTC Target or FROM a PTC Target) of the Instant Personal Alert. |
17.2.9 PTC Party Join
The Party Join Continue Record shall be sent from the MF/DF to the LEMF when a request to join (or re-joins) a PTC Group Session (i.e. Chat Group) that is already in progress is received from the PTC target.
Table 17.2.9: PTC Party Join Continue Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Party Join Continue Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
IPAPartyID |
M |
Identifies the PTC associate that receives or has sent the Instant Personal Alert to the target. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCParticipants |
C |
Shall Identify all known individual PTC participants, if known. |
|
AssociatePresenceStatus |
C |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
|
MediaStreamAvail |
C |
Shall include for a session to indicate if the PTC intercept target’s PTC Client is not able/willing to receive media streams immediately, when the session is established. |
|
Bearer-Capability |
C |
Shall provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
17.2.10 PTC Party Drop
The Party Join Continue Record shall be sent from the MF/DF to the LEMF when an associate leaves the PTC Group Session in which the PTC target is also participating.
Table 17.2.10: PTC Party Drop Continue Record
|
Parameter |
MOC |
Description/Conditions |
||
|
observed IMPI |
M |
Provide at least one and others when available. |
||
|
observed IMPU |
||||
|
observed IPv4/IPv6 Address |
||||
|
observed MCPPTID |
||||
|
EventType |
M |
Shall indicate a Party Drop Continue Record event. |
||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
||
|
PTCPartyDrop |
M |
Shall provide the identity of the associate that leaves the PTC Session. |
||
|
AssociatePresenceStatus |
C |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
||
17.2.11 PTC Party Hold-Retrieve Record
A PTC Party Hold Continue Record shall be sent from the MF/DF to the LEMF when an on-going PTC Session with the target is placed on hold or retrieved from hold.
Table 17.2.11: PTC Party Hold Continue Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Party Hold Continue Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
PTCParticipants |
C |
Shall Identify all known individual PTC participants, if known. |
|
PTCParty |
M |
The identity of the PTC associate that placed the PTC session on hold. |
|
RetrieveID |
M |
Identifies the PTC associate that retrieved from hold an on-going PTC Session. |
|
HoldRetrieveInd |
M |
Shall indicate the PTC Session is put on hold ((deactivate Media Bursts) a PTC Session is locked for talking/listening)) or released from hold. True indication equals placed on hold, false indication was retrieved from hold. |
17.2.12 PTC Media Modification
During the PTC Session, a PTC Client may modify the voice frame packetization or voice codec mode by Out-of-band signalling using SDP payload within SIP messages. The Media Modification Continue Record shall be sent from the MF/DF to the LEMF when a re-negotiation of the media parameters occurs during a PTC Session involving the target MS.
Table 17.2.12: PTC Media Modification Continue Record
|
Parameter |
MOC |
Description/Conditions |
||
|
observed IMPI |
M |
Provide at least one and others when available. |
||
|
observed IMPU |
||||
|
observed IPv4/IPv6 Address |
||||
|
observed MCPPTID |
||||
|
EventType |
M |
Shall indicate a Media Modification Continue Record event. |
||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
||
|
MediaStreamAvail |
C |
Shall include to indicate if the PTC target’s PTC Client is not able/willing to receive media streams immediately. |
||
|
Bearer-Capability |
M |
Shall provide when known the media characteristics information Elements of the PTC session, e.g. SDP information, media format, vocoder type. |
||
17.2.13 PTC Group Advertisement
The PTC Group Advertisement Report Record shall be sent from the MF/DF to the LEMF is generated when a PTC Intercept Target sends Group Advertisement information to a single PTC user, a list of PTC users or to all members of the Group using the Group Identity.
Table 17.2.13: PTC Group Advertisement Report Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Group Advertisement Report Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCIDList |
C |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
|
PTCGroupID |
C |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
|
GroupAuthRule |
C |
Identifies the action requested by the PTC Target to the PTC Group Authorization Rules: – Report when action requested to the PTC Group Authorization Rules by the target. – Report when the PTC Target attempts a change or queries the Access Control List(s). |
|
GroupAdSender |
M |
Identifies the group administrator who was the originator of the group call. |
|
PTCHost |
C |
Identifies the PTC participant who has authority to initiate and administrate an active PTC Group Session. Provide when known. |
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
17.2.14 PTC Floor Control
Floor Control arbitrates requests from the PTC Clients for the right to send media (i.e. the right to speak). Note, the term "Floor Control" is used to mean the same as the term "Talk Burst Control". Talk Burst Control Protocol [TBCP] is a protocol for performing floor control and these aspects are defined in (OMA-PoC-AD [97]) and [OMA-PoC-UP [98]). When the PTC target is participating in a PTC Session, a Floor Control event Continue Record shall be sent from the MF/DF to the LEMF when the target requests to speak (e.g. presses the PTC mechanism) or the target is given permission to speak in response to a request (e.g. the network responds positively to the PTC Subscriber’s request) or is refused the request to speak and when the target is finished speaking (e.g. the PTC Intercept target releases the PTC mechanism).
When the PTC target is participating in a PTC Session, a Floor Control Continue Record is triggered when:
– The PTC target request to speak is received (e.g. when the PTC Intercept target presses the Push To Talk (PTT)).
– The PTC target is given permission to speak in response to a request (e.g. the network responds positively to the PTC Subscriber’s request).
– The PTC target who initiates a PTC session is given permission to speak automatically when the PTC session starts (i.e., if the service allows the initiating PTC participant the floor automatically and there is no request).
– The PTC target’s request to speak is refused (e.g. the network responds negatively to the PTC Subscriber’s request).
– The PTC target request to release the floor control is received (e.g. when the PTC target releases the PTT).
– The service revokes the PTC target’s permission to speak (e.g. network response, possibly to time out or host’s instructions).
– The floor becomes idle (i.e., no one has requested nor has permission to speak).
– An associate (i.e., another member of the PTC Session other than the PTC target) is given permission to speak and the PTC target’s service is aware of the request.
– The PTC target cancels the request to speak.
– The PTC target’s request to speak is queued.
– The PTC target’s query to determine their position in the floor-control-request queue is received.
– The position of the PTC target’s request in the queue is changed due to differing priority levels in the queue (OMA-PoC-AD [97]).
– The PTC target’s request to speak is de-queued and permission to speak is granted (i.e., when the request for permission to speak was previously queued).
– When the PTC associate’s request permission to speak is queued or de-queued (i.e., permission to speak is granted) and the PTC target’s service is aware of the event.
Table 17.2.14: PTC Floor Control Continue Record
|
Parameter |
MOC |
Description/Conditions |
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Floor Control Continue Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|
FloorActivity |
M |
Choice of: a) TBCP_Request: Used by the PTC Client to request permission from the PTC Server to send a Talk Burst. b) TBCP_Granted: Used by the PTC Server to notify the PTC Client that it has been granted permission to send a Talk Burst. c) TBCP_Deny: Used by the PTC Server to notify a PTC Client that it has been denied permission to send a Talk Burst. d) TBCP_Idle: Used by the PTC Server to notify all PTC Clients that no one has the permission to send a Talk Burst at the moment and that it may accept the TBCP Talk Burst Request message. e) TBCP_Taken: Used by the PTC Server to notify all PTC Clients, except the PTC Client that has been given permission to send a Talk Burst, that another PTC Client has been given permission to send a Talk Burst. f) TBCP_Revoke: Used by the PTC Server to revoke the media resource from a PTC Client and can be used for pre-emption functionality but is also used by the system to prevent overly long use of the media resource. g) TBCP_Queued: Indicates the request to talk is queued, if queued floor control is supported. Include identification of the PTC Client that has the queued Talk Burst, if known. h) TBCP_Release: Indicates the request to talk has completed. |
|
FloorSpeakerID |
C |
Include identification of the PTC Client that has the Talk Burst, if known. Do not include if TBCP Idle parameter is present. |
|
MaxTBTime |
C |
Include the maximum duration value for the Talk Burst before the permission is revoked. Provide when known |
|
QueuedFloorControl |
C |
Indicates if queuing is supported by the PTC Server and the PTC Intercept Subject’s PTC Client. |
|
QueuedPosition |
C |
If queued floor control is supported, indicates the queue position. |
|
TalkBurstPriority |
C |
If more than one level of priority is supported, indicates the Talk Burst priority level of the PTC Client (OMA-PoC-AD [97]). |
|
Talkburstreason |
C |
The reason code for the denial or revoke of a Talk Burst. Provide if known. |
17.2.15 PTC Target Presence
If the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of a Presence Source, the PTC Target Presence Report Record shall be sent from the MF/DF to the LEMF when the PTC Server publishes network presence information to the Presence server on behalf of PTC target.
Table 17.2.15: PTC Target Presence Report Record
|
Parameter |
MOC |
Description/Conditions |
||
|
observed IMPI |
M |
Provide at least one and others when available. |
||
|
observed IMPU |
||||
|
observed IPv4/IPv6 Address |
||||
|
observed MCPPTID |
||||
|
EventType |
M |
Shall indicate a Target Presence Report Record event. |
||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||
|
TargetPresenceStatus |
C |
Shall identify any PTC related presence information of the PTC target, if changed. |
||
17.2.16 PTC Associate Presence
The PTC Associate Presence Report Record shall be sent from the MF/DF to the LEMF when the PTC Server receives presence status notifications from the Presence Servers after having subscribed to the PTC presence status of other PTC Clients (i.e. Associates of the PTC Intercept target).
Table 17.2.16: PTC Associate Presence Report Record
|
Parameter |
O/C/M |
Description/Conditions |
|||
|
observed IMPI |
M |
Provide at least one and others when available. |
|||
|
observed IMPU |
|||||
|
observed IPv4/IPv6 Address |
|||||
|
observed MCPPTID |
|||||
|
EventType |
M |
Shall indicate a Associate Presence Report Record event. |
|||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|||
|
AssociatePresenceStatus |
C |
Shall provide the Associate Presence Status, which is a list of: – PresenceID: Identity of PTC Client(s) or PTC group, when known. – PresenceType: Identifies type of ID [PTC Client(s) or PTC group]. – PresenceStatus: Presence state of each ID. Report when the Presence functionality is supported by the PTC Server and the PTC Server assumes the role of the Watcher on behalf of PTC target. |
|||
17.2.17 PTC List Management Events
When the targets PTC Client attempts to change their own contact list or their own PTC Group list(s), the PTC List Management Events Report Record shall be sent from the MF/DF to the LEMF. Also when the network notifies the Intercept target’s PTC Client of changes made to their PTC-specific documents stored in the network (i.e. contact lists or PTC Group lists), the PTC List Management Events Report Record shall be sent from the MF/DF to the LEMF.
The PTC List Management Events Report Record is triggered when:
– The PTC Target’s PTC Client attempts to change his contact list (e.g. create, modify, retrieve, delete);
– The PTC Target’s PTC Client attempts to change his PTC Group list (e.g. create, modify, retrieve, delete; or add or delete a contact from a PTC Group);
– The network notifies the PTC Target’s PTC Client of changes made to his contact list, or his PTC Group list; or
– If the PTC Target is a member of a PTC Group and the network notifies the PTC Target’s PTC Client of changes made to that PTC Group List.
The PTC List Management Events Report Record is triggered if the event is successful or unsuccessful.
Table 17.2.17: PTC List Management Events Report Record
|
Parameter |
MOC |
Description/Conditions |
||
|
observed IMPI |
M |
Provide at least one and others when available. |
||
|
observed IMPU |
||||
|
observed IPv4/IPv6 Address |
||||
|
observed MCPPTID |
||||
|
EventType |
M |
Shall indicate a List Management Events Report Record event. |
||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||
|
TargetPresenceStatus |
C |
Shall identify any PTC related presence information of the PTC target, if changed. |
||
|
ListManagementType Choice of: a) ContactListManagementAttempt b) GroupListManagementAttempt c) ContactListManagementResult d) GroupListManagementResult e) Request unsuccessful |
C |
The "List Management Attempts" identify the type of list being managed by the PTC Target. For example, a) and b) are reported when PTC Target’s Client attempt changes to his Contact List and his PTC Group List(s). The "List Management Results" identify the network response to a modification by the PTC Target. For example, c), d), or e) is reported when the network notifies the PTC Target of changes to his Contact List or his PTC Group List(s). |
||
|
ListManagmentAction Choice of: a) Create b) Modify c) Retrieve d) Delete e) Notify |
C |
Identifies the action requested by the PTC Intercept Subject to the Contact Lists or PTC Group List(s). Report when PTC Intercept Subject attempts changes to his Contact List or PTC Group List(s). Also report when a notification is sent to the PTC Intercept Subject due to changes occuring to his Contact List or PTC Group List(s). |
||
|
ListManagementFailure |
C |
Reports the error code or reason for failure. Report when List Management request is unsuccessful. |
||
|
ContactID |
C |
Identity of the contact in the list. One contact per Contact List or PTC Group List. Report if known. |
||
|
PTCGroupID |
C |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
||
|
PTCIDList |
C |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
||
|
PTCHost |
C |
Identifies the PTC participant who has authority to initiate and administrate an active PTC Group Session. Provide when known. |
||
17.2.18 PTC Access Policy
The PTC Access Policy Report Record shall be sent from the MF/DF to the LEMF when the PTC Intercept target attempts to change the access control lists (e.g. PTC user access policy and PTC Group authorization rules) located in the PTC XML Document Management Server (XDMS) see ref (OMA-PoC-AD [97]). In addition the PTC Access Policy Report Record shall be sent from the MF/DF to the LEMF when the network responds to a modification or query by the PTC Intercept target to the access control lists (e.g. PTC user access policy and PTC Group authorization rules).
The PTC Access policy message is triggered when:
– The PTC Target requests changes to the access control lists.
– The PTC Target is the PTC Group owner and modifies the PTC User permissions to access a PTC Group.
– The PTC Target attempts a change or queries the access control lists (e.g. PTC User access policy and PTC Group authorization rules) regardless if the change or query to the access control list was successful or unsuccessful.
– The PTC Target is the owner of a PTC Group (i.e., the creator of the Chat PTC Group or Pre-Arranged PTC Group) and attempts a change or queries to the PTC Group authorization rules regardless if the request was successful or unsuccessful.
– The network responds to a change to the PTC Group authorization rules by the PTC Target when the PTC Target is the owner of a PTC Group (i.e., the creator of the Chat PTC Group or Pre-Arranged PTC Group), or the network responds to a query by the PTC Target for his PTC user access policy and PTC group authorization rules.
– The network notifies the PTC Target of changes to his access control lists (e.g. PTC User access policy and PTC Group authorization rules) regardless if the change to the access control list was successful or unsuccessful.
Table 17.2.18: PTC Access Policy event Record
|
Parameter |
MOC |
Description/Conditions |
||
|
observed IMPI |
M |
Provide at least one and others when available. |
||
|
observed IMPU |
||||
|
observed IPv4/IPv6 Address |
||||
|
observed MCPPTID |
||||
|
EventType |
M |
Shall indicate an Access Policy event Record event. |
||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||
|
TargetPresenceStatus |
M |
Shall identify any PTC related presence information of the PTC target, if changed. |
||
|
AccessPolicyType Choice of: a) PTCUserAccessPolicyAttempt b) GroupAuthorizationRulesAttempt c) PTCUserAccessPolicyQuery d) GroupAuthorizationRulesQuery e) PTCUserAccessPolicyResult f) GroupAuthorizationRulesResult g) Request unsuccessful |
C |
Identifies the type of Access Policy list being managed or queried by the PTC Target: – Report a), b), c), or d) when the PTC Target attempts a change or queries the Access Control list(s). – Report e), f), or g) when the network notifies the PTC Target of changes to the Access Control list(s) or the request was unsuccessful. |
||
|
PTCUserAccessPolicy Choice of: a) Allow Incoming PTC Session request b) Block Incoming PTC Session request c) Allow Auto Answer Mode d) Allow Override Manual Answer Mode |
C |
Identifies the action requested by the PTC Intercept Target to the PTC user or group access policy: – Report when action requested to the PTC User Access Policy. – Report when the PTC Intercept Subject attempts a change or queries the Access Control list(s). |
||
|
GroupAuthRule Choice of: a) Allow Initiating PTC Session b) Block Initiating PTC Session c) Allow Joining PTC Session d) Block Joining PTC Session e) Allow Add Participants f) Block Add Participants g) Allow Subscription PTC Session State h) Block Subscription PTC Session State i) Allow Anonymity j) Forbid Anonymity |
C |
Identifies the action requested by the PTC Target to the PTC Group Authorization Rules: – Report when action requested to the PTC Group Authorization Rules by the target. – Report when the PTC Target attempts a change or queries the Access Control List(s). |
||
|
ContactID |
C |
Identity of the contact in any of the lists. One contact per Access Control list. Required for all contact requests. Report if known. |
||
|
PTCGroupID |
C |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
||
|
AccessPolicyFailure |
C |
Reports the error code or reason for failure when Access Policy Request is unsuccessful. |
||
17.2.19 PTC Media Type Notification
The PTC Media Type Notification Continue Record shall be sent from the MF/DF to the LEMF when media is detected at the ICE for media types other than PTC speech (e.g. video, images, text, and files) directed to/from the target’s PTC client. Media Types are either real-time or non-real time, i.e., Audio (e.g. music), Video, Discrete Media (e.g. still image, formatted and non-formatted text, file), or Real Time Streaming Media (RTSP). Media parameters are SIP/SDP based information exchanged between the PTC server and the targets PTC client, between the PTC server and the PoC Box and between PTC servers that specify the characteristics of the Media for a PTC session being established or that already exists.
Table 17.2.19: PTC Media Type Notification Continue Record
|
Parameter |
MOC |
Description/Conditions |
|||||
|
observed IMPI |
M |
Provide at least one and others when available. |
|||||
|
observed IMPU |
|||||||
|
observed IPv4/IPv6 Address |
|||||||
|
observed MCPPTID |
|||||||
|
EventType |
M |
Shall indicate a Media Type Notification Continue Record event. |
|||||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|||||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|||||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|||||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|||||
|
MediaStreamAvail |
C |
Shall include for a Pre-established session to indicate if the PTC intercept target’s PTC Client is not able/willing to receive media streams immediately, when the Pre-established session is established. |
|||||
|
PTCSessionInfo |
M |
Shall provide PTC Session information such as PTC Session URI, PTC Session type, and Nickname. |
|||||
17.2.20 PTC Pre-established Session Record
The PTC Pre-Established Session Record shall be reported when a pre-established session is setup/modified/released between the client present within the target’s UE and the PTC server associated with the PTC client.
Table 17.2.20: PTC Pre-Established Session Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMPI |
M |
Provide at least one and others when available. |
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a PTC Pre-Established Session event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCServerURI |
M |
The participating PTC Server URI associated with the PTC client originating the PTC Pre-Established Session request. |
|
RTPSetting |
M |
The IP address and the port number of the target at the PTC Server for the RTP Session |
|
PTCMediaCapability |
M |
The codec(s) and Media Parameters selected by the PTC Server from those contained in the original SDP offer from the targets PTC Client. |
|
PreEstSessionID |
M |
Identifies the PTC Pre-established Session identity. |
|
PreEstStatus |
M |
Indicates if the Pre-Established Session is established (setup completed), modified, or released. |
|
MediaStreamAvail |
C |
Indicates if the target’s PTC Client is not able/willing to receive media streams immediately. Provide when Pre-established session is established |
|
Location |
C |
When authorized, reports when a PTC Pre-Established Session is first established or terminated by the intercept target. |
|
FailureCode |
C |
Provide when the Pre-Established Session cannot be established or modified. |
17.3 PTC Group Calls
17.3.1 Introduction
A PTC Group Session supports a One-to-One, One-to-Many, or One-to-Many-to-One with the following events; Session initiation request/response, Session modification, joining/leaving, termination, voice communication begins, ends, or forced disconnected. When detected at the ICE, these events can originate from the target’s PTC Client to the PTC Server or from the PTC Server to the target’s PTC Client or PTC server to PTC Server on the behalf of the target.
17.3.2 Group Call Request
The Group Call Request Begin Record shall be sent from the MF/DF to the LEMF when the PTC server serving the target receives a request for a group session or sends to the target’s PTC client for a PTC Group Call request to join, rejoin, or release of the group call. This can be a Group Call Request event received at the PTC Server serving the target from a separate PTC server (outside the SP architecture) to the target.
Table 17.3.2: Group Call Request Begin Record
|
Parameter |
O/C/M |
Description/Conditions |
||||
|
observed MSISDN |
M |
Provide at least one and others when available. |
||||
|
observed IMSI |
||||||
|
observed IMEI |
||||||
|
observed SIP URI |
||||||
|
observed TEL URI |
||||||
|
observed IMPI |
||||||
|
observed IMPU |
||||||
|
observed IPv4/IPv6 Address |
||||||
|
observed MCPPTID |
||||||
|
EventType |
M |
Shall indicate a Group Call Request Begin Record event. |
||||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
||||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
||||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
||||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
||||
|
PTCGroupID |
M |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
||||
|
PTCParticipants |
C |
Shall Identify all known individual PTC participants, if known. |
||||
|
PTCIDList |
M |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
||||
|
PTCHost |
C |
Identifies the PTC participant who has authority to initiate and administrate an active PTC Group Session. Provide when known. |
||||
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
||||
|
BroadcastIndicator |
C |
Shall indicates that this was a broadcast destined for the group |
||||
|
Emergency |
C |
Shall indicate emergency type, if this is a peril or an imminent peril condition alert. |
||||
|
EmergencyGroupState |
C |
Shall indicate the emergency state or condition of an MCPTT emergency call, if an emergency is indicated. |
||||
|
AlertIndicator |
C |
Indicates an emergency alert condition was indicated. |
||||
|
MCPTTInd |
C |
Indicates direction of the emergency state, or condition, as either from the MCPPT target or from a MCPTT group to the target. |
||||
|
MCPTTOrganizationName |
C |
Include the name of the organization that the MCPTT device belongs to, if known. |
||||
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
||||
17.3.3 Group Call Cancel
When a Group Call Cancel is detected it can originate from the target’s client or from the Group. In either case, a Group Call Cancel End Record shall be sent from the MF/DF to the LEMF. This event is generated when received at the PTC server serving the target or sent to the targets PTC client for a PTC Group Call request to release of the group call. This Group Call Cancel can be received at the PTC Server serving the target from a separate PTC server (outside the SP architecture) to the target.
Table 17.3.3: Group Call Cancel End Record
|
Parameter |
O/C/M |
Description/Conditions |
|
observed MSISDN |
M |
Provide at least one and others when available. |
|
observed IMSI |
||
|
observed IMEI |
||
|
observed SIP URI |
||
|
observed TEL URI |
||
|
observed IMPI |
||
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Session Abandon End Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
Lawful intercept identifier |
M |
Shall be delivered. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCGroupID |
M |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
|
PTCParty |
M |
The identity of the associate that cancelled the session. |
|
PTCIDList |
C |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
|
BroadcastIndicator |
C |
Shall indicate that this was a broadcast destined for the group |
|
Emergency |
C |
Shall indicate emergency type, if this is a peril or an imminent peril condition alert cancel. |
|
EmergencyGroupState |
C |
Shall indicate the emergency state for the group was cancelled. |
|
AlertIndicator |
C |
Indicates an emergency alert signalling was cancelled. |
|
MCPTTInd |
C |
Indicates direction of the received cancel as either from the MCPPT target or from a MCPTT group to the target. |
|
MCPTTOrganizationName |
C |
Include the name of the organization that the MCPTT device belongs to, if known. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |
17.3.4 Group Call Response
A Group Call Response Continue Record shall be sent from the MF/DF to the LEMF upon sending a group call response to the target or receiving a group call response at the PTC Server from the target or on behalf of the target sends a group call response to a separate PTC server (outside the SP architecture).
Table 17.3.4: Group Call Response End Record
|
Parameter |
O/C/M |
Description/Conditions |
|
observed MSISDN |
M |
Provide at least one and others when available. |
|
observed IMSI |
||
|
observed IMEI |
||
|
observed SIP URI |
||
|
observed TEL URI |
||
|
observed IMPI |
||
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Group Call Response End Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
PTCGroupID |
M |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
|
PTCParty |
C |
The identity of the associate that requested the session, if requested by the associate. |
|
PTCParticipants |
M |
Shall Identify all known individual PTC participants. |
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
|
BroadcastIndicator |
C |
Shall indicates that this was a broadcast destined for the group |
|
AlertIndicator |
C |
Indicates an emergency alert condition was indicated. |
|
Emergency |
C |
Shall indicate emergency type, if this is a peril or an imminent peril condition alert. |
|
EmergencyGroupState |
C |
Shall indicate the emergency state or condition of an MCPTT emergency call, if an emergency is indicated. |
|
MCPTTInd |
C |
Indicates direction of the emergency state, or condition, as either from the MCPPT target or from a MCPTT group to the target. |
|
MCPTTOrganizationName |
C |
Include the name of the organization that the MCPTT device belongs to, if known. |
17.3.5 PTC Group Interrogate
A PTC Group Interrogate Continue Record shall be sent from the MF/DF to the LEMF when a group interrogate request or a response is received at the PTC Server serving the target.
Table 17.3.5: Group Interrogate Continue Record
|
Parameter |
O/C/M |
Description/Conditions |
|||
|
observed MSISDN |
M |
Provide at least one and others when available. |
|||
|
observed IMSI |
|||||
|
observed IMEI |
|||||
|
observed SIP URI |
|||||
|
observed TEL URI |
|||||
|
observed IMPI |
|||||
|
observed IMPU |
|||||
|
observed IPv4/IPv6 Address |
|||||
|
observed MCPPTID |
|||||
|
EventType |
M |
Shall indicate a Group Interrogate Continue Record event. |
|||
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|||
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|||
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|||
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|||
|
PTCGroupID |
M |
Identifies the PTC Group Identity, Nick Name, and characteristics. |
|||
|
PTCParty |
C |
The identity of the associate that generated the request to the target, if initiated by the associate. |
|||
|
PTCParticipants |
M |
Shall Identify all known individual PTC participants. |
|||
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
|||
|
Emergency |
C |
Shall indicate emergency type, if this is a peril or an imminent peril condition alert. |
|||
|
EmergencyGroupState |
C |
Shall indicate the emergency state or condition of an MCPTT emergency call, if an emergency is indicated. |
|||
|
MCPTTInd |
C |
Indicates direction of the emergency state, or condition, as either from the MCPPT target or from a MCPTT group to the target. |
|||
|
MCPTTOrganizationName |
C |
Include the name of the organization that the MCPTT device belongs to, if known. |
|||
|
PTCIDList |
C |
Identifies each participant from the PTC Target’s contact list (i.e., individuals) and PTC Group list (i.e., list of pre-identified individuals using a group identification) for a group call. |
|||
17.3.6 MCPTT Imminent Peril Group Call
When the MCPTT Imminent Peril Group Call Request, Response or Cancel is detected at the MCPTT Server, a MCPTT Imminent Peril Group Call Report Record shall be sent from the MF/DF to the LEMF it can originate from the targets MCPTT client or to the targets MCPTT client from a MCPTT Group.
Table 17.3.6: Imminent Peril Group Call Report Record
|
Parameter |
O/C/M |
Description/Conditions |
|
observed MSISDN |
M |
Provide at least one and others when available. |
|
observed IMSI |
||
|
observed IMEI |
||
|
observed SIP URI |
||
|
observed TEL URI |
||
|
observed IMPI |
||
|
observed IMPU |
||
|
observed IPv4/IPv6 Address |
||
|
observed MCPPTID |
||
|
EventType |
M |
Shall indicate a Imminent Peril Group Call Report Record event. |
|
LIID |
M |
Shall include a unique number for each lawful authorization. |
|
TimeStamp |
M |
Shall include the Time and date of the event generation. |
|
Correlation |
M |
Shall provide to allow correlation of CC and IRI records as well as related IRI records. |
|
Network Identifier |
M |
Unique identifier for the network element reporting the event. |
|
MCPTTGroupID |
M |
Identifies the Mission Critical Push To Talk group Identity |
|
PTCParticipants |
M |
Shall Identify all known individual PTC participants. |
|
GroupCharacteristics |
C |
PTC group identifying feature or any identifying specific characteristics for the group e.g. MCPTT specific. |
|
ImminentPerilInd |
M |
Shall indicate that the PTC call is an imminent peril notification, the specific notification to/from the target (i.e., call request to target, response from the target, or cancel). |
|
PTCParty |
M |
The identity of the MCPTT associate that initiated the session to the target. |
|
MCPTTInd |
M |
Indicates direction of the emergency state, or condition, as either from the MCPPT target or from a MCPTT group to the target. |
|
Location |
C |
Shall include when reporting of the PTC Intercept Target’s location information is authorized |