19.1.6 ProSe Direct Communication/Pre-configured authorisation / UE out of coverage on the frequency used for sidelink communication / Transmission and Reception / Operation with/without SyncRef UE / Usage information report list sending procedure

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.1.6.1 Test Purpose (TP)

(1)

with { UE being authorized for performing ProSe Direct Communication being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" associated with a geographical area, and, UE out of coverage on the frequency used for sidelink communication }

ensure that {

when { UE wants to transmit ProSe direct communication, and, UE determines itself as being not located in that geographical area }

then { UE does not initiate ProSe direct communication }

}

(2)

ensure that {

when { UE wants to transmit ProSe direct communication, and, UE has determined itself located in that geographical area, and, UE does not have a selected SyncRef UE }

then { UE is able to transmit ProSe Direct Communication utilizing the radio parameters associated with that geographical area based on the UE’s own timing }

}

(3)

ensure that {

then { UE selects the correct SLSSID and subframe for transmission and transmits SLSS and MasterInformationBlock-SL message }

}

(4)

ensure that {

when { UE wants to transmit ProSe direct communication, and, UE has determined itself located in that geographical area, and, UE does have a selected SyncRef UE }

then { UE is able to transmit ProSe Direct Communication utilizing the radio parameters associated with that geographical area and in accordance with the timing of the selected SyncRef UE }

}

(5)

ensure that {

when { UE wants to transmit ProSe direct communication, and, UE can determine itself located in that geographical area, and, syncTxThreshOoC is included in the preconfigured sidelink parameters and the UE has selected SyncRef UE and the S-RSRP measurement result of the selected SyncRef UE is below the value of syncTxThreshOoC, and, inCoverage in the MasterInformationBlock-SL message received from this UE is set to TRUE }

then { UE selects the correct SLSSID and subframe for transmission and transmits SLSS and MasterInformationBlock-SL message }

}

(6)

ensure that {

then { UE selects the correct SLSSID and subframe for transmission and transmits SLSS and MasterInformationBlock-SL message }

}

(7)

ensure that {

when { UE wants to receive ProSe direct communication, and, UE can determine itself located in that geographical area, and, UE does not have a selected SyncRef UE }

then { UE is able to receive ProSe Direct Communication utilizing the radio parameters associated with that geographical area based on the UE’s own timing }

}

(8)

ensure that {

when { UE wants to receive ProSe direct communication, and, UE can determine itself located in that geographical area, and, UE does have a selected SyncRef UE }

then { UE is able to receive ProSe Direct Communication utilizing the radio parameters associated with that geographical area and in accordance with the timing of the selected SyncRef UE }

}

(9)

ensure that {

when { UE returns to coverage, and, a usage information report list sending procedure was not performed yet after beginning of ProSe direct communication, the configured collection period has elapsed since beginning of ProSe direct communication and the configured reporting window has not elapsed after the configured collection period elapsed, and, UE is in the RRC CONNECTED mode, and, UE has usage information for at least one collection period }

then { UE performs the usage information report list sending procedure }

}

(10)

with { UE being authorized for performing ProSe Direct Communication being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" associated with two geographical areas, and, UE out of coverage on the frequency used for sidelink communication }

ensure that {

when { UE moves from one to another geographical are }

then { UE obeys the resource configured for the new geographical area and uses them for transmission/reception of ProSe Direct Communication }

}

19.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.334, clauses 5.1.1, 5.1.2, 10.2.1, 10.2.2, 10.2.3, 10.3.2.1.1, 10.3.2.1.2, TS 36.331, clauses 5.2.2.4, 5.2.2.25, 5.10.3, 5.10.4, 5.10.7.1, 5.10.7.2, 5.10.7.3, 5.10.7.4, 5.10.9.1, 5.10.9.2. Unless otherwise stated these are Rel-12 requirements.

[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

[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 10.2.1]

One-to-many ProSe direct communication is applicable only to ProSe-enabled Public Safety UEs. One-to-many ProSe direct communication can only apply when the UE is:

…

b) not served by E-UTRAN, and authorised for ProSe direct communication for "not served by E-UTRAN"; or

…

Upon receiving a request from upper layers to send or receive data for ProSe direct communication in a given group, the UE shall initiate the procedure for ProSe direct communication. For case a, the UE shall perform ProSe direct communication procedures specified in subclause 10.2.2. For case b and c, the UE shall perform ProSe direct communication procedures specified in subclause 10.2.3.

…

The UE shall obtain the ProSe direct communication policy parameters for that group as specified in subclause 5.

If the ProSe direct communication policy parameters indicate that the UE is configured to use IPv6 for that group, the UE shall auto-configures a link local IPv6 Address following procedures defined in RFC 4862 [15]. This address can only be used as the source IP address for one-to-many ProSe direct communication.

If the ProSe Direct communication policy parameters group indicate that the UE is configured to use IPv4 for that group, then the UE shall:

– use the configured IPv4 address for that group as source address; or

– if there is no configured IPv4 address for that group, use Dynamic Configuration of IPv4 Link-Local Addresses as specified in IETF RFC 3927 [16].

[TS 24.334, clause 10.2.2]

When the UE is served by E-UTRAN and intends to use the ProSe radio resources (i.e. carrier frequency) provided by an E-UTRAN cell, the UE requests the parameters from the lower layers for transmitting or receiving ProSe direct communication (see 3GPP TS 36.331 [12]). The UE shall perform direct communication only if the lower layers indicate that ProSe direct communication is supported by the network. If the UE in EMM-IDLE mode has to request resources for ProSe direct communication 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]. Once the radio resources for transmitting or receiving ProSe direct communication are provided by eNodeB as specified in 3GPP TS 36.331 [12], the UE shall start ProSe direct communication.

[TS 24.334, clause 10.2.3]

When the UE is not served by E-UTRAN, the UE shall select the radio parameters to be used for ProSe direct communication as follows:

– if the UE can determine itself located in a geographical area, and the UE is provisioned with radio parameters for the geographical area, the UE shall select the radio parameters associated with that geographical area; or

– in all other cases, the UE shall not initiate ProSe direct communication.

NOTE 1: It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT it can for example use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT it can use other techniques as determined by local regulations.

…

If the UE is performing ProSe direct communication using radio parameters associated with a geographical area and moves out of that geographical area, the UE shall stop performing ProSe direct communication and then:

– if the UE is not served by E-UTRAN or the UE intends to use radio resources for ProSe other than those operated by the serving E-UTRAN cell, the UE shall select appropriate radio parameters for the new geographical area as specified above; or

– if the UE is served by E-UTRAN and intends to use radio resources for ProSe operated by the serving E-UTRAN cell, the UE shall proceed with the procedure to initiate ProSe direct communication when served by E-UTRAN.

[TS 24.334, clause 10.3.2.1.1]

The purpose of the usage information report list sending procedure is to enable a ProSe-enabled Public Safety UE to provide information necessary for composing of charging events related to the ProSe direct communication as defined in 3GPP TS 32.277 [27].

The UE shall perform the usage information report list sending procedure with the Accounting Data Forwarding (ADF) function block of the Charging Trigger Function (CTF) in the ProSe Function (ProSe Function CTF (ADF)) residing in the HPLMN.

The UE shall construct the usage information report based on the policy described in subclause 5.1.3.

[TS 24.334, clause 10.3.2.1.2]

The UE shall perform the usage information report list sending procedure if the UE is in E-UTRAN coverage and if:

a) the following is true:

1) if a usage information report list sending procedure was already performed after beginning of ProSe direct communication, the configured collection period has elapsed since the end of the previous usage information report list sending procedure;

2) if a usage information report list sending procedure was not performed yet after beginning of ProSe direct communication, the configured collection period has elapsed since beginning of ProSe direct communication;

3) the configured reporting window has not elapsed after the configured collection period elapsed;

4) the UE is in the RRC CONNECTED mode; and

5) the UE has usage information for at least one collection period; or

b) the following is true:

3) the configured reporting window has elapsed after the configured collection period elapsed; and

4) the UE has usage information for at least one collection period.

The UE shall initiate the usage information report list sending procedure by sending a USAGE_INFORMATION_REPORT_LIST message to the ProSe Function CTF (ADF).

If the UE is configured with the IP address of the ProSe Function CTF (ADF), the UE shall send the USAGE_INFORMATION_REPORT_LIST message to the configured IP address of the ProSe Function CTF (ADF). If the UE is not configured with the IP address of the ProSe Function CTF (ADF), the UE shall send the USAGE_INFORMATION_REPORT_LIST message to the IP address of the ProSe Function discovered as described in subclause 5.1.2.

In the USAGE_INFORMATION_REPORT_LIST message, the UE:

a) shall include a new transaction ID;

b) shall include the UE identity set to the UE’s IMSI;

c) for each collection period:

1) shall include a sequence number of the usage information report;

2) if the UE is configured to report the time stamps when it went in and out of E-UTRAN coverage during the collection period in the usage information, for each going in or out of E-UTRAN coverage:

A) shall include information whether the UE was in or out of E-UTRAN coverage;

B) shall include the time stamp of the move; and

C) if the UE was in E-UTRAN coverage and the UE is configured to report the list of locations of the UE when in E-UTRAN coverage during the collection period in the usage information, for each camping on a cell or usage of a cell in the EMM-CONNECTED mode:

i) shall include the E-UTRAN cell global identification of the cell; and

ii) shall include the time stamp of beginning of the camping on the cell or of beginning of the usage of the cell in the EMM-CONNECTED mode;

3) if the UE is configured to report the group parameters in the usage information, for each group:

A) shall include the ProSe Layer-2 Group ID;

B) shall include the ProSe Group IP multicast address;

C) if the UE transmitted data during the collection period and the UE is configured to report the time stamps of the first transmission/reception during the collection period in the usage information, shall include the time stamp of the first transmission to the ProSe Group IP multicast address in the collection period;

D) if the UE received data during the collection period and the UE is configured to report the time stamps of the first transmission/reception during the collection period in the usage information, shall include the time stamp of the first reception from the ProSe Group IP multicast address in the collection period;

E) shall include an IP address used by the UE as a source address;

F) shall include the ProSe UE ID;

G) for each transmitter in one-to-many ProSe direct communication, shall include the Source L2 ID and IP address of the transmitter;

H) if the UE is configured to report the amount of data transmitted during the collection period with location information in the usage information, per each in or out of E-UTRAN coverage period and per each E-UTRAN cell used when in E-UTRAN coverage:

i) shall indicate whether the data are sent in or out of E-UTRAN coverage;

ii) if the UE transmitted data in an E-UTRAN cell during an in E-UTRAN coverage period:

– shall include the E-UTRAN cell global identification of the E-UTRAN cell;

– shall include amount of the data transmitted in the E-UTRAN cell;

– if the UE is configured to report the time stamps of the first transmission/reception during the collection period in the usage information, shall include time stamp of the first transmission in the E-UTRAN cell; and

– if the UE is configured to report the radio parameters used for ProSe direct communication (i.e. indicator of which radio resources used and radio frequency used) during the reporting period in the usage information, shall include the indicator of which radio resources were used;

iii) if the UE transmitted data during out of E-UTRAN coverage period:

– shall include amount of the data transmitted during the out of E-UTRAN coverage period; and

iv) if the UE is configured to report the radio parameters used for ProSe direct communication (i.e. indicator of which radio resources used and radio frequency used) during the reporting period in the usage information, shall include the used radio frequency; and

I) if the UE is configured to report the amount of data transmitted during the collection period without location information in the usage information, per each in or out of E-UTRAN coverage period:

i) shall indicate whether the data are sent in or out of E-UTRAN coverage;

ii) if the UE transmitted data during in E-UTRAN coverage period:

– shall include amount of the data transmitted during the in E-UTRAN coverage period;

iii) if the UE transmitted data during out of E-UTRAN coverage period:

– shall include amount of the data transmitted during the out of E-UTRAN coverage period; and

J) if the UE is configured to report the amount of data received during the collection period with location information in the usage information, per each in or out of E-UTRAN coverage period and per each E-UTRAN cell used when in E-UTRAN coverage:

i) shall indicate whether the data are sent in or out of E-UTRAN coverage;

ii) if the UE received data in an E-UTRAN cell during an in E-UTRAN coverage period:

– shall include the E-UTRAN cell global identification of the E-UTRAN cell;

– shall include amount of the data received in the E-UTRAN cell;

iii) if the UE received data during out of E-UTRAN coverage period:

– shall include amount of the data received during the out of E-UTRAN coverage period; and

K) if the UE is configured to report the amount of data received during the collection period without location information in the usage information, per each in or out of E-UTRAN coverage period:

i) shall indicate whether the data are sent in or out of E-UTRAN coverage;

ii) if the UE received data during in E-UTRAN coverage period:

– shall include amount of the data received during the in E-UTRAN coverage period;

iii) if the UE received data during out of E-UTRAN coverage period:

– shall include amount of the data received during the out of E-UTRAN coverage period; and

4) if configured radio parameters for the ProSe direct communication applicable in the geographical area of the UE were used during the collection period, shall include the configured radio parameters for the ProSe direct communication applicable in the geographical area of the UE; and

d) for each application specific data received from upper layers during the collection period, shall include the received application specific data.

Figure 10.3.2.1.2.1 illustrates the interaction of the UE and the ProSe Function CTF (ADF) in the usage information report list sending procedure.

Figure 10.3.2.1.2.1: Usage information report list sending procedure

[TS 36.331, clause 5.2.2.4]

1> if the UE is capable of sidelink communication and is configured by upper layers to receive or transmit sidelink communication:

2> if the cell used for sidelink communication meets the S-criteria as defined in TS 36.304 [4]; and

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

3> acquire SystemInformationBlockType18;

[TS 36.331, clause 5.2.2.25]

Upon receiving SystemInformationBlockType18, the UE shall:

1> if SystemInformationBlockType18 message includes the commConfig:

2> if configured to receive sidelink communication:

3> from the next SC period, as defined by sc-Period, use the resource pool indicated by commRxPool for sidelink communication monitoring, as specified in 5.10.3;

2> if configured to transmit sidelink communication:

3> from the next SC period, as defined by sc-Period, use the resource pool indicated by commTxPoolNormalCommon or by commTxPoolExceptional for sidelink communication transmission, as specified in 5.10.4;

[TS 36.331, clause 5.10.3]

A UE capable of sidelink communication that is configured by upper layers to receive sidelink communication shall:

…

2> else (i.e. out of coverage on the sidelink carrier):

3> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources that were preconfigured (i.e. preconfigComm in SL-Preconfiguration defined in 9.3);

NOTE 2: The UE may monitor in accordance with the timing of the selected SyncRef UE, or if the UE does not have a selected SyncRef UE, based on the UE’s own timing.

[TS 36.331, clause 5.10.4]

A UE capable of sidelink communication that is configured by upper layers to transmit sidelink communication and has related data to be transmitted shall:

…

2> else (i.e. out of coverage on sidelink carrier):

3> configure lower layers to transmit the sidelink control information and the corresponding data using the pool of resources that were preconfigured i.e. indicated by the first entry in preconfigComm in SL-Preconfiguration defined in 9.3 and in accordance with the timing of the selected SyncRef UE, or if the UE does not have a selected SyncRef UE, based on the UEs own timing;

[TS 36.331, clause 5.10.7.1]

Figure 5.10.7.1-2: Synchronisation information transmission for sidelink communication, out of coverage

…

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 shall, when transmitting sidelink communication in accordance with 5.10.4 and when the following conditions are met:

1> else (i.e. out of coverage):

2> if syncTxThreshOoC is included in the preconfigured sidelink parameters (i.e. SL-Preconfiguration defined in 9.3); and the UE has no selected SyncRef UE or the S-RSRP measurement result of the selected SyncRef UE is below the value of syncTxThreshOoC:

3> transmit SLSS in accordance with 5.10.7.3 and TS 36.211 [21];

3> transmit the MasterInformationBlock-SL message, in the same subframe as SLSS, and in accordance with 5.10.7.4;

[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 communication:

…

2> else (i.e. out of coverage on sidelink carrier):

3> select the synchronisation reference UE (i.e. SyncRef UE) as defined in 5.10.8;

3> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlock-SL message received from this UE is set to TRUE; or

…

4> select the same SLSSID as the SLSSID of the selected SyncRef UE;

4> select the subframe in which to transmit the SLSS according to the syncOffsetIndicator1 or syncOffsetIndicator2 included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration defined in 9.3), such that the subframe timing is different from the SLSS of the selected SyncRef UE;

3> else if the UE has a selected SyncRef UE:

4> select the SLSSID from the set defined for out of coverage having an index that is 168 more than the index of the SLSSID of the selected SyncRef UE, see TS 36.211 [21];

4> select the subframe in which to transmit the SLSS according to syncOffsetIndicator1 or syncOffsetIndicator2 included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration defined in 9.3), such that the subframe timing is different from the SLSS of the selected SyncRef UE;

3> else (i.e. no SyncRef UE selected):

4> randomly select, using a uniform distribution, an SLSSID from the set of sequences defined for out of coverage, see TS 36.211 [21];

4> select the subframe in which to transmit the SLSS according to the syncOffsetIndicator1 or syncOffsetIndicator2 (arbitrary selection between these) included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration defined in 9.3);

[TS 36.331, clause 5.10.7.4]

The UE shall set the contents of the MasterInformationBlock-SL message as follows:

…

1> else if the UE has a selected SyncRef UE (as defined in 5.10.8):

2> set inCoverage to FALSE;

2> set sl-Bandwidth, subframeAssignmentSL and reserved to the value of the corresponding field included in the received MasterInformationBlock-SL;

1> else (i.e. no SyncRef UE selected):

2> set inCoverage to FALSE;

2> set sl-Bandwidth, subframeAssignmentSL and reserved to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. preconfigGeneral in SL-Preconfiguration defined in 9.3);

1> set directFrameNumber and directSubframeNumber according to the subframe used to transmit the SLSS, as specified in 5.10.7.3;

1> submit the MasterInformationBlock-SL message to lower layers for transmission upon which the procedure ends;

[TS 36.331, clause 5.10.9.1]

The sidelink common control information is carried by a single message, the MasterInformationBlock-SL (MIB-SL) message. The MIB-SL includes timing information as well as some configuration parameters and is transmitted via SL-BCH.

The MIB-SL uses a fixed schedule with a periodicity of 40 ms without repetitions. In particular, the MIB-SL is scheduled in subframes indicated by syncOffsetIndicator i.e. for which (10*DFN + subframe number) mod 40 = syncOffsetIndicator.

The sidelink common control information may change at any transmission i.e. neither a modification period nor a change notification mechanism is used.

A UE configured to receive or transmit sidelink communication shall:

1> if the UE has a selected SyncRef UE, as specified in 5.10.8.2:

2> ensure having a valid version of the MasterInformationBlock-SL message of that SyncRefUE:

[TS 36.331, clause 5.10.9.2]

Upon receiving MasterInformationBlock-SL, the UE shall:

1> apply the values of sl-Bandwidth, subframeAssignmentSL, directFrameNumber and directSubframeNumber included in the received MasterInformationBlock-SL message;

19.1.6.3 Test description

19.1.6.3.1 Pre-test conditions

System Simulator:

SS-NW

– Cell 1, operating on the frequency f1 configured in the UE for usage for ProSe Communication, HPLMN (PLMN1 authorised for ProSe Communication, PLMN1 in USIM EF_{PROSE_PLMN}).

– System information combination23 as defined in TS 36.508 [18] clause 4.4.3.1 is transmitted on Cell 1 when active.

SS-UE

– SS-UE1.

– As defined in TS 36.508 [18], configured for and operating as ProSe Direct Communication transmitting and receiving device, as well as, transmitting Synchronisation information on the resources which the UE is expected to use for transmission and reception (as specified in the relevant procedure steps in Table 19.1.6.3.2-1).

UE:

– ProSe related configuration

– The UE is authorised to perform ProSe Direct Communication; The UE is equipped with a USIM containing values shown in Table 19.1.6.3.1-1, 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 Communication when served by E-UTRAN, Direct Communication Radio Parameters and geographical area when UE is "not served by E-UTRAN", ProSe Layer-2 Group ID, ProSe Group IP multicast address, relevant information requesting/allowing the submission of Usage Information Reports, etc.).

Table 19.1.6.3.1-1: USIM Configuration

USIM field	Value
EF_UST	Service n°101 (ProSe) supported.
EF_PST	Service n°2 (HPLMN ProSe Function) supported.
	Service n°3 (ProSe Direct Communication radio parameters) supported.
	Service n°6 (ProSe policy parameters) supported.
	Service n°7 (ProSe group counter) supported.
	Service n°8 (ProSe Usage Information Reporting configuration) supported.
	Service n°9 (UICC ProSe Direct Communication usage information reporting) 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.

– For each PLMN a timer T4005 is assigned long enough not to expire before the TC is completed, e.g. 9 min (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).

NOTE: The requirement for authorisation of a second PLMN is not essential for the present TC. It is included simply to allow the same pre-configured SIM to be used for most, if not all, of the ProSe TCs).

Preamble:

– The UE is in state Generic RB Established, UE Test Mode E Activated (State 3A) according to [18] on Cell 1.

19.1.6.3.2 Test procedure sequence

Table 19.1.6.3.2-0 illustrates the downlink power levels and other, if any, changing parameters to be applied for the SS-UEs 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.1.6.3.2-0: Time instances of simulated SS-UE power level and parameter changes

	Parameter	Unit	SS-UE1	Comment
T0	S-RSRP	dBm/15kHz	"Off"
T1	S-RSRP	dBm/15kHz	-79	The power levels of the SS-UE are set so that upon S-RSRP measurement by the UE the result is NOT below the value of syncTxThreshOoC (SL-Preconfiguration).
T2	S-RSRP	dBm/15kHz	-85	The power levels of the SS-UE are set so that upon S-RSRP measurement by the UE the result is below the value of syncTxThreshOoC (SL-Preconfiguration).
T3	S-RSRP	dBm/15kHz	-79	The power levels of the SS-UE are set so that upon S-RSRP measurement by the UE the result is NOT below the value of syncTxThreshOoC (SL-Preconfiguration).

Table 19.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS-NW sends UPDATE UE LOCATION INFORMATION message which provides location data different to the location area pre-configured in the UE for prose communication (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}).	<–	UPDATE UE LOCATION INFORMATION	–	–
2	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
3	SS-NW Configures Cell 1 as "Not suitable "Off" cell".	–	–	–	–
4	Force the UE upper layer application to request continuous transmission of sidelink communication (a maximum of 100 Bytes per communication "message"). NOTE: This can be done e.g. via a MMI command. Note that the max of 100 Bytes is not a 3GPP requirement rather it is requested only for the purpose of facilitating the test case specification.	–	–	–	–
4A	Wait for 5 sec to allow the UE to start transmission.	–	–	–	–
5	Check: Does the UE transmit sidelink communication data over the PC5 interface in the next 3 transmission periods in accordance with the resources pre-configured for usage when "Out of coverage"?	–>	–	1	F
6	SS configures: SS-NW Cell 1 as "Serving cell".	–	–	–	–
6A	Void	–	–	–	–
7-10 A	Steps 1 – 4 from the generic test procedure for UE registration, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
–	EXCEPTION: In parallel to the event described in steps 11 – 11N1 the events described in Table 19.1.6.3.2-2 take place	–	–	–	–
11-11N1	Steps 5 – 19 from the generic test procedure for UE Registration, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
12	The SS-NW sends UPDATE UE LOCATION INFORMATION message for area 1 (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}).	<–	UPDATE UE LOCATION INFORMATION	–	–
13	Close UE Test Loop with bit E0 in UE test loop mode E LB setup IE set to one and bring UE into state Loopback Activated (State 4). NOTE: The loop is closed here and used towards the end of the test sequence to allow that most of the time the UE is kept out of coverage and is not moving often between in and out of coverage.	<–	CLOSE UE TEST LOOP	–	–
14	The UE responds with CLOSE UE TEST LOOP COMPLETE.	–>	CLOSE UE TEST LOOP COMPLETE	–	–
14A	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
15-15Ab1	Void.	–	–	–	–
16	SS-NW configures: SS-NW Cell 1 as "Not suitable "Off" cell"	–	–	–	–
17	Wait for 5 sec to allow the UE to adjust to the cell changes and "recognise" it is out of coverage.	–	–	–	–
17A	Force the UE upper layer application to request continuous transmission of sidelink communication (a maximum of 100 Bytes per communication "message"). NOTE: Although the UE is expected to transmit continuously, only the STCH PDCP SDU packets which need to be checked are shown explicitly in the step sequence.	–	–	–	–
17B	Wait for 5 sec to allow the UE to start transmission.	–	–	–	–
–	EXCEPTION: Steps 17C – 17D are repeated 3 times.	–	–	–	–
17C	Check: Does the UE transmit SLSS in accordance with the information provided in syncTxThreshOoC included in the preconfigured sidelink parameters (SL-Preconfiguration) in the next transmission period? UE shall – select the subframe in which to transmit the SLSS according to the syncOffsetIndicator1 or syncOffsetIndicator2 (arbitrary selection between these) included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration). NOTE: UE does not have a selected SyncRef UE and therefore shall use timing based on the UE’s own timing.	–>	SLSS	3	P
17D	Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 19?	–>	MasterInformationBlock-SL	3	P
18	Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources pre-configured for usage when "Out of coverage"? NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. NOTE 2: UE does not have a selected SyncRef UE and therefore shall use timing based on the UE’s own timing.	–>	STCH PDCP SDU packet	2	P
19-21	Void.
22	SS configures: SS-UE1 in accordance with " T1" defined in Table 19.1.6.3.2-0. SS-UE1 continuously transmits SLSS and MasterInformationBlock-SL message in the same subframe as the SLSS. SLSS-ID is set to 101, syncOffsetIndicator is set to 3. the SLSS transmitted is NOT part of the set defined for out of coverage in the UE inCoverage in the MasterInformationBlock-SL message set to TRUE. Note: The power levels of the SS-UE1 are set so that upon S-RSRP measurement by the UE the result is NOT below the value of syncTxThreshOoC (SL-Preconfiguration).	<–	SLSS MasterInformationBlock-SL	–	–
23	Wait for 1 sec to allow time for the UE to select the SS-UE1 for SyncRef UE.	–	–	–	–
–	EXCEPTION: Step 24 is repeated until one completed STCH PDCP SDU packet is received.	–	–	–	–
24	Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources pre-configured for usage when "Out of coverage" and the information provided by the SyncRef UE (SS-UE1)? NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.	–>	STCH PDCP SDU packet	4	P
–	EXCEPTION: Steps 25 – 26 is repeated 3 times.	–	–	–	–
25	Check: Does the UE transmit SLSS in the next transmission period in accordance with the information provided by the SyncRef UE?	–>	SLSS	5	F
26	Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 25?	–>	MasterInformationBlock-SL	5	F
27	SS configures: SS-UE1 in accordance with "T2" defined in Table 19.1.6.3.2-0. Note: SS configures a SS-UE1 so that upon S-RSRP measurement by the UE the result is below the value of syncTxThreshOoC (SL-Preconfiguration). No changes to the SLSS and MasterInformationBlock-SL message	–	–	–	–
–	EXCEPTION: Steps 28 – 29 are repeated 3 times.	–	–	–	–
28	Check: Does the UE transmit SLSS in the next transmission period in accordance with the information provided by the SyncRef UE (SS-UE1)? UE shall: – select the same SLSSID as the SLSSID of the selected SyncRef UE; – select the subframe in which to transmit the SLSS according to the syncOffsetIndicator1 or syncOffsetIndicator2 included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration defined in section 19.1.6.3.3), such that the subframe timing is different from the SLSS of the selected SyncRef UE.	–>	SLSS	5	P
29	Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 28?	–>	MasterInformationBlock-SL	5	P
30	SS-UE1 while continuing transmitting SLSS and MasterInformationBlock-SL message in the same subframe as the SLSS, changes the inCoverage in the MasterInformationBlock-SL message to FALSE. SLSS-ID = 172.	<–	SLSS MasterInformationBlock-SL	–	–
–	EXCEPTION: Steps 31 – 32 are repeated 3 times.	–	–	–	–
31	Check: Does the UE transmit SLSS in the next transmission period in accordance with the information provided by the SyncRef UE? The UE shall: – select the SLSSID from the set defined for out of coverage having an index that is 168 more than the index of the SLSSID of the selected SyncRef UE, see TS 36.211]; – select the subframe in which to transmit the SLSS according to syncOffsetIndicator1 or syncOffsetIndicator2 included in the preconfigured sidelink parameters (i.e. preconfigSync in SL-Preconfiguration defined in section 19.1.6.3.3), such that the subframe timing is different from the SLSS of the selected SyncRef UE.	–>	SLSS	6	P
32	Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 30?	–>	MasterInformationBlock-SL	6	P
33	SS-UE1 stops transmitting Synchronisation information.	–	–	–	–
33A	Force the UE upper layer application to stop transmission of sidelink communication.	–	–	–	–
34	Force the UE upper layer application to request reception of sidelink communication.	–	–	–	–
34A	Wait for 5 sec to allow the UE to start searching for transmission.	–	–	–	–
–	EXCEPTION: Step 35 is repeated 3 times.	–	–	–	–
35	SS-UE1 sends sidelink communication over the PC5 interface in the next transmission period using the UE timing. NOTE: This step verifies TP7 – it is expected that the UE shall receive these packets – if they were received is checked in step 69.	<–	STCH PDCP SDU packet	–	–
36	SS configures: SS-UE1 in accordance with "T3" defined in Table 19.1.6.3.2-0. SS-UE1 continuously transmits SLSS and MasterInformationBlock-SL message in the same subframe as the SLSS. The timing used is different than the timing used by the UE. Note: The power levels of the SS-UE1 are set so that upon S-RSRP measurement by the UE the result is NOT below the value of syncTxThreshOoC (SL-Preconfiguration).	<–	SLSS MasterInformationBlock-SL	–	–
37	Wait for 1 sec to allow time for the UE to search for SyncRef UE and find the SS-UE1 and select it as SyncRef UE.	–	–	–	–
–	EXCEPTION: Step 38 is repeated 3 times.	–	–	–	–
38	SS-UE1 sends sidelink communication over the PC5 interface in the next transmission period using its own timing. NOTE: This step verifies TP8 – it is expected that the UE shall receive these packets – if they were received is checked in step 69.	<–	STCH PDCP SDU packet	–	–
39	SS configures: SS-NW Cell 1 as "Serving cell". The provided in the SystemInformationBlockType18 message resources for transmission/reception of sidelink communication are different to the preconfigured resources.	–	–	–	–
39A	Void	–	–	–	–
40-43A	Steps 1 – 4 from the generic test procedure for UE Registration, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
–	EXCEPTION: In parallel to the event described in steps 44 – 48N1 the events described in Table 19.1.6.3.2-2 take place	–	–	–	–
44-48N1	Steps 5 – 19 from the generic test procedure for UE Registrations, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
49-67	Void
68	The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message.	<–	UE TEST LOOP PROSE PACKET COUNTER REQUEST	–	–
69	Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER=6? (Confirmation that the messages sent in steps 35 and 38 were received.)	–>	UE TEST LOOP PROSE PACKET COUNTER RESPONSE	7, 8	P
70	The SS-NW sends UPDATE UE LOCATION INFORMATION message for area 2 (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}).	<–	UPDATE UE LOCATION INFORMATION	–	–
70A	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
71-71Ab1	Void.	–	–	–	–
72	SS-NW Configures Cell 1 as "Not suitable "Off" cell"	–	–	–	–
73	Wait for 5 sec to allow the UE to adjust to the cell changes and "recognise" it is out of coverage..	–	–	–	–
73A	Force the UE upper layer application to start transmission of sidelink communication.	–	–	–	–
73B	Wait for 5 sec for UE to process the request and start transmitting.	–	–	–	–
–	EXCEPTION: Step 74 is repeated until one complete STCH PDCP SDU packet is received.	–	–	–	–
74	Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources pre-configured for usage when "Out of coverage" for area 2? NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict	–>	STCH PDCP SDU packet	10	P
74A	Force the UE upper layer application to stop transmission of sidelink communication.	–	–	–	–
74B	Wait for 5 sec for UE to process the request and stop transmitting.	–	–	–	–
–	EXCEPTION: Step 75 is repeated 3 times.	–	–	–	–
75	SS-UE1 sends sidelink communication over the PC5 interface in the next transmission period using its own timing. NOTE: This step verifies TP10 – it is expected that the UE shall receive these packets – if they were received is checked in step 105.	<–	STCH PDCP SDU packet	–	–
76	SS-NW Configures Cell 1 as "Serving cell"	–	–	–	–
76A	Void	–	–	–	–
77-80 A	Steps 1 – 4 from the generic test procedure for UE Registration, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
–	EXCEPTION: In parallel to the event described in steps 81 – 85 N1 the events described in Table 19.1.6.3.2-2 take place	–	–	–	–
81-85N1	Steps 5 – 19 from the generic test procedure for UE Registration, UE Test Mode Activated (State 2A) defined in TS 36.508 [18] subclause 4.5.2A take place.	–	–	–	–
86-103	Void	–	–	–	–
104	The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message.	<–	UE TEST LOOP PROSE PACKET COUNTER REQUEST	–	–
105	Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER=9?	–>	UE TEST LOOP PROSE PACKET COUNTER RESPONSE	10	P
106-107b1	Void.	–	–	–	–
108	The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.	<–	OPEN UE TEST LOOP	–	–
109	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	OPEN UE TEST LOOP COMPLETE	–	–
110	The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure.	<–	DEACTIVATE TEST MODE	–	–
111	The UE transmits a DEACTIVATE TEST MODE COMPLETE message.	–>	DEACTIVATE TEST MODE COMPLETE	–	–
112	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–
113	Wait for the configured collection period time to elapse (see 36.508 [18], clause 4.9.3.1, ProSe CollectionPeriod value in EF_{PROSE_UIRC}). NOTE: The period starts with the first UE Direct communication transmission in step 17B. Note that depending on the time the TC may take to move from step 17B to step 112 the configured collection period time may have already elapsed at this point of time.	–	–	–	–
114	Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition USAGEINFOREPORT defined in TS 36.508 [18] subclause 4.5A.22 take place in the next 5 sec? (UE performs Usage information report list sending procedure) NOTE: The pre-configured timers shall be set so that it is ensured that at this moment of time the configured reporting window has not elapsed after the configured collection period elapsed see 36.508 [18], clause 4.9.3.1, ProSe ReportingWindow value in EF_{PROSE_UIRC}.	–	–	9	P
115	The SS-NW releases the connection.	<–	RRCConnectionRelease	–	–

Table 19.1.6.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in RRC_CONNECTED.	–>	SidelinkUEInformation	–	–

19.1.6.3.3 Specific message contents

Table 19.1.6.3.3-1: SystemInformationBlockType18 for Cell 1 when active

Derivation Path: 36.508 [18] , table 4.4.3.3-17
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType18-r12 ::= SEQUENCE {
commConfig-r12 SEQUENCE {
commRxPool-r12 SEQUENCE (SIZE (1..maxSL-RxPool-r12)) OF SL-CommResourcePool-r12 {
SL-CommResourcePool-r12[2]	Not Present
}
commTxPoolNormalCommon-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-CommResourcePool-r12 {
SL-CommResourcePool-r12[2]	Not Present
}
commTxPoolExceptional-r12	Not Present
commSyncConfig-r12	Not Present
}
}
Note: SideLink direct communication supported; resources for transmission in RRC_IDLE provided (commTxPoolNormalCommon – 1 pool, SL-CommResourcePool-r12[1]); resources for reception in RRC_IDLE provided (commRxPool – 2 pools SL-CommResourcePool-r12[1], SL-CommResourcePool-r12[3]).

Table 19.1.6.3.3-2: ATTACH REQUEST (Preamble)

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)	‘0’ or ‘1’	The UE may, but need not to, support also ProSe direct discovery
ProSe direct communication (ProSe-dc) (octet 8, bit 1)	‘1’	The ProSe direct communication supported

Table 19.1.6.3.3-3: Void

Table 19.1. 6.3.3-4: SidelinkUEInformation (step 1, Table 19.1.6.3.2-2, step 11, Table 19.1.6.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-21A
Information Element	Value/remark	Comment	Condition
SidelinkUEInformation-r12-IEs ::= SEQUENCE {
commRxInterestedFreq-r12	f1	Preconfigured value for the service authorisation (same as the frequency on which the simulated cells operate)	Indicates the frequency on which the UE is interested to receive sidelink communication
commTxResourceReq-r12 SEQUENCE {		Indicates the frequency on which the UE is interested to transmit sidelink communication as well as the sidelink communication transmission destination(s) for which the UE requests E-UTRAN to assign dedicated resources.
carrierFreq-r12	f1	Preconfigured value for the service authorisation (same as the frequency on which the simulated cells operate)
destinationInfoList-r12 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SL-DestinationIdentity-r12	1 entry
SL-DestinationIdentity-r12[1]	the destination which is identified by the ProSe Layer-2 Group ID	Preconfigured value for the service authorisation
}
}
discRxInterest-r12	Not Present	Note 1
discTxResourceReq-r12	Not Present	Note 1
}
Note 1: It is assumed that it will be possible to trigger in the UE an Application that requests only sidelink communication transmission.

Table 19.1.6.3.3-5: MasterInformationBlock-SL (steps 17D, 29, 32, Table 19.1.6.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-4A0
Information Element	Value/remark	Comment	Condition
MasterInformationBlock-SL ::= SEQUENCE {
inCoverage-r12	FALSE	UE is out of E-UTRAN coverage
}

Table 19.1.6.3.3-6: MasterInformationBlock-SL (step 22, Table 19.1.6.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-4A0
Information Element	Value/remark	Comment	Condition
MasterInformationBlock-SL ::= SEQUENCE {
sl-Bandwidth-r12	px_SL_AdditionalSupportedBandwidth : a value different to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. preconfigGeneral in SL-Preconfiguration)
}

Table 19.1.6.3.3-7: Void

Table 19.1.6.3.3-8: MasterInformationBlock-SL (step 30, Table 19.1.6.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-4A0
Information Element	Value/remark	Comment	Condition
MasterInformationBlock-SL ::= SEQUENCE {
sl-Bandwidth-r12	px_SL_AdditionalSupportedBandwidth : a value different to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. preconfigGeneral in SL-Preconfiguration)
inCoverage-r12	FALSE	UE is out of E-UTRAN coverage
}

Table 19.1.6.3.3-9: UPDATE UE LOCATION INFORMATION (step 1, Table 19.1.6.3.2-1)

Derivation Path: 36.509 [38], clause 6.12.
Information Element	Value/remark	Comment	Condition
ellipsoidPointWithAltitude		The Location information provided shall be different to the one pre-configured in the UE (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}) as geographical area where the UE is allowed to use prose communication
horizontalVelocity	horizontalVelocity: 0 m/s
Gnss-TOD-msec	Equal to system time

Table 19.1.6.3.3-10: UPDATE UE LOCATION INFORMATION (step 12, Table 19.1.6.3.2-1)

Derivation Path: 36.509 [38], clause 6.12.
Information Element	Value/remark	Comment	Condition
ellipsoidPointWithAltitude		The Location information provided shall match the area 1 pre-configured in the UE (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}) as geographical area where the UE is allowed to use prose communication
horizontalVelocity	horizontalVelocity: 0 m/s
Gnss-TOD-msec	Equal to system time

Table 19.1.6.3.3-11: CLOSE UE TEST LOOP (step 13, Table 19.1.6.3.2-1)

Derivation Path: 36.508 [18], table 4.7A-3 condition UE TEST LOOP MODE E

Information Element

Value/remark

Comment

Condition

Communication Transmit or Receive

00000000

RECEIVE

receive sidelink direct communication

this is the default

Table 19.1.6.3.3-12: UPDATE UE LOCATION INFORMATION (step 70, Table 19.1.6.3.2-1)

Derivation Path: 36.509 [38], clause 6.12.
Information Element	Value/remark	Comment	Condition
ellipsoidPointWithAltitude		The Location information provided shall match the area 2 pre-configured in the UE (see TS 36.508 [18], clause 4.9.3.1, EF_{PROSE_RADIO_COM}) as geographical area where the UE is allowed to use prose communication
horizontalVelocity	horizontalVelocity: 0 m/s
Gnss-TOD-msec	Equal to system time