13 List of system parameters

24.3343GPPProximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspectsRelease 17Stage 3TS

13.1 General

The description of timers in table 13.2.1 and table 13.2.2 should be considered a brief summary. The complete descriptions of the timers are in the procedures defined in subclause 5 and subclause 6.

13.2 Timers of ProSe direct services procedures

Table 13.2.1: ProSe direct services timers – UE side

TIMER NUM.

TIMER VALUE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T4000

NOTE 1

Upon receiving a ProSe Application Code with an associated T4000 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the <response-announce> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "announce", as described in subclause 6.2.2.4.

Upon receiving a ProSe Application Code with an associated T4000 timer in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.7.3.

Upon receiving a new T4000 timer value for the same ProSe Application Code or receiving a new Timer associated with a new ProSe Application Code for the same ProSe Application ID in a DISCOVERY_RESPONSE message.

When the UE selects a new PLMN.

Upon receiving a <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.7.3.

Stop announcing the associated ProSe Application Code over the PC5 interface and re-initiate the announce request procedure if the request from upper layers to announce the ProSe Application ID corresponding to the associated ProSe Application Code is still in place.

T4002

NOTE 2

Upon receiving a Discovery Filter with an associated T4002 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the <response-monitor> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "monitor", as described in subclause 6.2.3.4.

Upon receiving a Discovery Filter in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.7.3.

Upon receiving a new T4002 timer value for the same Discovery Filter in a DISCOVERY_RESPONSE message.

Upon receiving a <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.7.3.

Stop using the associated Discovery Filter for ProSe direct discovery monitoring over the PC5 interface and re-initiate the monitor request procedure, if the request from upper layers to monitor the ProSe Application ID corresponding to the associated Discovery Filter is still in place.

T4004

NOTE 3

Upon receiving a T4004 timer in a MATCH_REPORT_ACK message whose transaction ID contained in the <match-ack> element matches the value sent by the UE in a MATCH_REPORT message, as described in subclause 6.2.4.4.

Upon receiving a new T4004 timer value for the same ProSe Application Code in a MATCH_REPORT_ACK message.

Upon receiving a MATCH_REPORT_ACK message with a <match-reject> element containing PC3 Control Protocol cause value is #5.

The UE may inform the upper layers that the corresponding ProSe Application ID is no longer matched.

T4005

NOTE 4

Upon receiving a monitoring, announcing, discoveree operation, discoverer operation or communication policy for a given PLMN with an associated T4005 value in the ProSe service authorisation as described in subclause 5.1.3.

When the service authorisation for the corresponding PLMN is revoked by the ProSe Function.

Upon receiving a new T4005 timer value for the same operation (monitoring, announcing, discoveree operation, discoverer operation or communication) in the same PLMN.

Stop the monitoring, announcing, discoveree, discoverer or communication operation in the corresponding PLMN and re-initiate the service authorisation procedure if the UE wants to continue performing announcing, monitoring, discoveree, discoverer or communication operation in that

PLMN.

T4006

NOTE 3

Upon receiving a T4006 timer in a MATCH_REPORT_ACK message whose transaction ID contained in the <match-ack> element matches the value sent by the UE in a MATCH_REPORT message, as described in subclause 6.2.4.4.

Upon receiving a new T4006 timer value for the same ProSe Application Code in a MATCH_REPORT_ACK message.

When the corresponding T4004 timer for the ProSe Application Code is stopped or expires.

The UE needs to

send a Match Report on next instance it detects the corresponding ProSe Application Code.

T4007

NOTE 5

Upon receiving a ProSe Restricted Code or ProSe Restricted Code Prefix with an associated T4007 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the <restricted-announce-response> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "announce" and the Discovery Type set to "Restrict discovery", as described in subclause 6.2.2A.4.

Upon receiving a ProSe Restricted Code with an associated T4007 timer in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.6.3.

Upon receiving a new T4007 timer value for the same ProSe Restricted Code or ProSe Restricted Code Prefix, or upon receiving a new T4007 timer associated with a new ProSe Restricted Code or ProSe Restricted Code Prefix for the same RPAUID in a DISCOVERY_RESPONSE message.

When the UE selects a new PLMN.

Upon receiving a ProSe Restricted Code with an associated T4007 timer in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.6.3.

Stop announcing the associated ProSe Restricted Code over the PC5 interface if the ProSe Restricted Code is already allocated; and re-initiate the announce request procedure if the request from upper layers to announce the RPAUID corresponding to the associated ProSe Restricted Code is still in place.

T4009

NOTE 6

Upon receiving a Restricted Discovery Filter with an associated T4009 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the <restricted-monitor-response> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "monitor" and the Discovery Type set to "Restrict discovery", as described in subclause 6.2.3A.4.

Upon receiving a Restricted Discovery Filter in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.6.2.

Upon receiving one or more new T4009 timer values for the same discovery entry in a DISCOVERY_RESPONSE message.

Upon receiving a Restricted Discovery Filter in the Update Info in the <discovery-update-request> element in a DISCOVERY_UPDATE_REQUEST message and the Discovery Entry ID in the <discovery-update-request> element is known, as described in subclause 6.2.6.2.

Stop using the associated Restricted Discovery Filter for restricted ProSe direct discovery monitoring over the PC5 interface and re-initiate the monitor request procedure, if the request from upper layers to monitor the corresponding discovery target is still in place.

T4011

NOTE 7

Upon receiving a ProSe Response Code and Discovery Query Filters with an associated T4011 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the < restricted-discoveree-response > element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "response" and the Discovery Type set to "Restrict discovery", as described in subclause 6.2.2B.4.

Upon receiving a new T4011 timer value for the same discovery entry in a DISCOVERY_RESPONSE message.

When the UE selects a new PLMN.

Stop announcing the associated ProSe Response Code or monitoring with the associated Discovery Query Filter(s) over the PC5 interface and re-initiate the discoveree request procedure if the request from upper layers to announce the RPAUID in Model B is still in place.

T4013

NOTE 8

Upon receiving a ProSe Query Code and Discovery Response Filters with an associated T4013 timer in a DISCOVERY_RESPONSE message whose transaction ID contained in the < restricted-discoverer-response > element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "query" and the Discovery Type set to "Restrict discovery", as described in subclause 6.2.3B.4.

Upon receiving a new T4013 timer value for the same discovery entry in a DISCOVERY_RESPONSE message.

Stop announcing the associated ProSe Query Code or monitoring with the associated Discovery Response Filter(s) over the PC5 interface and re-initiate the discoverer request procedure if the request from upper layers to query for the same targets in Model B is still in place.

T4015

NOTE 4

Upon receiving a ProSe Discovery UE ID with an associated T4015 value in the ProSe service authorisation as described in subclause 5.1.3.

Upon receiving a new ProSe Discovery UE ID.

Stop performing ProSe restricted discovery and re-initiate the service authorisation procedure if the UE wants to continue performing ProSe restricted discovery.

T4016

NOTE 13

Upon receiving a T4016 timer in a MATCH_REPORT_ACK message whose transaction ID contained in the <restricted-match-ack> element matches the value sent by the UE in a MATCH_REPORTmessage, as described in subclause 6.2.4A.4 or 6.2.4B.4.

Upon receiving a new T4016 timer value for the same ProSe Restricted Code or ProSe Response Code in a MATCH_REPORT_ACK message.

Upon receiving a MATCH_REPORT_ACK message with a <match-reject> element containing PC3 Control Protocol cause value #5.

The UE may inform the upper layers that the corresponding RPAUID is no longer matched.

T4017

NOTE 13

Upon receiving a T4017 timer in a MATCH_REPORT_ACK message whose transaction ID contained in the <restricted-match-ack> element matches the value sent by the UE in a MATCH_REPORTmessage, as described in subclause 6.2.4A.4.

Upon receiving a new T4017 timer value for the same ProSe Restricted Code or ProSe Response Code in a MATCH_REPORT_ACK message.

When the corresponding T4016 timer for the ProSe Restricted Code or ProSe Response Code is stopped or expires.

The UE needs to

send a Match Report on next instance it detects the corresponding ProSe Restricted Code or ProSe Response Code.

T4100

Upon sending a DIRECT_COMMUNICATION_REQUEST message

Upon receiving a DIRECT_COMMUNICATION_ACCEPT or DIRECT_COMMUNICATION_REJECT message from the target UE

Retransmission of DIRECT_COMMUNICATION_REQUEST message

T4101

DIRECT_COMMUNICATION_KEEPALIVE message sent

Upon Receiving a DIRECT_COMMUNICATION_KEEPALIVE_ACK message or other PC5 Signaling message or user data from the peer UE

Retransmission of DIRECT_COMMUNICATION_KEEPALIVE message

T4102

Upon Receiving a DIRECT_COMMUNICATION_KEEPALIVE_ACK message, or other PC5 Signaling message, or any user data from the peer UE

Upon receiving an upper layer request to check whether the direct link is alive and sending out a DIRECT_COMMUNICATION_KEEPALIVE message

Send a DIRECT_COMMUNICATION_KEEPALIVE message

T4103

Upon sending a DIRECT_COMMUNICATION_RELEASE message

Upon receiving a DIRECT_COMMUNICATION_RELEASE_ACCEPT message from the peer UE.

Stop using the corresponding direct link for one-to-one communication

T4104

NOTE 9

Upon receiving a ProSe Layer2 Group ID with an associated T4104 timer in a TMGI_MONITORING_RESPONSE message, as described in subclause 10.5.

Upon receiving one or more new T4104 timer values for the same ProSe Layer2 Group ID in a TMGI_MONITORING_RESPONSE message.

Re-initiate the TMGI monitoring request procedure, if the request from upper layers to receive the MBMS content for the given TMGI is still in place.

T4105

NOTE 10

Upon assigning a ProSe Layer2 Group ID with an associated T4104 value to the remote UE, as described in subclause 10.5.

Upon sending a new TMGI_MONITORING_RESPONSE for the same TMGI.

Delete the associated TMGI and MBMS SAI list.

T4106

NOTE 11

Upon receiving a T4106 value in a CELL_ID_ANNOUNCEMENT_RESPONSE message as described in subclause 10.6.

Upon receiving one or more new T4106 timer values in a CELL_ID_ANNOUNCEMENT_RESPONSE message.

Re-initiate the cell ID announcement request procedure, if the upper layer application still needs to obtain ECGI of the cell serving the ProSe UE-to-network relay.

T4107

NOTE 12

Upon sending a CELL_ID_ANNOUNCEMENT_RESPONSE message as described in subclause 10.6.

Upon sending a new CELL_ID_ANNOUNCEMENT_RESPONSE message.

Stop the cell ID announcement in the PC5_DISCOVERY message for Relay Discovery Additional Information.

T4108

Upon receiving a Maximum Inactivity Period IE in DIRECT_COMMUNICATION_KEEPALIVE message; or when the UE has no more message or user data to send over the direct link.

Upon sending or receiving a PC5 Signaling message or user data over the direct link

Either initiate the direct link keepalive procedure or direct link release procedure.

T4109

Upon sending the PC5_DISCOVERY message for UE-to-Network Relay Discovery Solicitation used to trigger the PC5_DISCOVERY message signal strength measurement between the UE and the ProSe UE-to-network relay UE with which the UE has a link established.

Upon Receiving the PC5_DISCOVERY message for UE-to-Network Relay Discovery Response from the ProSe UE-to-network relay UE with which the UE has a link established,

Retransmission the PC5_DISCOVERY message for UE-to-Network Relay Discovery Solicitation,

T4110

Upon Receiving the PC5_DISCOVERY message for UE-to-Network Relay Discovery Response from the ProSe UE-to-network relay UE with which the UE has a link established,

Upon releasing the direct link with a ProSe UE-to-network relay UE.

Send the PC5_DISCOVERY message for UE-to-Network Relay Discovery Solicitation used to trigger the PC5_DISCOVERY message signal strength measurement between the UE and the ProSe UE-to-network relay UE with which the UE has a link established,

T4111

Upon sending a DIRECT_SECURITY_MODE_COMMAND message.

Upon receiving the DIRECT_SECURITY_MODE_COMPLETE or DIRECT_SECURITY_MODE_REJECT message.

Sending a DIRECT_COMMUNICATION_REJECT if the security mode control procedure is triggered by the DIRECT_COMMUNICATION_REQUEST message from the peer UE.

T4112

Upon sending a DIRECT_REKEYING_REQUEST message.

Upon receiving the DIRECT_REKEYING_RESPONSE message or receiving a DIRECT_REKEYING_REQUEST message from the peer UE and satisfying the conditions specified in subclause 10.4.8.

Retransmission of DIRECT_REKEYING_REQUEST message.

T4113

Upon sending a DIRECT_REKEYING_TRIGGER message.

Upon receiving the DIRECT_REKEYING_REQUEST message from the remote UE.

Retransmission of DIRECT_REKEYING_TRIGGER message.

NOTE 1: The value of this timer is provided by the ProSe Function during the announce request and discovery update procedure for open ProSe direct discovery.

NOTE 2: The value of this timer is provided by the ProSe Function during the monitor request and discovery update procedure for open ProSe direct discovery.

NOTE 3: The value of this timer is provided by the ProSe Function during the match report procedure for open ProSe direct discovery.

NOTE 4: The value of this timer is provided by the ProSe Function during service authorisation procedure.

NOTE 5: The value of this timer is provided by the ProSe Function during the announce request and discovery update procedure for restricted ProSe direct discovery model A.

NOTE 6: The value of this timer is provided by the ProSe Function during the monitor request and discovery update procedure for restricted ProSe direct discovery model A.

NOTE 7: The value of this timer is assigned by the ProSe Function during the discoveree request procedure for restricted ProSe direct discovery model B.

NOTE 8: The value of this timer is assigned by the ProSe Function during the discoverer request procedure for restricted ProSe direct discovery model B.

NOTE 9: The value of this timer is provided by the ProSe UE-to-network relay UE during the TMGI monitoring request procedure.

NOTE 10: The value of this timer is assigned by the ProSe UE-to-network relay UE during the TMGI monitoring request procedure

NOTE 11: The value of this timer is provided by the ProSe UE-to-network relay UE during the cell ID announcement request procedure.

NOTE 12: The value of this timer is assigned by the ProSe UE-to-network relay UE during the cell ID announcement request procedure.

NOTE 13: The value of this timer is provided by the ProSe Function during the match report procedure for restricted ProSe direct discovery model  A or match report procedure for restricted ProSe direct discovery model B.

Table 13.2.2: ProSe direct services timers – ProSe Function side

TIMER NUM.

TIMER VALUE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T4001

NOTE 1

Upon assigning a ProSe Application Code with an associated T4000 value to the UE, as described in subclause 6.2.2.3 and subclause 6.2.7.2.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "announce" for the same ProSe Application ID.

Delete the association between the UE, the requested ProSe Application ID and the corresponding ProSe Application Code allocated by the ProSe Function.

T4003

NOTE 2

Upon assigning a Discovery Filter with an associated T4002 value to the UE, as described in subclause 6.2.3.3 and subclause 6.2.7.2.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "monitor" for the same ProSe Application ID

Delete the association between the UE, the requested ProSe Application ID and the corresponding Discovery Filter allocated by the ProSe Function.

T4008

NOTE 3

Upon assigning a ProSe Restricted Code or ProSe Restricted Code Prefix with an associated T4007 value to the UE, as described in subclause 6.2.2A.3 and subclause 6.2.6.3.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "announce" for the same RPAUID or discovery entry ID. Set to be the same as the discovery entry in which this timer is running.

Delete the association between the UE, the RPAUID and the corresponding ProSe Restricted Code or ProSe Restricted Code Prefix allocated by the ProSe Function.

T4010

NOTE 4

Upon assigning a Restricted Discovery Filter with an associated T4009 value to the UE, as described in subclause 6.2.3A.3 and subclause 6.2.6.2.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "monitor" and discovery entry ID set to be the same as the discovery entry in which this timer is running.

Delete the association between the UE, the RPAUID and the corresponding Restricted Discovery Filter allocated by the ProSe Function.

T4012

NOTE 5

Upon assigning a ProSe Query Code, ProSe Response Code and Discovery Query Filter(s) with an associated T4011 value to the UE, as described in subclause 6.2.2B.3.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "response" for the same RPAUID or discovery entry ID. Set to be the same as the discovery entry in which this timer is running.

Delete the discovery entry in discoveree UE context which contains association between the UE, the RPAUID and the corresponding ProSe Query Code, ProSe Response Code, Discovery Query Filter(s) allocated by the ProSe Function.

T4014

NOTE 6

Upon retrieving the ProSe Query Code, ProSe Response Code from discoveree UE context and assigning Discovery Response Filter(s) with an associated T4013 value to the UE, as described in subclause 6.2.3B.3.

Upon receiving a new DISCOVERY_REQUEST message from the UE with the command set to "query" and discovery entry ID set to be the same as the discovery entry in which this timer is running.

Delete the discovery entry in discoverer UE context which contains the association between the UE, the RPAUID and the corresponding Discovery Response Filter(s) allocated by the ProSe Function.

T4018

NOTE 7

Upon assigning a ProSe Discovery UE ID with an associated T4015 value in the ProSe service authorisation as described in subclause 5.1.3.

Upon assigning a new ProSe Discovery UE ID for the same UE.

Delete the UE context related to the restricted discovery.

NOTE 1: The value of this timer is assigned by the ProSe Function during the announce request and discovery update procedure for open ProSe direct discovery.

NOTE 2: The value of this timer is assigned by the ProSe Function during the monitor request and discovery update procedure for open ProSe direct discovery.

NOTE 3: The value of this timer is assigned by the ProSe Function during the announce request and discovery update procedure for restricted ProSe direct discovery model A.

NOTE 4: The value of this timer is assigned by the ProSe Function during the monitor request and discovery update procedure for restricted ProSe direct discovery model A.

NOTE 5: The value of this timer is assigned by the ProSe Function during the discoveree request procedure for restricted ProSe direct discovery model B.

NOTE 6: The value of this timer is assigned by the ProSe Function during the discoverer request procedure for restricted ProSe direct discovery model B.

NOTE 7: The value of this timer is assigned by the ProSe Function during the service authorisation procedure.

NOTE: Multiple timers T4001, T4003, T4008, T4010, T4012 and T4014 can run simultaneously in the ProSe Function.

Annex A (informative):
IANA registrations