Content for TS 33.128 Word version: 18.6.0

0… 4… 5… 5.7… 6… 6.2.2.2A… 6.2.3… 6.2.3.2.7… 6.2.3.3… 6.2.4… 6.3… 6.3.2.2A… 6.3.3… 6.3.3.2… 6.3.3.2.4… 6.3.3.2A… 7… 7.3… 7.3.3… 7.3.3.2.21… 7.3.3.2.42… 7.3.3.2.63… 7.3.4… 7.4… 7.4.3.8… 7.5… 7.6… 7.7… 7.7.4… 7.8… 7.8.4… 7.9… 7.10… 7.10.4… 7.11… 7.12… 7.13… 7.13.3… 7.13.3.4… 7.14… 7.15… 8… A… D… E… M…

7.5 PTC service 7.5.1 Introduction 7.5.1.1 Provisioning over LI_X1 7.5.1.2 Generating xIRI over LI_X2 7.5.1.3 Generation of xCC over LI_X3 7.5.2 IRI events 7.5.2.1 PTC registration 7.5.2.2 PTC session initiation 7.5.2.3 PTC session abandon attempt 7.5.2.4 PTC session start 7.5.2.5 PTC session end 7.5.2.6 PTC start of interception 7.5.2.7 PTC pre-established session 7.5.2.8 PTC instant personal alert 7.5.2.9 PTC party join 7.5.2.10 PTC party drop 7.5.2.11 PTC party hold 7.5.2.12 PTC media modification 7.5.2.13 PTC group advertisement 7.5.2.14 PTC floor control 7.5.2.15 PTC target presence 7.5.2.16 PTC participant presence 7.5.2.17 PTC list management 7.5.2.18 PTC access policy 7.5.3 IRI and CC Generation 7.5.3.1 Generation of IRI over LI_HI2 7.5.3.2 Generation of CC over LI_HI3
...

The Stage 3 intercept capabilities defined in this clause for the Push to Talk over Cellular (PTC) service apply when supported by a CSP. The term PTC represents either a Push to Talk over Cellular (PoC) or Mission Critical Push to Talk (MCPTT) type service. The use of the term PTC server represents either a MCPTT function or PoC server.

7.5.1.1 Provisioning over LI_X1 p. 234

The IRI-POI present in the PTC server is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2 of the present document.

The POI in the PTC Server shall support the identifier types given in Table 7.5.1-1.

Table 7.5.1-1: TargetIdentifier Types for PTC service

Identifier	Owner	ETSI TS 103 221-1 [7] TargetIdentifier type	Definition
iMPU	ETSI	IMPU	See ETSI TS 103 221-1 [7]
iMPI	ETSI	IMPI	See ETSI TS 103 221-1 [7]
mCPTTID	ETSI	TargetIdentifierExtension	See XSD schema
instanceIdentifierURN	3GPP	TargetIdentifierExtension	See XSD schema
pTCChatGroupID	3GPP	TargetIdentifierExtension	See XSD schema

7.5.1.2 Generating xIRI over LI_X2 p. 234

The IRI-POI present in the PTC server shall send xIRI over LI_X2 for each of the events listed in clause 7.6.3 of TS 33.127, each of which is described in the following clauses. The IRI events are based on the use of 3GPP MCPTT features as defined in TS 24.379 and OMA PoC features as defined in OMA-TS-PoC_System_Description-V2_1-20110802-A [56].

7.5.1.3 Generation of xCC over LI_X3 p. 235

The CC-POI present in the PTC server shall send xCC over LI_X3.

The CC-POI shall set the payload format to indicate the appropriate payload type (5 for IPv4 Packet, 6 for IPv6 Packet) per clause 6.2.3.6 of the present document.

7.5.2 IRI events p. 235

7.5.2.1 PTC registration p. 235

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCRegistration record when the IRI-POI present in the PTC server detects that a PTC target matching one of the PTC target identifiers, referenced in clause 7.5.1.1, provided via LI_X1 has registered, re-registered, or de-registered for PTC services , regardless of whether it is successful or unsuccessful. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server receives a SIP REGISTER from a PTC target.

Table 7.5.2-1: Payload for PTCRegistration record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCServerURI	Shall include the identity of the PTC server serving the PTC target.	M
pTCRegistrationRequest	Identifies the type of registration request (register, re-register, or de-register).	M
pTCRegistrationOutcome	Identifies success or failure of the registration.	M

7.5.2.2 PTC session initiation p. 235

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCSessionInitiation record when the IRI-POI present in the PTC server detects that the PTC target initiates an on-demand session or the target receives an invitation to join an on-demand session regardless of the success or the final disposition of the invitation. The PTCSessionIniation record shall also be reported when a chat group is the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a SIP INVITE from a PTC target.
when the PTC Server sends a SIP INVITE to the PTC target.
when the PTC Server hosting a PTC chat group session, where the PTC chat group is the target, receives a SIP INVITE from a participating PTC server to initiate a PTC chat group session.

Table 7.5.2-2: Payload for PTCSessionInitiation record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCServerURI	Shall include the identity of the PTC server serving the PTC target.	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCOriginatingID	Shall identify the originating party.	M
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
pTCParticipantPresenceStatus	Shall provide the Participant 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. True indicates PTC client is available, while false indicates PTC client is unavailable. Report when the Presence functionality is supported by the PTC server and the PTC server assumes the role of the watcher on behalf of the PTC target or in the case of a target PTC chat group, when the PTC server assumes the role of the watcher on behalf of any member of the chat group.	C
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCBearerCapability	Shall provide when known the media characteristics information elements of the PTC session, encoded in SDP format as per Section 5 of RFC 4566.	C
pTCHost	Shall identify the PTC participant who has the authority to initiate and administrate a PTC session, if known.	C

7.5.2.3 PTC session abandon attempt p. 236

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCSessionAbandon record when the IRI-POI present in the PTC server detects that the PTC Session is not established and the request is abandoned before the PTC session starts. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server serving the PTC target receives a SIP CANCEL from the PTC target or sends a SIP CANCEL to the PTC target.

Table 7.5.2-3: Payload for PTCSessionAbandonAttempt record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCAbandonCause	Shall identify the reason for the abandoned PTC session based on the warning header field code provided in a response to a SIP INVITE per clause 4.4.2 of TS 24.379.	M

7.5.2.4 PTC session start p. 236

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCSessionStart record when the IRI-POI present in the PTC server detects that the PTC Session is initiated and communication begins for both an on-demand and pre-established PTC session. The PTCSessionStart record shall also be reported when a chat group is the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server sends a SIP 200 OK to the PTC target in response to a SIP INVITE from the PTC target for an on-demand PTC session where the PTC target originates the PTC session.
when the PTC server receives a SIP 200 OK from the PTC target in response to a SIP INVITE for an on-demand PTC session where the PTC target receives an invitation to join a PTC session.
when the PTC server receives a SIP 200 OK from the participant PTC server in response to a SIP INVITE previously sent to that participating PTC server for PTC sessions initiated by the PTC target with a pre-established PTC session (PTC server sends a TBCP Connect to the PTC target with a pre-established session).
when the PTC server sends a SIP 200 OK to the participant PTC server in response to a SIP INVITE previously received from that participating PTC server for PTC sessions terminated to the PTC target with a pre-established PTC session (PTC server sends a TBCP Connect to the PTC target with a pre-established session).
when the PTC server hosting a PTC chat group session, where PTC chat group is the PTC target, sends a SIP 200 OK in response to a SIP INVITE previously received from the participant PTC server to initiate a PTC chat group session.

Table 7.5.2-4: Payload for PTCSessionStart record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCServerURI	Shall include the identity of the PTC server serving the PTC target.	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCOriginatingID	Shall identify the originating party.	M
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
pTCParticipantPresenceStatus	Shall provide the Participant 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. True indicates PTC client is available, while false indicates PTC client is unavailable. Report when the Presence functionality is supported by the PTC server and the PTC server assumes the role of the watcher on behalf of the PTC target.	C
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCHost	Shall identify the PTC participant who has the authority to initiate and administrate a PTC Session, if known.	C
pTCBearerCapability	Shall provide the media characteristics information elements of the PTC session, encoded in SDP format as per Section 5 of RFC 4566 when known.	C

7.5.2.5 PTC session end p. 237

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCSessionEnd record when the IRI-POI present in the PTC server detects that the PTC session is released for any reason (i.e. normal or abnormal release) and voice communications ends. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a SIP BYE from the PTC target to end the session.
when the PTC server receives a SIP 200 OK from the PTC target in response to a SIP BYE.
when the PTC server sends a SIP BYE to the participating PTC server to end the PTC session of a PTC target with a pre-established PTC session (PTC server also sends a TBCP Disconnect to the PTC target with a pre-established PTC session).
when the PTC server receives a SIP BYE from the participant PTC server to end the PTC session of a PTC target with a pre-established PTC session (PTC server sends a TBCP Disconnect to the PTC target with a pre-established PTC session).
when the PTC server hosting a PTC chat group session, where PTC chat group is the PTC target, sends a SIP 200 OK in response to a SIP BYE received from the participating PTC server of the last participant in the PTC chat group session.
when the PTC server sends a SIP 487 to the PTC target in response to a SIP CANCEL to end the session.

Table 7.5.2-5: Payload for PTCSessionEnd record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCServerURI	Shall include the identity of the PTC server serving the PTC target.	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCSessionEndCause	Shall identify the reason for the PTC session end based on the following events per OMA-TS-PoC_System_Description-V2_1-20110802-A [56] clause 4.5.7: PTC session initiator leaves session Defined participant leaves session Number of participants less than certain value PTC Session timer expired PTC Speech inactive for specified time All Media types inactive for specified time	M

7.5.2.6 PTC start of interception p. 238

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCStartOfInterception record when a PTC target or a PTC chat group as a target has an active PTC session in progress. If multiple PTC Sessions are active at the start of interception, a PTCStartOfInterception record is generated for each active session. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server detects that LI is enabled on a PTC participant or a PTC chat group with an active PTC session.

Table 7.5.2-6: Payload for PTCStartOfIntercept record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCPreEstSessionID	Identifies the PTC Pre-Established Session Identity when available.	C
pTCOriginatingID	Shall identify the originating party.	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session) when available.	C
pTCHost	Shall identify the PTC participant who has the authority to initiate and administrate a PTC session, if known.	C
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCMediaStreamAvail	Shall include this parameter to indicate if the PTC target is able/not able to receive media streams immediately. True indicates available for media, while false indicates not able to accept media.	M
pTCBearerCapability	Shall provide when known the media characteristics information elements of the PTC session, encoded in SDP format as per Section 5 of RFC 4566.	C

7.5.2.7 PTC pre-established session p. 239

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCPre-EstablishedSession record when the IRI-POI present in the PTC server detects that a pre-established session is setup/modified/released between the PTC target and the PTC server associated with the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC Server receives a SIP INVITE from the PTC target to setup a pre-established session.
when the PTC Server receives a SIP BYE from the PTC target to release a pre-established session.
when the PTC Server receives a SIP UPDATE or SIP re-INVITE from the PTC target for a pre-established session to modify the current session.

Table 7.5.2-7: Payload for PTCPre-EstablishedSession record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCServerURI	Shall include the identity of the PTC server serving the PTC target.	M
rTPSetting	The IP address and the port number of the PTC target at the PTC server for the RTP Session.	M
pTCMediaCapability	The codec(s) and media parameters selected by the PTC server from those contained in the original SDP offer from the PTC target's SIP REFER and encoded in SDP format as per Section 5 of RFC 4566.	M
pTCPreEstSessionID	Identifies the PTC Pre-Established Session Identity.	M
pTCPreEstStatus	Indicates if the pre-established session is established (setup completed), modified, or released.	M
pTCMediaStreamAvail	Shall include for a pre-established session to indicate if the PTC target's PTC client is able/not able to receive media streams immediately, when the pre-established session is established. True indicates available for media, while false indicates not able to accept media.	M
location	Shall include the PTC target's location when reporting of the PTC target's location information is authorized and available.	C
pTCFailureCode	Provide when the pre-established session cannot be established or modified.	C

7.5.2.8 PTC instant personal alert p. 240

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCInstantPersonalAlert record when the IRI-POI present in the PTC server detects that an Instant Personal Alert (IPA) (i.e. a request for one participant to initiate a one-to-one PTC session) is initiated by or sent to the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a SIP MESSAGE from a PTC target for an IPA.
when the PTC Server sends a SIP MESSAGE to the PTC target for an IPA.

Table 7.5.2-8: Payload for PTCInstantPersonalAlert record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCIPAPartyID	Identifies the PTC participant that receives or has sent the Instant Personal Alert to the target.	M
pTCIPADirection	Identifies the direction (To PTC target or From PTC target) of the Instant Personal Alert.	M

7.5.2.9 PTC party join p. 240

The IRI-POI present in the PTC server hosting the PTC chat group session when the PTC chat group is the PTC target, shall generate an xIRI containing a PTCPartyJoin record when the IRI-POI present in that PTC server detects when a PTC participant joins (or re-joins) an on-going PTC chat group session. The PTCPartyJoin record shall also be generated when the IRI-POI present in the participating PTC server of the PTC target detects when a PTC Participant joins (or re-joins) an on-going PTC chat group session. Accordingly, the IRI-POI in the participating PTC server generates the xIRI when the following event is detected:

when the PTC server hosting a PTC chat group session sends a SIP 200 OK in response to a SIP INVITE indicating a PTC participant joining the PTC chat group session.
when the participating PTC server of a PTC target forwards a SIP NOTIFY (received from the PTC server hosting the PTC chat group session) to the PTC target containing information about a PTC participant joining the PTC chat group session.

Table 7.5.2-9: Payload for PTCPartyJoin record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
participantPresenceStatus	Shall provide the Participant 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. True indicates PTC client is available, while false indicates PTC client is unavailable. Report when the Presence functionality is supported by the PTC server and the PTC server assumes the role of the watcher on behalf of the PTC target.	C
pTCMediaStreamAvail	Shall include this parameter to indicate if the PTC target is able/not able to receive media streams immediately. True indicates available for media, while false indicates not able to accept media.	M
pTCBearerCapability	Shall provide when known the media characteristics information elements of the PTC session, encoded in SDP format as per Section 5 of RFC 4566.	C

7.5.2.10 PTC party drop p. 241

The IRI-POI present in the PTC server hosting the PTC chat group session, when the PTC chat group is the PTC target, shall generate an xIRI containing a PTCPartyDrop record when the IRI-POI present in that PTC server detects that a PTC participant leaves the PTC chat group session that still remains active with other PTC participants. The PTCPartyDrop record shall also be generated when the IRI-POI present in the participating PTC server of the PTC target detects when a PTC Participant leaves an on-going PTC chat group session. Accordingly, the IRI-POI in the participating PTC server generates the xIRI when the following event is detected:

when the PTC server hosting a PTC chat group session, where the PTC chat group is the target, sends a SIP 200 OK in response to a SIP BYE with the PTC chat group session remaining active with other PTC participants.
when the participating PTC server of a PTC target forwards a SIP NOTIFY (received from the PTC server hosting the PTC chat group session) to the PTC target containing information about a PTC participant leaving the PTC chat group session.

Table 7.5.2-10: Payload for PTCPartyDrop record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCPartyDrop	Shall provide the identity of the participant that leaves the PTC session.	M
pTCParticipantPresenceStatus	Shall provide the Participant 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. True indicates PTC client is available, while false indicates PTC client is unavailable. Report when the Presence functionality is supported by the PTC server and the PTC server assumes the role of the watcher on behalf of the PTC target.	C

7.5.2.11 PTC party hold p. 241

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCPartyHold record when the IRI-POI present in the PTC server detects that an on-going PTC session is placed on hold or retrieved from hold by the PTC target or by a PTC participant in a PTC chat group, where the PTC chat group is the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server receives a SIP UPDATE or SIP re-INVITE from the PTC target and returns a SIP 200 OK to the PTC target for hold/resume operations.
when the PTC server hosting a PTC chat group, where PTC chat group is the PTC target, receives a SIP UPDATE or SIP re-INVITE from a PTC participant for hold/resume operations.

Table 7.5.2-11: Payload for PTCPartyHold record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCParticipants	Shall identify the individual PTC participants of the communication session, when known.	C
pTCHoldID	The identity of the PTC participant that placed the PTC session on hold or retrieved the held PTC session.	M
pTCHoldRetrieveInd	Shall indicate the PTC session is put on hold (i.e. deactivate Media Bursts or a PTC session is locked for talking/listening) or retrieved from hold. True indication equals placed on hold, false indication was retrieved from hold.	M

7.5.2.12 PTC media modification p. 242

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCMediaModification record when the IRI-POI present in the PTC server detects that a re-negotiation of the media parameters occurs during a PTC session involving the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server receives a SIP UPDATE or SIP reINVITE to indicate a PTC media modification on a PTC session being intercepted.

Table 7.5.2-12: Payload for PTCMediaModification record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessionInfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCMediaStreamAvail	Shall include this parameter to indicate if the PTC target is able/not able to receive media streams immediately. True indicates available for media, while false indicates not able to accept media.	M
pTCBearerCapability	Shall provide when known the media characteristics information elements of the PTC session, encoded in SDP format as per Section 5 of RFC 4566.	C

7.5.2.13 PTC group advertisement p. 242

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCGroupAdvertisement record when the IRI-POI present in the PTC server detects when a PTC target sends group advertisement information to a single PTC participant, a list of PTC participants, or to all members of a PTC chat group, as well as when a PTC target receives group advertisement information from a single PTC participant, a list of PTC participants, or from members of a PTC chat group using the group identity. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a SIP MESSAGE (containing group advertisement information) from a PTC target.
when the PTC server sends a SIP MESSAGE (containing group advertisement information) to the PTC target.

Table 7.5.2-13: Payload for PTCGroupAdvertisement record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCIDList	Shall provide Identities of each participant from the 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 when available.	C
pTCGroupAuthRule	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 PTC target. Report when the PTC target attempts a change or queries the access control list(s).	C
pTCGroupAdSender	Identifies the sender of the group advertisement.	M
pTCGroupNickname	The nickname is a human-readable tag (e.g. "display-name" in a SIP header associated with a PTC client or PTC group per OMA-TS-PoC_System_Description-V2_1-20110802-A [56]).	C

7.5.2.14 PTC floor control p. 243

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCFloorControl record when the IRI-POI present in the PTC server detects when the PTC target requests floor control (i.e. send media), when floor control is granted to PTC target, when floor control request from the PTC target is rejected/released, when the floor becomes open (e.g. idle), when the floor control request from the PTC target is queued, when the floor control request from the PTC target is dequeued, or when the floor control request is revoked. In addition, when the PTC chat group is the PTC target, the IRI-POI present in the PTC server hosting the PTC chat group shall generate an xIRI containing a PTCFloorControl record when the IRI-POI present in the PTC server detects any of the previously mentioned scenarios for all PTC participants participating in the PTC chat group session. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a TBCP Talk Burst Request from the PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, receives a TBCP Talk Burst Request from a PTC participant.
when the PTC server sends a TBCP Talk Burst Granted to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Granted to a PTC participant.
when the PTC server sends a TBCP Talk Burst Taken to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Taken to a PTC participant.
when the PTC server sends a TBCP Talk Burst Deny to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Deny to a PTC participant.
when the PTC server sends a TBCP Talk Burst Release to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Release to a PTC participant.
when the PTC server sends a TBCP Talk Burst Idle to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Idle to a PTC participant.
when the PTC server sends a TBCP Talk Burst Request Queue Status Response to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Request Queue Status Response to a PTC participant.
when the PTC server receives a TBCP Talk Burst Cancel from a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, receives a TBCP Talk Burst Cancel from a PTC participant.
when the PTC server sends a TBCP Talk Burst Revoke to a PTC target.
when the PTC server hosting the PTC chat group, where the PTC chat group is the PTC target, sends a TBCP Talk Burst Revke to a PTC participant.

Table 7.5.2-14: Payload for PTCFloorControl record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCSessioninfo	Shall provide PTC session information such as PTC Session URI and PTC Session type (e.g. on-demand, pre-established, ad-hoc, pre-arranged, group session).	M
pTCFloorActivity	Sequence of: "TBCP_Request": Received by the PTC server to request permission for the PTC target or PTC participant to send a talk burst. "TBCP_Granted": Used by the PTC server to notify the PTC target or PTC participant that it has been granted permission to send a talk burst. "TBCP_Deny": Used by the PTC server to notify a PTC target or PTC participant that it has been denied permission to send a talk burst. "TBCP_Idle": Used by the PTC server to notify the PTC target or PTC participant 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. "TBCP_Taken": Used by the PTC server to notify the PTC target or PTC participant that another PTC participant has been given permission to send a talk burst. "TBCP_Revoke": Used by the PTC server to revoke the media resource from the PTC target or PTC participant and can be used for pre-emption functionality but is also used by the system to prevent overly long use of the media resource. "TBCP_Queued": Indicates the request to talk is queued, if queued floor control is supported. Include identification of the PTC target or PTC participant that has the queued talk burst, if known. "TBCP_Release": Indicates the request to talk has completed.	M
pTCFloorSpeakerID	Include identification of the PTC participant that has initiated the talk burst, if known.	C
pTCMaxTBTime	Include the maximum duration value for the talk burst before the permission is revoked. This parameter is defined in seconds. Provide when known.	C
pTCQueuedFloorControl	Indicates if queuing is supported by the PTC server and the PTC target's device.	C
pTCQueuedPosition	Include if queue position in the TBCP is detected by the IRI-POI.	C
pTCTalkBurstPriority	If more than one level of priority is supported, indicates the talk burst priority level of the PTC target.	C
pTCTalkBurstReason	The reason for the denial or revoke of a Talk Burst. Provide when known.	C

7.5.2.15 PTC target presence p. 244

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCTargetPresence record when the IRI-POI present in the PTC server detects that the PTC server publishes network presence information to the Presence server on behalf of the PTC target. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server sends a SIP PUBLISH message to the Presence server based on the PTC target's PTC session involvement.

Table 7.5.2-15: Payload for PTCTargetPresence record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCTargetPresenceStatus	Shall provide the PTC target 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. True indicates PTC target is available, while false indicates PTC target is unavailable.	M

7.5.2.16 PTC participant presence p. 245

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCParticipantPresence record when the IRI-POI present in the PTC server (when it supports the Presence functionality and assumes the role of the Watcher on behalf of the PTC target) detects that the PTC server receives presence status notifications from the Presence servers after having subscribed to the PTC presence status of other PTC participants (i.e. participants in communication with the PTC target). Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server receives a SIP NOTIFY in response to a SIP SUBSCRIBE updating presence information for a participant.

Table 7.5.2-16: Payload for PTCParticipantPresence record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCParticipantPresenceStatus	Shall provide the Participant 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. True indicates PTC client is available, while false indicates PTC client is unavailable. Report when the Presence functionality is supported by the PTC server and the PTC server assumes the role of the watcher on behalf of the PTC target.	M

7.5.2.17 PTC list management p. 245

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCListManagement record when the IRI-POI present in the PTC server detects that the PTC target attempts to change their contact list/group list(s) or those lists are updated by the network. Accordingly, the IRI-POI in the PTC server generates the xIRI when the following events are detected:

when the PTC server receives a SIP PUBLISH from a PTC target to change the PTC target's contact list or group list(s).
when the PTC server receives a SIP NOTIFY from other PTC participants updating the PTC target's contact list or group list(s) (e.g. participant reachability).

Table 7.5.2-17: Payload for PTCListManagement record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCListManagementType	The "List Management Attempts" identify the type of list being managed by the target when available: ContactListManagementAttempt GroupListManagementAttempt ContactListManagementResult GroupListManagementResult Request unsuccessful For example, a) and b) are reported when PTC target attempts changes to their contact list and their 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 their contact list or their PTC group list(s).	C
pTCListManagementAction	Identifies the action requested by the PTC target to the contact lists or PTC group list(s). Report when PTC target attempts changes to his contact list or PTC group list(s): Create Modify Retrieve Delete Notify Also report when a notification is sent to the PTC target due to changes occurring to his contact list or PTC group list(s).	C
pTCListManagementFailure	Report when list management request is unsuccessful.	C
pTCContactID	Identity of the contact in the list. One contact per contact list or PTC group list. Report if known.	C
pTCIDList	Shall provide identities of 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. Report if known.	C
pTCHost	Identifies the PTC participant who has authority to initiate and administrate an active PTC group session. Provide when known.	C

7.5.2.18 PTC access policy p. 246

The IRI-POI present in the PTC server shall generate an xIRI containing a PTCAccessPolicy record when the IRI-POI present in the PTC server detects when the PTC 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). Accordingly, the IRI-POI in the PTC server generates the xIRI when the following event is detected:

when the PTC server receives a SIP PUBLISH from a PTC target to change the access control lists.

Table 7.5.2-18: Payload for PTCAccessPolicy record

Field Name	Description	M/C/O
pTCTargetInformation	Provide PTC target identity. At least one among MCPTT ID, IMPU, IMPI, InstanceIdentifierURN and PTCChatGroupID shall be provided for PTCTargetInformation.	M
pTCDirection	Indicates the direction of the session relative to the target: "toTarget" or "fromTarget".	M
pTCAccessPolicyType	Identifies the type of access policy list being managed or queried by the target when known: PTCUserAccessPolicyAttempt GroupAuthorizationRulesAttempt PTCUserAccessPolicyQuery GroupAuthorizationRulesQuery PTCUserAccessPolicyResult GroupAuthorizationRulesResult Request unsuccessful 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 target of changes to the access control list(s) or the request was unsuccessful.	C
pTCUserAccessPolicy	Identifies the action requested by the PTC target to the PTC user or group access policy: Allow Incoming PTC session request Block Incoming PTC session request Allow Auto Answer Mode Allow Override Manual Answer Mode Report when action requested to the PTC user access policy. Report when the PTC target attempts a change or queries the access control list(s).	C
pTCGroupAuthRule	Identifies the action requested by the PTC target to the PTC Group Authorization Rules: Allow Initiating PTC session Block Initiating PTC session Allow Joining PTC session Block Joining PTC session Allow Add Participants Block Add Participants Allow Subscription PTC session state Block Subscription PTC session state Allow Anonymity Forbid Anonymity Report when action requested to the PTC group authorization rules by the PTC target. Report when the PTC target attempts a change or queries the access control List(s).	C
pTCContactID	Identity of the contact in the list. One contact per contact list or PTC group list. Report if known.	C
pTCAccessPolicyFailure	Reports the reason for failure when access policy request is unsuccessful.	C

7.5.3 IRI and CC Generation p. 247

7.5.3.1 Generation of IRI over LI_HI2 p. 247

When an xIRI is received over LI_X2 from the IRI-POI in the PTC server, the MDF2 shall generate the corresponding IRI message and deliver it over LI_HI2 without undue delay. The IRI shall contain a copy of the record received over LI_X2. This record may be enriched with any additional information available at the MDF2 (e.g. additional location information).

7.5.3.2 Generation of CC over LI_HI3 p. 248

When xCC is received over LI_X3 from the CC-POI in the PTC server, the MDF3 shall populate the threeGPP33128DefinedCC field with a CCPayload structure containing PTCCCPDU and send it over LI_HI3 interface to LEMF without undue delay.

The PTC media contents are structured in a CC payload as formatted in clause 5.5.3 of the present document.