19.2.2 ProSe Direct Discovery Announcing/Pre-configured authorisation / Announcing and SLSS transmission in RRC_IDLE / Handling of validity timers / Utilisation of the resources of different cells/PLMNs

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

19.2.2.1 Test Purpose (TP)

(1)

with { UE supporting ProSe direct discovery announcing }

ensure that {

when { UE performs Attach procedure, or, Normal tracking area updating procedure }

then { UE announces its ProSe capabilities }

}

(2)

ensure that {

when { UE is triggered by an upper layer application to announce a ProSe Application ID and the UE has no valid corresponding ProSe Application Code for that upper layer application }

then { UE does not initiate Announce request procedure }

}

(3)

ensure that {

when { UE is triggered by an upper layer application to announce a ProSe Application ID and the UE has no valid corresponding ProSe Application Code for that upper layer application }

then { UE initiates and successfully completes an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements }

}

(4)

with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }

ensure that {

when { UE is in RRC_IDLE, and, UE is configured with discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased }

then { UE is able to transmit the sidelink discovery announcement using the assigned/configured resources in Cell1/f1/PLMN1 selecting for the transmission an entry of discTxPoolCommon for which RSRP measurement of the serving is in-between threshLow and threshHigh }

}

(5)

ensure that {

when { UE moves to RRC_IDLE on a new Cell2/f1/PLMN1 which provides resources for sidelink discovery announcements (poolSelection provided in the SystemInformationBlockType19/discTxPoolCommon is NOT set to rsrpBasedUE) }

then { UE does not initiate a new Announce request procedure, and, is able to transmit sidelink discovery announcements using the assigned/configured resources in Cell2/f1/PLMN1 }

}

(6)

with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell2/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }

ensure that {

when { UE moves to a new Cell4/f1/PLMN2 authorized for ProSe Direct Discovery Announcing and broadcasting SystemInformationBlockType19 indicating the provision of Direct Discovery announcing resources on the serving PLMNs }

then { UE initiates and successfully completes an Announce request procedure }

}

(7)

with { UE capable of SLSS transmission, and, being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }

ensure that {

when { UE is in RRC_IDLE, and, networkControlledSyncTx is not configured, and, syncTxThreshIC is included in SystemInformationBlockType19, and, the RSRP measurement of the serving cell is below the value of syncTxThreshIC }

then { UE transmits SLSS }

}

(8)

with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }

ensure that {

when { timer T4000 expires }

then { UE initiates and successfully completes an Announce request procedure }

}

(9) Void

(10) Void

(11)

ensure that {

when { UE moves to a new Cell11/f1/PLMN3 broadcasting SystemInformationBlockType19 providing resources for sidelink discovery announcements, and, the UE is not authorized for ProSe Direct Discovery announcing on this PLMN }

then { the UE does not initiate Announce request procedure, and, does not announce over the PC5 in the assigned resources in Cell11/f1/PLMN3 }

}

19.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.303, clause 5.3.1.1, TS 24.301, clauses 5.5.1.2.2, 5.5.3.2.2, 5.6.1.1, TS 24.334, clauses 5.1.1, 5.1.2, 6.1.1, 6.2.2.2, 6.2.2.4, TS 36.331, clauses 5.2.2.4, 5.2.2.26, 5.3.3.1a, 5.10.2.1, 5.10.2.2, 5.10.2.3, 5.10.6, 5.10.7.1, 5.10.7.2, 5.10.7.3. Unless otherwise stated these are Rel-12 requirements.

[TS 23.303, clause 5.3.1.1]

The UE can act as "announcing UE" only in the band designated by the serving PLMN but may act as a "monitoring" UE also in the resources of the serving PLMN and Local PLMNs.

ProSe-enabled UEs which have obtained authorization to participate in ProSe Direct Discovery procedures shall not continue in participating in ProSe Direct Discovery procedures as soon as they detect loss of E-UTRA coverage in the serving PLMN.

[TS 24.301, clause 5.5.1.2.2]

If the UE supports ProSe direct discovery, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct discovery bit to "ProSe direct discovery supported" in the UE network capability IE of the ATTACH REQUEST message.

[TS 24.301, clause 5.5.3.2.2]

The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME,

…

b) when the periodic tracking area updating timer T3412 expires;

…

If the UE has to request resources for ProSe direct discovery or Prose direct communication (see 3GPP TS 36.331 [22]), then the UE shall set the "active" flag to 1 in the TRACKING AREA UPDATE REQUEST message.

…

For all cases except case b, if the UE supports ProSe direct discovery, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct discovery bit to "ProSe direct discovery supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message.

[TS 24.301, clause 5.6.1.1]

The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED mode and establish the radio and S1 bearers when user data or signalling is to be sent. Another purpose of this procedure is to invoke MO/MT CS fallback or 1xCS fallback procedures.

This procedure is used when:

…

– the UE has to request resources for ProSe direct discovery or Prose direct communication.

…

The UE shall invoke the service request procedure when:

…

l) the UE in EMM-IDLE mode has to request resources for ProSe direct discovery or Prose direct communication (see 3GPP TS 36.331 [22]).

[TS 24.334, clause 5.1.1]

The service authorisation for ProSe direct discovery and ProSe direct communication determines whether the UE is authorised to use ProSe direct discovery announcing or ProSe direct discovery monitoring or both, and to use ProSe direct communication, in a particular PLMN or when not served by E-UTRAN. In this release of the specification, ProSe direct communication is supported only for Public Safety ProSe-enabled UE. The service authorisation is either:

1) pre-configured in the UE. The pre-configured service authorisation may be stored in the ME, or in the USIM as specified in 3GPP TS 31.102 [17], or in both the ME and the USIM. If both the ME and the USIM contain the same parameters, the values stored in the USIM shall take precedence. The UE shall not use the pre-configured service authorisation if the contents of the USIM indicate that the UE is not authorised to use them (see 3GPP TS 31.102 [17]); or

2) transferred between the UE and the ProSe Function over the PC3 interface with the ProSe Direct Services Provisioning Management Object or the ProSe Public Safety Direct Services Provisioning Management Object as specified in 3GPP TS 24.333 [9].

…

The service authorisation provided by the ProSe Function of the HPLMN for ProSe direct discovery contains a list of PLMNs in which the UE is authorised to use ProSe direct discovery.

…

The UE discovers the IP address of the ProSe Functions of the HPLMN as specified in subclause 5.1.2.

[TS 24.334, clause 5.1.2]

The IP address of the ProSe function in the HPLMN may be pre-configured in the UE and in this case, the UE may use the pre-configured IP address. Alternatively, the FQDN of the ProSe Function in the HPLMN may be self-constructed by the UE, i.e. derived from the PLMN ID of the HPLMN. The UE may perform DNS lookup as specified in IETF RFC 1035 [10].

[TS 24.334, clause 6.1.1]

The UE and ProSe Function shall use HTTP 1.1 as specified in IETF RFC 7230 [18] and IETF RFC 7231 [19] as the transport protocol for ProSe messages over the PC3 interface. The ProSe messages described here shall be included in the body of either an HTTP request message or an HTTP response message. The following rules apply:

– The UE initiates ProSe transactions with an HTTP request message containing the PC3 request(s);

– The ProSe Function responds to the requests with an HTTP response message containing the PC3 response(s) for the PC3 request(s); and

– HTTP POST methods are used for PC3 direct discovery procedures.

Optionally, the operator can configure the UE with configuration parameters for establishment of the PDN connection for reaching the HPLMN ProSe Function. If the UE is configured with the configuration parameter for establishment of the PDN connection for reaching the HPLMN ProSe Function (see 3GPP TS 24.333 [9]):

a) if a PDN connection for reaching the HPLMN ProSe Function is not established yet, the UE shall establish the PDN connection for reaching the HPLMN ProSe Function according to the UE configuration and shall send the HTTP request message via the PDN connection for reaching the HPLMN ProSe Function; and

b) if a PDN connection for reaching the HPLMN ProSe Function is already established (e.g. either due to other ProSe feature or due to other application), the UE shall send the HTTP request message via the PDN connection for reaching the HPLMN ProSe Function;

[TS 24.334, clause 6.2.2.2]

Before initiating the announce request procedure, the UE is configured with the data structure of the ProSe Application IDs appropriate for its HPLMN. This step is performed using mechanisms out of scope of 3GPP.

If the UE is authorised to perform ProSe direct discovery announcing in the registered PLMN, it shall initiate an announce request procedure:

a) when the UE is triggered by an upper layer application to announce a ProSe Application ID and the UE has no valid corresponding ProSe Application Code for that upper layer application;

b) when the validity timer T4000 assigned by the ProSe Function to a ProSe Application Code has expired and the request from upper layers to announce the ProSe Application ID corresponding to that ProSe Application Code is still in place; or

c) when the UE selects a new PLMN while announcing a ProSe Application Code and the UE is authorised for ProSe direct discovery announcing in the new PLMN.

When the UE selects a new PLMN while announcing a ProSe Application Code and the UE is not yet authorised for ProSe direct discovery announcing in the new PLMN, the UE shall initiate an announce request procedure only after the UE is authorised for ProSe direct discovery announcing in the new PLMN.

NOTE 1: To ensure service continuity if the UE needs to keep announcing a ProSe Application Code corresponding to the same ProSe Application ID, the UE can initiate the announce request procedure before the TTL timer T4000 assigned by the ProSe Function for a Prose Application Code expires.

The UE initiates the announce request procedure by sending a DISCOVERY_REQUEST message with a new transaction ID, the ProSe Application ID set to the ProSe Application ID received from upper layers, the command set to "announce", the UE identity set to the UE’s IMSI, and the Application Identity set to the Application Identity of the upper layer application that requested the announcing.

NOTE 2: A UE can include one or multiple transactions in one DISCOVERY_REQUEST message for different ProSe Application IDs, and receive corresponding <response-announce> element or <response-reject> element in a DISCOVERY_RESPONSE message for each respective transaction. In the following description of the announce request procedure, only one transaction is included.

Figure 6.2.2.2.1 illustrates the interaction of the UE and the ProSe Function in the announce request procedure.

Figure 6.2.2.2.1: Announce request procedure

[TS 24.334, clause 6.2.2.4]

Upon receipt of the DISCOVERY_RESPONSE message, if the 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", the UE shall, for each ProSe Application Code received in the DISCOVERY_RESPONSE message, stop the validity timer T4000 if running and start the validity timer T4000 with the received value. Otherwise the UE shall discard the DISCOVERY_RESPONSE message and shall not perform the procedures below.

The UE may perform direct discovery announcing as described below.

The UE requests the parameters from the lower layers for Prose direct discovery announcing (see 3GPP TS 36.331 [12]). The UE shall perform direct discovery announcing only if the lower layers indicate that ProSe direct discovery is supported by the network. If the UE in EMM-IDLE mode has to request resources for ProSe direct discovery announcing as specified in 3GPP TS 36.331 [12], the UE shall perform a service request procedure or tracking area update procedure as specified in 3GPP TS 24.301 [11]. The UE shall obtain the UTC time for the next discovery transmission opportunity for ProSe direct discovery from the lower layers.

If a valid UTC time is obtained, the UE shall generate the UTC-based counter corresponding to this UTC time as specified in subclause 12.2.2.18, and then use the UTC-based counter to compute the MIC field for the PC5_DISCOVERY message as described in 3GPP TS 33.303 [6].

The UE shall use the ProSe Application Code received in the DISCOVERY_RESPONSE message, along with the MIC and the four least significant bits of the UTC-based counter, in order to construct a PC5_DISCOVERY message, according to the format defined in subclause 11.2.5.

The UE then passes the PC5_DISCOVERY message to the lower layers for transmission if:

– the UE is currently authorised to perform direct discovery announcing in the registered PLMN;

– the validity timer T4000 for the allocated ProSe Application Code has not expired; and

– a request from upper layers to announce the ProSe Application ID associated with both the ProSe Application Code and the authorised Application Identity is still in place.

The UE shall ensure that it keeps on passing PC5_DISCOVERY messages to the lower layers for transmission until the validity timer T4000 of the ProSe Application Code expires. How this is achieved is left up to UE implementation.

During the announcing operation, if one of the above conditions is no longer met, the UE may instruct the lower layers to stop announcing. When the UE stops announcing, if the lower layers indicate that the UE is required to send a discovery indication to the eNodeB and the UE is in EMM-CONNECTED mode, the UE shall trigger the corresponding procedure in lower layers as specified in 3GPP TS 36.331 [12].

[TS 36.331, clause 5.2.2.4]

1> if the UE is capable of sidelink discovery and is configured by upper layers to receive or transmit sidelink discovery announcements on the primary frequency:

2> if schedulingInfoList indicates that SystemInformationBlockType19 is present and the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType19;

[TS 36.331, clause 5.2.2.26]

Upon receiving SystemInformationBlockType19, the UE shall:

1> if SystemInformationBlockType19 message includes the discConfig:

…

2> if SystemInformationBlockType19 message includes the discTxPoolCommon; and the UE is in RRC_IDLE:

3> from the next discovery period, as defined by discPeriod, use the resources indicated by discTxPoolCommon for sidelink discovery announcement, as specified in 5.10.6;

[TS 36.331, clause 5.3.3.1a]

For sidelink discovery an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit sidelink discovery announcements:

2> if SystemInformationBlockType19 is broadcast by the cell on which the UE camps: and if the valid version of SystemInformationBlockType19 does not include discTxPoolCommon;

NOTE: Upper layers initiate an RRC connection. The interaction with NAS is left to UE implementation.

[TS 36.331, clause 5.10.2.1]

Figure 5.10.2-1: Sidelink UE information

The purpose of this procedure is to inform E-UTRAN that the UE is interested or no longer interested to receive sidelink communication or discovery, as well as to request assignment or release of transmission resources for sidelink communication or discovery announcements.

[TS 36.331, clause 5.10.2.2]

A UE capable of sidelink communication or discovery that is in RRC_CONNECTED may initiate the procedure to indicate it is (interested in) receiving sidelink communication or discovery in several cases including upon successful connection establishment, upon change of interest, upon change to a PCell broadcasting SystemInformationBlockType18 or SystemInformationBlockType19. A UE capable of sidelink communication or discovery may initiate the procedure to request assignment of dedicated resources for the concerned sidelink communication transmission or discovery announcements.

NOTE 1: A UE in RRC_IDLE that is configured to transmit sidelink communication/ discovery announcements, while SystemInformationBlockType18/ SystemInformationBlockType19 does not include the resources for transmission (in normal conditions), initiates connection establishment in accordance with 5.3.3.1a.

Upon initiating the procedure, the UE shall:

…

1> if SystemInformationBlockType19 is broadcast by the PCell:

2> ensure having a valid version of SystemInformationBlockType19 for the PCell;

…

2> if the UE is configured by upper layers to transmit sidelink discovery announcements:

3> if the UE did not transmit a SidelinkUEInformation message since entering RRC_CONNECTED state; or

3> if since the last time the UE transmitted a SidelinkUEInformation message the UE connected to a PCell not broadcasting SystemInformationBlockType19; or

3> if the last transmission of the SidelinkUEInformation message did not include discTxResourceReq; or if the sidelink discovery announcement resources required by the UE have changed (i.e. resulting in a change of discTxResourceReq) since the last transmission of the SidelinkUEInformation message:

4> initiate transmission of the SidelinkUEInformation message to indicate the sidelink discovery announcement resources required by the UE in accordance with 5.10.2.3;

2> else:

3> if the last transmission of the SidelinkUEInformation message included discTxResourceReq:

4> initiate transmission of the SidelinkUEInformation message to indicate it does no longer require sidelink discovery announcement resources in accordance with 5.10.2.3;

[TS 36.331, clause 5.10.2.3]

The UE shall set the contents of the SidelinkUEInformation message as follows:

…

1> if SystemInformationBlockType19 is broadcast by the PCell:

…

2> if the UE is configured by upper layers to transmit sidelink discovery announcements:

3> include discTxResourceReq and set it to indicate the number of discovery messages for sidelink discovery announcement(s) for which it requests E-UTRAN to assign dedicated resources;

The UE shall submit the SidelinkUEInformation message to lower layers for transmission.

[TS 36.331, clause 5.10.6]

A UE capable of sidelink discovery that is configured by upper layers to transmit sidelink discovery announcements shall:

NOTE 1: In case the configured resources are insufficient it is up to UE implementation to decide which sidelink discovery announcements to transmit.

1> if the UE’s serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is suitable as defined in TS 36.304 [4]:

…

2> else if T300 is not running (i.e. UE in RRC_IDLE, announcing via serving cell):

3> if SystemInformationBlockType19 of the serving cell includes discTxPoolCommon:

4> if poolSelection is set to rsrpBased:

5> select an entry of discTxPoolCommon for which RSRP measurement of the serving cell is in-between threshLow and threshHigh;

4> else:

5> randomly select, using a uniform distribution, an entry of discTxPoolCommon;

4> configure lower layers to transmit the sidelink discovery announcement using the selected pool of resources;

NOTE 2: When performing resource pool selection based on RSRP, the UE uses the latest results of the available measurements used for cell reselection evaluation in RRC_IDLE/ for measurement report triggering evaluation in RRC_CONNECTED, which are performed in accordance with the performance requirements specified in TS 36.133 [16].

[TS 36.331, clause 5.10.7.1]

Figure 5.10.7.1-3: Synchronisation information transmission for sidelink discovery

The purpose of this procedure is to provide synchronisation information to a UE. The synchronisation information concerns a Sidelink Synchronisation Signal (SLSS) for sidelink discovery, while it concerns an SLSS, timing information and some additional configuration parameters (i.e. the MasterInformationBlock-SL message) for sidelink communication. A UE transmits synchronisation information either when E-UTRAN configures it to do so by dedicated signalling (i.e. network based), or when not configured by dedicated signalling (i.e. UE based) and E-UTRAN broadcasts (in coverage) or pre-configures a threshold (out of coverage).

The synchronisation information transmitted by the UE may be derived from information/ signals received from E-UTRAN (in coverage) or received from a UE acting as synchronisation reference for the transmitting UE. In the remainder, the UE acting as synchronisation reference is referred to as SyncRef UE.

[TS 36.331, clause 5.10.7.2]

A UE capable of SLSS transmission shall, when transmitting sidelink discovery announcements in accordance with 5.10.6 and when the following conditions are met:

1> if the UE’s serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is suitable as defined in TS 36.304 [4]:

…

2> if networkControlledSyncTx is not configured; and syncTxThreshIC is included in SystemInformationBlockType19; and the RSRP measurement of the serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is below the value of syncTxThreshIC:

3> transmit SLSS in accordance with 5.10.7.3 and TS 36.211 [21], unless the UE uses the selected subframe for regular uplink transmission;

[TS 36.331, clause 5.10.7.3]

The UE shall select the SLSSID and the subframe in which to transmit SLSS as follows:

1> if triggered by sidelink discovery announcement:

2> select the SLSSID included in the entry of discSyncConfig included in the received SystemInformationBlockType19, that includes txParameters;

2> use syncOffsetIndicator corresponding to the selected SLSSID;

2> for each pool used for the transmission of discovery announcements (each corresponding to the selected SLSSID):

3> if a subframe indicated by syncOffsetIndicator corresponds to the first subframe of the discovery transmission pool;

4> select the concerned subframe;

3> else

4> select the subframe indicated by syncOffsetIndicator that precedes and which, in time domain, is nearest to the first subframe of the discovery transmission pool;

19.2.2.3 Test description

19.2.2.3.1 Pre-test conditions

System Simulator:

SS-NW

– 4 cells with parameters defined in Table 19.2.2.3.1-1.

NOTE: The test only requires at maximum 2 cells to be active at any one instant.

Table 19.2.2.3.1-1: Cell parameters values

Cell	Frequency	PLMN
1	f1	HPLMN (PLMN1)
2	f1	HPLMN (PLMN1)
4	f1	PLMN2
11	f1	PLMN3
Note 1: PLMN1: PLMN1 in USIM EF_{PROSE_ANN} PLMN2: PLMN2 in USIM EF_{PROSE_ANN} PLMN3: MCC = MCC of PLMN1 in USIM EF_{PROSE_ANN}; MNC=03. Note 2: A single frequency has been chosen for all PLMNs to allow the TC to be applicable even for UEs supporting a single band which comprises a single frequency.

– System information combination 24 as defined in TS 36.508 [18] clause 4.4.3.1 is used in all active cells when SystemInformationBlockType19 is transmitted. In all other cases System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 shall be used.

– SystemInformationBlockType19 is transmitted on all cells when they are active unless otherwise stated; the sidelink related resources in each instance are specified in the specific message content.

SS-UE

– SS-UE 1.

– As defined in TS 36.508 [18], configured for and operating as ProSe Direct Discovery Monitoring on the resources which the UE is expected to use for transmission (as specified in the relevant procedure steps in Table 19.2.2.3.2-1).

UE:

– ProSe related configuration

– The UE is equipped with a USIM containing values shown in Table 19.2.2.3.1-2, and, relevant to each of the supported services values as specified in TS 36.508 [18], section 4.9.3.1 (e.g. 2 PLMNs are authorised for ProSe Direct Discovery Announcing).

Table 19.2.2.3.1-2: USIM Configuration

USIM field	Value
EF_UST	Service n°101 (ProSe) supported.
EF_PST	Service n°1 (ProSe direct discovery parameters) supported
	Service n°5 (ProSe Direct Discovery announcing radio parameters) supported
EF_AD	b3=1: the ME is authorized to use the parameters stored in the USIM or in the ME for ProSe services for Public Safety usage

Depending on implementation, a Rel-12 UE may not support USIM settings for ProSe Direct Discovery Announcing (pc_disc_public_safety=FALSE, i.e. ProSe Discovery for Public Safety not supported) . Such UEs are expected to provide means for pre-configuring the PLMNs which are authorised for ProSe Direct Discovery Announcing (e.g. via MMI). The values specified for EF_{PROSE_ANN} in TS 36.508 [18], section 4.9.3.1 shall be preconfigured.

– For each PLMN a timer T4005 is assigned long enough not to expire before the TC is completed, e.g. 5min (For Rel-12 this timer cannot be set in the USIM, it is expected that the UE shall provide means for setting the timer e.g. via MMI).

– The UE is configured with the data structure of the ProSe Application ID (px_ProSeAnnApplicationIdentity1) it wants to announce (This step is performed using UE implementation dependent mechanisms, e.g. MMI command, or, may be pre-loaded in the UE).

– The UE has no valid ProSe Application Code corresponding to the configured ProSe Application ID (px_ProSeAnnApplicationIdentity1).

Preamble:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [18].

19.2.2.3.2 Test procedure sequence

Table 19.2.2.3.2-0 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" … "Tn" are to be applied subsequently. The exact instants on which these values shall be applied are described elsewhere in the present clause.

Table 19.2.2.3.2-0: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 2	Cell 4	Cell 11	Comments
T0	Cell-specific RS EPRE	dBm/15kHz	-85	"Off"	"Off"	"Off"	Note 1
T1	Cell-specific RS EPRE	dBm/15kHz	"Off"	-85	"Off"	"Off"
T2	Cell-specific RS EPRE	dBm/15kHz	"Off"	"Off"	-79	"Off"
T3	Cell-specific RS EPRE	dBm/15kHz	"Off"	"Off"	-87	"Off"	Note 2
T4	Cell-specific RS EPRE	dBm/15kHz	"Off"	"Off"	"Off"	-79
Note 1: The Cell power is set to satisfy the SystemInformationBlockType19 pool settings (discTxPoolCommon set to rsrpBasedUE) Note 2: The Cell power is set to ensure that the RSRP measurement is below the value of syncTxThreshIC included in SystemInformationBlockType19.

Table 19.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: SS-NW Cell 1 does not broadcast SystemInformationBlockType19.	–	–	–	–
2	The UE is switched on.	–	–	–	–
–	EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1.	–	–	–	–
3	Check: Does the UE announce its ProSe direct discovery capabilities? The Generic test procedure for ‘UE Registration, UE Test Mode Activated (State 2A)’ defined in TS 36.508 [18] clause 4.5.2A takes place.	–	–	1	P
4	Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity1 to initiate continuous ProSe direct discovery announcing. NOTE: Although the UE is expected to transmit continuously, only the PC5_DISCOVERY messages which need to be checked are shown explicitly in the step sequence.	–	–	–	–
5	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22 take place (UE performs Announce request procedure) in the next 5s?	–	–	2	F
6	SS-NW starts broadcasting SystemInformationBlockType19 on Cell 1, no resources for Announcing are provided at this moment of time.	–	–	–	–
7	Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType19.	–	–	–	–
8	Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity1 to initiate continuous ProSe direct discovery announcing.	–	–	–	–
9	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22 take place (UE performs Announce request procedure)?	–	–	3	P
10	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
11	SS-NW modifies the transmitted SystemInformationBlockType19 on Cell 1 to provide resources for Direct discovery announcing, the poolSelection provided in the discTxPoolCommon is set to rsrpBasedUE.	–	–	–	–
12	Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType19.	–	–	–	–
–	EXCEPTION: Step 13 is repeated 3 times .	–	–	–	–
13	Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 9) and utilising the resources configured in the SystemInformationType19 transmitted on the serving cell? NOTE: The UE uses for the transmission the DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is in-between the set for that pool threshLow and threshHigh (SystemInformationType19/discTxPoolCommon/ SL-DiscResourcePool-r12[1]).	–>	PC5_DISCOVERY	4	P
14	Check: Does the UE transmit in the next3 transmission periods a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 9) and utilising the resources configured in the SystemInformationType19 transmitted on the serving cell? NOTE: The UE uses for the transmission the DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is NOT in-between the set in that pool threshLow and threshHigh (SystemInformationType19/discTxPoolCommon/ SL-DiscResourcePool-r12[2]).	–>	PC5_DISCOVERY	4	F
15	The SS configures: SS-NW Cell 1 and Cell 2 parameters according to the row "T1" in table 19.2.2.3.2-0. Cell 2 broadcasts SystemInformationBlockType19 with the poolSelection provided in the discTxPoolCommon is NOT set to rsrpBasedUE.	–	–	–	–
–	EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2.	–	–	–	–
16	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Announce request procedure) in the next 5 sec?	–	–	5	F
–	EXCEPTION: Step 17 is repeated 3 times .	–	–	–	–
17	Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 9) and utilising the resources configured in the SystemInformationType19 transmitted on the serving cell(2 transmission pools; the pool to be used for transmission is to be chosen by the UE randomly)?	–>	PC5_DISCOVERY	5	P
18	The SS configures: SS-NW Cell 2 and Cell 4 parameters according to the row "T 2" in table 19.2.2.3.2-0.. Cell 4 broadcasts SystemInformationBlockType19 providing different resources for Announcing than those provided on Cell 2. In addition to all other settings the syncTxThreshIC is included in the SystemInformationBlockType19 Note: The Power level of Cell 4 is such that it is ensured that the RSRP measurement of the serving cell is NOT below the value of syncTxThreshIC included in SystemInformationBlockType19.	–	–	–	–
–	EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4.	–	–	–	–
19	Check: Does the UE announce its ProSe direct discovery capabilities? The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place.	–	–	1	P
20	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Announce request procedure)?	–	–	6	P
21	SS-NW starts a timer=T4000 (the value of T4000 is provided in the DISCOVERY_RESPONSE message sent in the procedure taking place in step 20; the expiry of this timer takes place in step 25)	–	–	–	–
22	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
–	EXCEPTION: Step 23 is repeated 3 times .	–	–	–	–
23	Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 18) and utilising the resources configured in the SystemInformationType19 transmitted on the serving cell (SystemInformationType19/discTxPoolCommon/ SL-DiscResourcePool-r12[2])?	–>	PC5_DISCOVERY	6	P
–	EXCEPTION: Steps 24a1 – 24a3 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place if the UE is capable of SLSS transmission.	–	–	–	–
24a1	IF pc_discSLSS THEN Check: Does the UE transmit SLSS in the next3transmission periods? NOTE: The Power level of Cell 4 is such that it is ensured that the RSRP measurement of the serving cell is NOT below the value of syncTxThreshIC included in SystemInformationBlockType19.	–	SLSS	7	F
24a2	The SS configures: SS-NW Cell 4 parameters according to the row "T 3" in table 19.2.2.3.2-0. Note: RSRP measurement of Cell 4 (the serving cell) is below the value of syncTxThreshIC included in SystemInformationBlockType19.	–	–	–	–
–	EXCEPTION: Step 24a3 is repeated 3 times.	–	–	–	–
24a3	Check: Does the UE transmit SLSS in the next transmission period in accordance with the information provided in the SystemInformationBlockType19 (SLSSID, a subframe indicated by syncOffsetIndicator)?	–>	SLSS	7	P
25	SS-NW waits until the timer T4000 set in step 21 expires.	–	–	–	–
26	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Announce request procedure)?	–	–	8	P
27	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
28-35	Void	–	–	–	–
36	The SS configures: SS-NW Cell 4 and Cell 11 parameters according to the row "T 4" in table 19.2.2.3.2-0 Cell 11 broadcasts SystemInformationBlockType19 providing resources for Announcing.	–	–	–	–
–	EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11.	–	–	–	–
37	Check: Does the UE announce its ProSe direct discovery capabilities? The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place.	–	–	1	P
38	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Announce request procedure) in the next 5s?	–	–	11	F
39	Check: Does the UE transmit in the next3 transmission periods a PC5_DISCOVERY message containing a ProSe Application Code and utilising the resources configured in the SystemInformationType19 transmitted on the serving cell (SystemInformationType19/discTxPoolCommon/ SL-DiscResourcePool-r12[2])?	–>	PC5_DISCOVERY	11	F
40	Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity1 to initiate ProSe direct discovery announcing.	–	–	–	–
41	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Announce request procedure) in the next 5s?	–	–	11	F

Table 19.2.2.3.2-2: Parallel behaviour – Generic RB Establishment

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1-2	Steps 6 – 7 from the Generic test procedure ‘Generic Radio Bearer Establishment (State 3)’ defined in TS 36.508 [18] subclause 4.5.3 take place.	–	–	–	–

19.2.2.3.3 Specific message contents

Table 19.2.2.3.3-1: SystemInformationBlockType19 for Cell 1 (step 6, Table 19.2.2.3.2-1)

Derivation Path: 36.508 [18] Table 4.4.3.3-17
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType19-r12 ::= SEQUENCE {
discConfig-r12 SEQUENCE {		No Resources for Direct Discovery Announcing.
discTxPoolCommon-r12	Not Present
discTxPowerInfo-r12	Not Present
discSyncConfig-r12	Not Present
}
}

Table 19.2.2.3.3-2: SystemInformationBlockType19 for Cell 1 (step 11, Table 19.2.2.3.2-1)

Derivation Path: 36.508 [18] Table 4.4.3.3-17
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType19-r12 ::= SEQUENCE {
discConfig-r12 SEQUENCE {
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 {
SL-DiscResourcePool-r12[1] SEQUENCE {	Pool 1
txParameters-r12 SEQUENCE {
ue-SelectedResourceConfig-r12 SEQUENCE {
poolSelection-r12 SEQUENCE {		rsrpBased-r12
threshLow-r12	3	-90dBm
threshHigh-r12	4	-80dBm
}
}
}
}
SL-DiscResourcePool-r12[2] SEQUENCE {	Pool 2
txParameters-r12 SEQUENCE {
ue-SelectedResourceConfig-r12 SEQUENCE {
poolSelection-r12 SEQUENCE {		rsrpBased-r12
threshLow-r12	4	-80dBm
threshHigh-r12	5	-70dBm
}
}
}
}
}
}
}
Note 1: The rsrpBased-r12r values are chosen in regard to Cell 1 setting to -85 dBm in Table 19.2.2.3.2-0; Pool1 is set so that -85 dBm is between of threshLow and threshHigh; Pool 2 is set so that -85 dBm is outside threshLow … threshHigh

Table 19.2.2.3.3-3: SystemInformationBlockType19 for Cell 2 when active

Derivation Path: 36.508 [18] Table 4.4.3.3-17
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType19-r12 ::= SEQUENCE {
discConfig-r12 SEQUENCE {
discRxPool-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 {
SL-DiscResourcePool-r12[1] SEQUENCE {		RxPool 1
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00001100 00000000 00000000 00000000 00000000	bs40-r12	FDD
	00001100 00000000	bs16-r12	TDD
}
}
SL-DiscResourcePool-r12[2] SEQUENCE {		RxPool 2
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00000011 00000000 00000000 00000000 00000000	bs40-r12	FDD
	00000011 00000000	bs16-r12	TDD
}
}
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 {
SL-DiscResourcePool-r12[1] SEQUENCE {		TxPool 1
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00001100 00000000 00000000 00000000 00000000	bs40-r12	FDD
	00001100 00000000	bs16-r12	TDD
}
}
SL-DiscResourcePool-r12[2] SEQUENCE {		TxPool 2
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00000011 00000000 00000000 00000000 00000000	bs40-r12	FDD
	00000011 00000000	bs16-r12	TDD
}
}
}
}
}
Note 1: 2 transmission/reception pools; the pool to be used for transmission is to be chosen by the UE randomly. Note 2 The resources provided for Tx are different to the resources on Cell 1 where the UE operates prior to moving to Cell 2.

Table 19.2.2.3.3-4: SystemInformationBlockType19 for Cell 4 and Cell 11 when active

Derivation Path: 36.508 [18] Table 4.4.3.3-17
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType19-r12 ::= SEQUENCE {
discConfig-r12 SEQUENCE {
discRxPool-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 {
SL-DiscResourcePool-r12[2] SEQUENCE {		RxPool 2
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00000000 11000000 00000000 00000000 00000000	bs40-r12	FDD
	00000000 11000000	bs16-r12	TDD
}
}
}
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 {
SL-DiscResourcePool-r12[1]	Not Present
SL-DiscResourcePool-r12[2] SEQUENCE {
tf-ResourceConfig-r12 SEQUENCE {
subframeBitmap-r12	00000000 11000000 00000000 00000000 00000000	bs40-r12	FDD
	00000000 11000000	bs16-r12	TDD
}
rxParameters-r12 SEQUENCE {
syncConfigIndex-r12	1	Entry 2 in discSyncConfig-r12 (SL-SyncConfig-r12[2]) (Note 1)
}
}
}
}
}
Note 1: Entry 2 in discSyncConfig-r12 sets syncTxThreshIC-r12 to 7 (see 36.508 [18] Table 4.4.3.3-17), i.e. -85dBm is the threshold for starting transmission of SLSS, which with the Cell 4 settings to -79dBm and -87dBm in Table 19.2.2.3.2-0 should ensure that for "T2" there should be no SLSS transmission and for "T3" there should be SLSS transmission. Note 2: Only one Tx resource provided SL-DiscResourcePool-r12[2] and it is different to the Tx resource(s) provided on cell 2 where the UE operates prior to moving to Cell 4.

Table 19.2.2.3.3-5: Void

Table 19.2.2.3.3-6: ATTACH REQUEST (step 3, Table 19.2.2.3.2-1; step 4, TS 36.508 [18] Table 4.5.2.3-1)

Derivation path: 36.508 [18] table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
UE network capability
ProSe (octet 7, bit 7)	‘1’	ProSe Supported
..ProSe direct discovery (ProSe-dd) (octet 7, bit 8)	‘1’	ProSe direct discovery Supported
ProSe direct communication (ProSe-dc) (octet 8, bit 1)	‘0’ or ‘1’	The UE may, but need not to, support also ProSe direct communication

Table 19.2.2.3.3-7: TRACKING AREA UPDATE REQUEST (steps 19, 37, Table 19.2.2.3.2-1; step 4, TS 36.508 [18] Table 4.5A.2.1-1)

Derivation path: 36.508 [18] table 4.7.2-27
Information Element	Value/Remark	Comment	Condition
EPS update type
"Active" flag	‘1’B
UE network capability
ProSe (octet 7, bit 7)	‘1’	ProSe Supported
..ProSe direct discovery (ProSe-dd) (octet 7, bit 8)	‘1’	ProSe direct discovery Supported
ProSe direct communication (ProSe-dc) (octet 8, bit 1)	‘0’ or ‘1’	The UE may, but need not to, support also ProSe direct communication

Table 19.2.2.3.3-7A: RRCConnectionRequest (steps 9, 17E, 20, Table 19.2.2.3.2-1)

Derivation Path: 36.508, Table 4.6.1-16.
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mo-Data
	Delay tolerant
	High priority access AC 11 – 15
}
}
}

Table 19.2.2.3.3-8: DISCOVERY_REQUEST (steps 9, 20, 26, Table 19.2.2.3.2-1; step 10a1, TS 36.508 [18] Table 4.5A.22.3-2)

Derivation path: 36.508 [18] , Table 4.7F.1-1.
Information Element	Value/remark	Comment	Condition
discovery-request[1] {
command	1	announce
}

Table 19.2.2.3.3-9: DISCOVERY_RESPONSE (steps 9, 20, 26, Table 19.2.2.3.2-1; step 10a2, TS 36.508 [18] Table 4.5A.22.3-2)

Derivation path: 36.508 [18] , Table 4.7F.1-2.
Information Element	Value/remark	Comment	Condition
response-monitor[1]	Not Present
response-announce[1] {
validity-timer-T4000	2min	Note: Value of 2 min has been arbitrary chosen with the aim from one side not to prolong unnecessarily the TC when the expiration of the timer is checked, and, on another not to trigger not relevant to the TPs ANNOUNCE REQUEST procedure.
}

Table 19.2.2.3.3-10: SidelinkUEInformation (steps 9, 20, 26, Table 19.2.2.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-21A
Information Element	Value/remark	Comment	Condition
SidelinkUEInformation-r12-IEs ::= SEQUENCE {
commRxInterestedFreq-r12	Not Present	Note 1
commTxResourceReq-r12	Not Present	Note 1
discRxInterest-r12	Not Present	Note 1
discTxResourceReq-r12	1	Note 2
}
Note 1: It is assumed that it will be possible to trigger in the UE an Application that requests only Announcing. Note 2 This TC assumes that the UE is triggering ProSe Direct Discovery Announcing for only one ProSe Application px_ProSeAnnApplicationIdentity1.

Table 19.2.2.3.3-11: Void

Table 19.2.2.3.3-12: PC5_DISCOVERY (steps 13, 14, 17, 23, Table 19.2.2.3.2-1)

Derivation path: 36.508 [18] , Table 4.7F.1-5.