19.1.1 ProSe direct Communication /Pre-configured authorisation / UE in RRC_IDLE on an E-UTRAN cell operating on the carrier frequency provisioned for ProSe direct service / Utilisation of the resources of (serving) cells/PLMNs / Transmission
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
19.1.1.1 Test Purpose (TP)
(0)
with { UE supporting ProSe direct communication }
ensure that {
when { UE performs Attach procedure, or, Normal tracking area updating procedure }
then { UE announces its ProSe capabilities }
}
(0A)
with { UE being authorised for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" on frequency f1, and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is not transmitting SystemInformationBlockType18 (i.e. ProSe direct communication is supported by the network) }
ensure that {
when { UE receives a request from upper layers to transmit sidelink communication }
then { UE does not initiate ProSe direct communication }
}
(1)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 which does not include commTxPoolNormalCommon }
ensure that {
when { UE receives a request from upper layers to transmit sidelink communication }
then { UE initiates an RRC connection, and, successfully completes a Sidelink UE information procedure to indicate the sidelink communication transmission resources required }
}
(2)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 indicating the provision of resources for sidelink communication (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) }
ensure that {
when { UE is triggered by an upper layer application to transmit sidelink communication }
then { UE is able to transmit sidelink communication using the configured resources in Cell1/f1/PLMN1 }
}
(3)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 indicating the provision of resources for sidelink communication }
ensure that {
when { Cell2/f1/PLMN4 (equivalent PLMN) which is broadcasting SystemInformationBlockType18 providing resources for sidelink communication (commTxResources set to scheduled) becomes the highest ranked cell, and, UE reselects to Cell2/f1/PLMN4 }
then { UE is able to transmit sidelink communication using the configured resources in Cell2/f1/PLMN4) }
}
(4) Void
(5)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell4/f1/PLMN2 which is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 indicating the provision of resources for sidelink communication and including syncTxThreshIC }
ensure that {
when { the RSRP measurement of the serving cell is below the value of syncTxThreshIC }
then { UE transmits SLSS and MasterInformationBlock-SL message in the same subframe }
}
(6)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell4/f1/PLMN2 which is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 indicating the provision of resources for sidelink communication }
ensure that {
when { Cell11/f1/PLMN3 which is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) becomes the highest ranked PCell, and, UE reselects to Cell11/f1/PLMN3 }
then { UE does not initiate an RRC connection and does not transmit a SidelinkUEInformation message to indicate the transmission resources required, and, does not transmit sidelink communication over the PC5 in the assigned resources in Cell11/f1/PLMN3 }
}
(7)Void
(8)
with { UE registered on PLMN1 and being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) and pre-configured with Radio parameters for when the UE is "not served by E-UTRAN", and, UE in EMM-IDLE mode and in limited service state on Cell4/f1/PLMN2 after attempting TAU on Cell4/f1/PLMN2 and receiving a TRACKING AREA UPDATE REJECT message with the EMM cause #11 "PLMN not allowed", and, n Cell4/f1/PLMN2 is operating on the same carrier frequency as the one pre-configured in the UE and is transmitting SystemInformationBlockType18 indicating the provision of resources for sidelink communication }
ensure that {
when { UE receives a request from upper layers to send data for ProSe direct communication }
then { UE transmits sidelink communication utilising the resources provided on Cell4/f1/PLMN2 }
}
19.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: T TS 24.301, clauses 5.5.1.2.2, 5.5.3.2.2S 24.334, clauses 5.1.1, 5.1.2, 10.2.1, 10.2.2, 10.2.3, TS 36.331, clauses 5.2.2.4, 5.2.2.25, 5.3.3.1a, 5.10.1a, 5.10.2.1, 5.10.2.2, 5.10.2.3. U, 5.10.4nless otherwise stated these are Rel-12 requirements.
[TS 24.301, clause 5.5.1.2.2]
If the UE supports ProSe direct communication, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct communication bit to "ProSe direct communication 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 communication, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct communication bit to "ProSe direct communication supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message.
[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:
a) served by E-UTRAN and authorised for ProSe direct communication in the registered PLMN;
…
c) in EMM-IDLE mode and in limited service state as specified in 3GPP TS 23.122 [24] and authorized for ProSe direct communication for "not served by E-UTRAN", if the reason for the UE being in limited service state is one of the following:
…
ii) the UE received an ATTACH REJECT message or a TRACKING AREA UPDATE REJECT message or a SERVICE REJECT message with the EMM cause #11 "PLMN not allowed" as specified in 3GPP TS 24.301 [11] or a LOCATION UPDATING REJECT message or a GPRS ATTACH REJECT message or ROUTING AREA UPDATE REJECT message or SERVICE REJECT message with cause #11 "PLMN not allowed" as specified in 3GPP TS 24.008 [30]; 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]
Before initiating ProSe direct communication, the UE shall check with lower layers whether the selected radio parameters can be used in the current location without causing interference to other cells as specified in 3GPP TS 36.331 [12], and:
– if the lower layers indicate that the usage would not cause any interference, the UE shall initiate ProSe direct communication; or
NOTE 2: If the lower layers find that there exists a cell operating the provisioned radio resources (i.e., carrier frequency), and the cell belongs to the registered PLMN or a PLMN equivalent to the registered PLMN, and the UE is authorized for ProSe direct communication in this PLMN, the UE can use the radio parameters indicated by the cell as specified in 3GPP TS 36.331 [12].
– else if the lower layers report that one or more PLMNs operate in the provisioned radio resources (i.e. carrier frequency) then:
a) if the following conditions are met:
1) none of the PLMNs reported by the lower layers is the registered PLMN or equivalent to the registered PLMN; and
2) at least one of the PLMNs reported by the lower layers is in the list of authorised PLMNs for ProSe direct communication and provides radio resources for ProSe direct communication as specified in 3GPP TS 36.331 [12];
then the UE shall:
1) if in EMM-IDLE mode, perform PLMN selection triggered by ProSe direct communication as specified in 3GPP TS 23.122 [24]; or
2) else if in EMM-CONNECTED mode, either:
i) perform a detach procedure as specified in 3GPP TS 24.301 [11] and then perform PLMN selection triggered by ProSe direct communication as specified in 3GPP TS 23.122 [24]; or
ii) not initiate ProSe direct communication.
Whether the UE performs i) or ii) above is left up to UE implementation; or
b) else the UE shall not initiate ProSe direct communication.
If the registration to the selected PLMN is successful, the UE shall proceed with the procedure to initiate ProSe direct communication as specified in subclause 10.2.2.
[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 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.3.3.1a]
For sidelink communication an RRC connection is initiated only in the following case:
1> if configured by upper layers to transmit sidelink communication and related data is available for transmission:
2> if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType18 does not include commTxPoolNormalCommon;
…
NOTE: Upper layers initiate an RRC connection. The interaction with NAS is left to UE implementation.
[TS 36.331, clause 5.10.1a]
When it is specified that the UE shall perform a particular sidelink operation only if the conditions defined in this section are met, the UE shall perform the concerned sidelink operation only if:
1> if the UE’s serving cell is suitable (RRC_IDLE or RRC_CONNECTED); and if either the selected cell on the frequency used for sidelink operation belongs to the registered or equivalent PLMN as specified in TS 24.334 [69] or the UE is out of coverage on the frequency used for sidelink operation as defined in TS 36.304 [4, 11.4]; or
1> if the UE is camped on a serving cell (RRC_IDLE) on which it fulfils the conditions to support sidelink communication in limited service state as specified in TS 23.303 [68, 4.5.6]; and if either the serving cell is on the frequency used for sidelink operation or the UE is out of coverage on the frequency used for sidelink operation as defined in TS 36.304 [4, 11.4]; or
…
[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 SystemInformationBlockType18 is broadcast by the PCell:
2> ensure having a valid version of SystemInformationBlockType18 for the PCell;
…
2> if configured by upper layers to transmit sidelink communication:
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 SystemInformationBlockType18; or
3> if the last transmission of the SidelinkUEInformation message did not include commTxResourceReq; or if the information carried by the commTxResourceReq has changed since the last transmission of the SidelinkUEInformation message:
4> initiate transmission of the SidelinkUEInformation message to indicate the sidelink communication transmission resources required by the UE in accordance with 5.10.2.3;
2> else:
3> if the last transmission of the SidelinkUEInformation message included commTxResourceReq:
4> initiate transmission of the SidelinkUEInformation message to indicate it does no longer require sidelink communication transmission 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 SystemInformationBlockType18 is broadcast by the PCell:
…
2> if configured by upper layers to transmit sidelink communication:
3> include commTxResourceReq and set its fields as follows:
4> set carrierFreq to indicate the sidelink communication frequency i.e. the same value as indicated in commRxInterestedFreq if included;
4> set destinationInfoList to include the sidelink communication transmission destination(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.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:
1> if the conditions for sidelink operation as defined in 5.10.1a are met:
2> if in coverage on the frequency used for sidelink communication, as defined in TS 36.304 [4, 11.4]:
…
3> else (i.e. sidelink communication in RRC_IDLE or on cell other than PCell in RRC_CONNECTED):
4> if the cell chosen for sidelink communication transmission broadcasts SystemInformationBlockType18:
5> if SystemInformationBlockType18 includes commTxPoolNormalCommon:
6> configure lower layers to transmit the sidelink control information and the corresponding data using the pool of resources indicated by the first entry in commTxPoolNormalCommon;
19.1.1.3 Test description
19.1.1.3.1 Pre-test conditions
System Simulator:
SS-NW
– 4 cells with parameters defined in Table 19.1.1.3.1-1.
NOTE: The test only requires at maximum 2 cells to be active at any one instance.
Table 19.1.1.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
1 |
f1 |
HPLMN (PLMN1) |
|
2 |
f1 |
PLMN4 |
|
4 |
f1 |
PLMN2 |
|
11 |
f1 |
PLMN3 |
|
Note 1: PLMN1: PLMN1 in USIM EFPROSE_PLMN Note 2: The Frequency f1 shall be the frequency pre-configured in the UE for when UE is "not served by E-UTRAN". Note 3: 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 23 as defined in TS 36.508 [18] clause 4.4.3.1 is used in all active cells.
SS-UE
– SS-UE1. As defined in TS 36.508 [18], configured for and operating as ProSe Direct Communication receiving device on the resources which the UE is expected to use for transmission (as specified in the relevant procedure steps in Table 19.1.1.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.1.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 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, etc.).
Table 19.1.1.3.1-2: USIM Configuration
|
USIM field |
Value |
|
EFUST |
Service n°101 (ProSe) supported. |
|
EFPST |
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. |
|
|
EFAD |
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. 10 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).
Preamble:
– The UE is in State Switched OFF (state 1) according to TS 36.508 [18].
19.1.1.3.2 Test procedure sequence
Table 19.1.1.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.1.1.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 4 |
Cell 11 |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
"Off" |
"Off" |
"Off" |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-79 |
"Off" |
"Off" |
|
T2 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
-85 |
-79 |
"Off" |
|
T3 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
-87 |
"Off" |
|
T4 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
-87 |
-79 |
|
T5 |
Void |
– |
– |
– |
– |
– |
|
T6 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
-79 |
"Off" |
Table 19.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0 |
The SS configures: SW-NW – Cell 1 does not transmit SystemInformationBlockType18. |
– |
– |
– |
– |
|
0A |
The UE is switched on. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
0B |
Check: Does the Generic test procedure from step 1 to 16c1 for ‘UE Registration (State 2)’ defined in TS 36.508 [18] clause 4.5.2 take place during which the UE announces its ProSe direct communication capabilities in the ATTACH REQUEST message? |
– |
– |
0 |
– |
|
0C |
The SS-NW transmits a UPDATE UE LOCATION INFORMATION message which provides location data as the one pre-configured in the UE for ProSe communication when UE is "not served by E-UTRAN". |
<– |
UPDATE UE LOCATION INFORMATION |
– |
– |
|
0D |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
1 |
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. |
– |
– |
– |
– |
|
1A |
Check: Does the UE transmit during the next 3 transmission periods sidelink communication data in accordance with the resources preconfigured in the UE (the first entry in preconfigComm in SL-Preconfiguration defined in TS 36.508 [18], section 6.8.1.1 based on the UE’s own timing)? |
–> |
– |
0A |
F |
|
1B |
SS-NW starts transmitting SystemInformationBlockType18 not including commTxPoolNormalCommon (i.e. ProSe direct communication supported by the network, no resources provided yet). |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit an RRCConnectionRequest message? |
–> |
RRCConnectionRequest |
1 |
P |
|
3 |
SS-NW transmits an RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
4 |
Check: Does the UE transmit an RRCConnectionSetupComplete message and a SERVICE REQUEST message to request resources for Prose direct communication transmission? |
–> |
RRCConnectionSetupComplete SERVICE REQUEST |
1 |
P |
|
5 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication? |
–> |
SidelinkUEInformation |
1 |
P |
|
6 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
6A |
SS-NW changes SystemInformationBlockType18 to include commTxPoolNormalCommon. |
– |
– |
– |
– |
|
6B |
Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType18. |
– |
– |
– |
– |
|
7 |
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 indicated in Cell 1 SystemInformationBlockType18? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
2 |
P |
|
8-20 |
Void |
– |
– |
– |
– |
|
21 |
The SS configures: SW-NW Cell 1 and Cell 2 parameters according to the row "T1" in table 19.1.1.3.2-1-0 in order to simulate needs for cell reselection to Cell2. Cell 2 broadcasts SystemInformationBlockType18 including commTxPoolNormalCommon. |
– |
– |
– |
– |
|
21A |
Wait for 5 sec to allow the UE to adjust to cell changes and start transmission. |
– |
– |
– |
– |
|
22-26 |
Void |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2. |
– |
– |
– |
– |
|
27 |
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 indicated in the broadcast on Cell 2 SystemInformationBlockType18? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
3 |
P |
|
28 |
The SS configures: SS-NW Cell 2 and Cell 4 parameters according to the row "T2" in table 19.1.1.3.2-1-0 in order to simulate cell reselection to Cell 4. Cell 4 broadcasts SystemInformationBlockType18 providing different resources for sideling communication transmission than those provided on Cell 2. In addition to all other settings the syncTxThreshIC is included with value 7 (this is needed for TP5). NOTE 1: Value 7 is chosen to ensure that the Power level of Cell 4 is such that it is ensured that the RSRP measurement of the Cell 4 (serving) cell is NOT below the power value that corresponds to 7 (-85dBm). |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel to steps 4-5 in the procedure described in step 29, the event described in Table 19.1.1.3.2-4 takes place. |
– |
– |
– |
– |
|
29 |
Check: Does the Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 take place during which the UE announces its ProSe direct communication capabilities in the TRACKING AREA UPDATE REQUEST message? |
– |
– |
1 |
– |
|
30-32 |
Void |
– |
– |
– |
– |
|
33 |
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 indicated in the broadcasted on Cell 4 SystemInformationBlockType18? NOTE: 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 34 – 35 are repeated 3 times. |
– |
– |
– |
– |
|
34 |
Check: Does the UE transmit SLSS in the next transmission period? |
–> |
SLSS |
5 |
F |
|
35 |
Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 34? |
–> |
MasterInformationBlock-SL |
5 |
F |
|
36 |
The SS configures: SW-NW Cell 4 parameters according to the row "T3" in table 19.1.1.3.2-1-0. NOTE 2: The Power level of Cell 4 is such that it is ensured that the RSRP measurement of the serving cell is below the value of syncTxThreshIC (7 (-85dBm)) included in SystemInformationBlockType18. |
– |
– |
– |
– |
|
36A |
Wait for 1 sec to allow the UE to adjust to cell changes and start transmission. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 37 – 38 are repeated 3 times. |
– |
– |
– |
– |
|
37 |
Check: Does the UE transmit SLSS in the next transmission period in accordance with the information provided in the SystemInformationBlockType18 (SLSSID, a subframe indicated by syncOffsetIndicator does not corresponds to the first subframe of the discovery transmission pool)? |
–> |
SLSS |
5 |
P |
|
38 |
Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 37? |
–> |
MasterInformationBlock-SL |
5 |
P |
|
39 |
The SS configures: SW-NW Cell 4 and Cell 11 parameters according to the row "T4" in table 19.1.1.3.2-1-0 in order to simulate needs for cell reselection to Cell 11. Cell 11 broadcasts SystemInformationBlockType18 providing resources for sidelink communication transmission. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel to the procedure described in step 40 the event described in Table 19.1.1.3.2-2 takes place. |
– |
– |
– |
– |
|
40 |
The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place. |
– |
– |
– |
– |
|
41-43 |
Void. |
– |
– |
– |
– |
|
44 |
Check: Does the UE transmit during the next 3 transmission periods sidelink communication over the PC5 interface in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 transmitted on Cell 11? |
–> |
– |
6 |
F |
|
45-50 |
Void |
– |
– |
– |
– |
|
51 |
The SS configures: SW-NW Cell 11 and Cell 4 parameters according to the row "T6" in table 19.1.1.3.2-1-0 in order to simulate needs for cell reselection to Cell4. Cell 4 is transmitting SystemInformationBlockType18 providing resources for ProSe direct communication transmission. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4. |
– |
– |
– |
– |
|
51A |
The UE transmits an RRCConnectionRequest message on the cell specified in the test case. |
–> |
RRCConnectionRequest |
– |
– |
|
51B |
SS-NW transmits an RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
– |
EXCEPTION: In parallel to steps 52-53, the event described in Table 19.1.1.3.2-4 takes place. |
– |
– |
– |
– |
|
52 |
The UE transmits a TRACKING AREA UPDATE REQUEST message. |
–> |
RRCConnectionSetupComplete TRACKING AREA UPDATE REQUEST |
– |
– |
|
53 |
The SS-NW transmits a TRACKING AREA UPDATE REJECT message with cause value set to “PLMN not allowed“. |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
|
54 |
Void |
– |
– |
– |
– |
|
55 |
SS-NW transmits an RRCConnectionRelease message to release RRC connection |
<– |
RRCConnectionRelease |
– |
– |
|
56 |
Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink data communication over the PC5 interface in accordance with the resources indicated on Cell 4? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
8 |
P |
Table 19.1.1.3.2-2: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 5s ? |
–> |
SidelinkUEInformation |
6 |
F |
Table 19.1.1.3.2-3: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS-NW transmits a SecurityModeCommand message to activate AS security. |
<– |
RRC: SecurityModeCommand |
– |
– |
|
2 |
The UE transmits a SecurityModeComplete message and establishes the initial security configuration. |
–> |
RRC: SecurityModeComplete |
– |
– |
Table 19.1.1.3.2-4: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 5s? |
–> |
SidelinkUEInformation |
– |
– |
19.1.1.3.3 Specific message contents
Table 19.1.1.3.3-1: SystemInformationBlockType18 for Cell 1 (step 1B, Table 19.1.1.3.2-1)
|
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[1] |
Not Present |
||
|
SL-CommResourcePool-r12[2] |
Not Present |
||
|
} |
|||
|
commTxPoolNormalCommon-r12 |
Not Present |
||
|
commTxPoolExceptional-r12 |
Not Present |
||
|
commSyncConfig-r12 |
Not Present |
||
|
} |
|||
|
} |
|||
|
Note: SideLink direct communication supported but no resources set for transmission. |
|||
Table 19.1.1.3.3-1A: SystemInformationBlockType18 for Cell 1 (when active steps 6A onwards, Table 19.1.1.3.2-1)
|
Derivation Path: 36.508 [18], table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType18-r12 ::= SEQUENCE { |
|||
|
commConfig-r12 SEQUENCE { |
|||
|
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]. |
|||
Table 19.1.1.3.3-1B: SystemInformationBlockType18 for Cell 2 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 { |
|||
|
commTxPoolNormalCommon-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-CommResourcePool-r12 { |
|||
|
SL-CommResourcePool-r12[1] |
Not Present |
||
|
} |
|||
|
commTxPoolExceptional-r12 |
Not Present |
||
|
commSyncConfig-r12 |
Not Present |
||
|
} |
|||
|
} |
|||
|
Note 1: SideLink direct communication supported; resources for transmission in RRC_IDLE provided (commTxPoolNormalCommon – 1 pool SL-CommResourcePool-r12[2]). Note 2: The transmission resources provided on Cell 2 are different to those provided on Cell 1 – differences only in the field subframeBitmap. |
|||
Table 19.1.1.3.3-2: SystemInformationBlockType18 for Cell 4 and Cell 11 when active and unless otherwise stated
|
Derivation Path: 36.508 [18] , table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType18-r12 ::= SEQUENCE { |
|||
|
commConfig-r12 SEQUENCE { |
|||
|
commTxPoolNormalCommon-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-CommResourcePool-r12 { |
|||
|
SL-CommResourcePool-r12[2] |
Not Present |
||
|
} |
|||
|
commTxPoolExceptional-r12 |
Not Present |
||
|
commSyncConfig-r12 SEQUENCE (SIZE (1..maxSL-SyncConfig-r12)) OF SL-SyncConfig-r12 |
|||
|
SL-SyncConfig-r12[2] |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note 1: For the commSyncConfig/SL-SyncConfig-r12[1] settings, the syncTxThreshIC is included with value 7 = -85dBm – the threshold for starting transmission of SLSS (this is needed for TP5). Note 2: The transmission resources provided are different to those provided on Cell 2 – differences only in the field subframeBitmap. |
|||
Table 19.1.1.3.3-3: ATTACH REQUEST (step 0B Table 19.1.1.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) |
‘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’ |
ProSe direct communication Supported |
|
Table 19.1.1.3.3-4: ATTACH ACCEPT (step 0B Table 19.1.1.3.2-1; step 14 TS 36.508 [18] Table 4.5.2.3-1)
|
Derivation path: 36.508 [18], table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN4 |
Cell 1 |
|
Table 19.1.1.3.3-5: Message TRACKING AREA UPDATE REQUEST (step 29, Table 19.1.1.3.2-1; step 4 TS 36.508 [18] Table 4.5A.2.1-1 , and step 52, Table 19.1.1.3.2-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) |
‘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’ |
ProSe direct communication Supported |
|
Table 19.1.1.3.3-5AA: Message TRACKING AREA UPDATE REQUEST (step 40, Table 19.1.1.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 |
|
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’ |
ProSe direct communication Supported |
|
Table 19.1.1.3.3-5A: Message TRACKING AREA UPDATE REQUEST REJECT (step 53, Table 19.1.1.3.2-1)
|
Derivation path: 36.508 [18] , table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Cause |
PLMN not allowed |
||
Table 19.1.1.3.3-5B: RRCConnectionRequest (step 2, Table 19.1.1.3.2-1)
|
Derivation Path: 36.508 [18], 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.1.1.3.3-6: SidelinkUEInformation (step 5, Table 19.1.1.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 |
Not Present |
NOTE 1 |
|
|
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.1.3.3-7: Void
Table 19.1.1.3.3-8: MasterInformationBlock-SL (step 38, Table 19.1.1.3.2-1)
|
Derivation Path: 36.508 [18], table 4.6.1-4A0 |
Table 19.1.1.3.3-9: UPDATE UE LOCATION INFORMATION (step 0C, Table 19.1.1.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, EFPROSE_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 |
||