19.1.5 ProSe Direct Communication/Pre-configured authorisation / UE camped on an E-UTRAN cell not operating on the carrier frequency provisioned for ProSe direct service / Utilisation of the resources of (not serving) cells/PLMNs / Transmission and Reception
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.5.1 Test Purpose (TP)
(1)
with { UE being authorized for performing ProSe Direct Communication in two PLMNs (PLMN1 and PLMN2) being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" carrier frequency f1, and, UE in RRC_IDLE on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to transmit prose direct communication, and, the lower layers find that there exists a cell Cell2/f1/PLMN1 operating the provisioned radio resources (i.e. carrier frequency), and the cell belongs to the registered PLMN }
then { UE is able to transmit sidelink communication using the assigned/configured resources in Cell2/f1/PLMN1 without re-selection to Cell2/f1/PLMN1 }
}
(2)
with { UE being authorized 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" carrier frequency f1, and, UE in RRC_IDLE on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to receive prose direct communication, and, the lower layers find that there exists a cell Cell2/f1/PLMN1 operating the provisioned radio resources (i.e. carrier frequency), and the cell belongs to the registered PLMN }
then { UE is able to receive sidelink communication transmitted in accordance with the assigned/configured resources in Cell2/f1/PLMN1 without re-selection to Cell2/f1/PLMN1 }
}
(3)
with { UE being authorized 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" carrier frequency f1, and, UE in RRC_IDLE on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to transmit prose direct communication, and, the lower layers find that there exists a cell Cell4/f1/PLMN3 operating the provisioned radio resources (i.e. carrier frequency), and the cell belongs to a PLMN equivalent to the registered PLMN }
then { UE is able to transmit sidelink communication using the assigned/configured resources in Cell4/f1/PLMN3 without re-selection to Cell4/f1/PLMN3 }
}
(4)
with { UE being authorized 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" carrier frequency f1, and, UE in RRC_IDLE on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to receive prose direct communication, and, the lower layers find that there exists a cell Cell4/f1/PLMN3 operating the provisioned radio resources (i.e. carrier frequency), and the cell belongs to a PLMN equivalent to the registered PLMN }
then { UE is able to receive sidelink communication transmitted in accordance with the assigned/configured resources in Cell4/f1/PLMN3 without re-selection to Cell4/f1/PLMN3 }
}
(5) Void
(6) Void
(7)
with { UE being authorized 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" carrier frequency f1, and, UE in RRC_CONNECTED on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to transmit prose direct communication, and, UE is capable of simultaneous transmission of EUTRA and sidelink communication (on different carriers), and, the lower layers find that there are not cells operating on the preconfigured radio resources (i.e. carrier frequency) }
then { UE is able to transmit sidelink communication using the preconfigured for "not served by E-UTRAN" resources }
}
(8)
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" carrier frequency f1, and, UE in RRC_CONNECTED on Cell3/f2/PLMN1 which does not indicate that ProSe direct communication is supported by the network }
ensure that {
when { UE wants to transmit prose direct communication, and, UE us capable of simultaneous transmission of EUTRA and sidelink communication (on different carriers), and, the lower layers find that there are not cells operating on the preconfigured radio resources (i.e. carrier frequency) }
then { UE is able to receive sidelink communication using the preconfigured "not served by E-UTRAN" resources }
}
19.1.5.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, TS 36.331, clauses 5.2.2.4, 5.2.2.25, 5.10.1a, 5.10.3, 5.10.4. 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:
a) served by E-UTRAN and authorised for ProSe direct communication in the registered PLMN;
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.
If the UE is camped on an E-UTRAN cell not operating on the carrier frequency provisioned for ProSe direct communication which indicates that ProSe direct communication is supported by the network, the UE can perform either ProSe direct communication procedures specified in subclause 10.2.2 or 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
…
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 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.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
[TS 36.331, clause 5.10.3]
A UE capable of sidelink communication that is configured by upper layers to receive sidelink communication 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> if the cell chosen for sidelink communication reception broadcasts SystemInformationBlockType18 including commRxPool:
4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by commRxPool;
NOTE 1: If commRxPool includes one or more entries including rxParametersNCell, the UE may only monitor such entries if the associated PSS/SSS or SLSSIDs is detected. When monitoring such pool(s), the UE applies the timing of the concerned PSS/SSS or SLSS.
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:
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;
5> else:
6> if the last connection establishment was initiated to request sidelink communication transmission resources and resulted in T300 expiry; and
6> if the cell on which the UE initiated connection establishment broadcasts SystemInformationBlockType18 including commTxPoolExceptional:
7> from the moment T300 expired, as specified in 5.3.3.6, until receiving an RRCConnectionReconfiguration including sl-CommConfig or until receiving an RRCConnectionRelease or an RRCConnectionReject;
8> configure lower layers to transmit the sidelink control information and the corresponding data using the pool of resources indicated by the first entry in commTxPoolExceptional;
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;
19.1.5.3 Test description
19.1.5.3.1 Pre-test conditions
System Simulator:
SS-NW
– 3 cells with parameters defined in Table 19.1.5.3.1-1.
NOTE: The test only requires at maximum 2 cells to be active at any one instant.
Table 19.1.5.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
3 |
f2 |
HPLMN (PLMN1) |
|
2 |
f1 |
PLMN1 |
|
4 |
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". The Frequency f2 is a frequency for which the UE is not authorised/preconfigured for ProSe. |
||
– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used on Cell 3 (Cell 3 does not broadcast SIB18). System information combination 23 as defined in TS 36.508 [18] clause 4.4.3.1 is used on Cell 2 and Cell 4when active.
SS-UE
– SS-UE1.
– As defined in TS 36.508 [18], configured for and operating as ProSe Direct Communication transmitting and receiving device on the resources provided by cells Cell 2 and Cell 4 when active (as specified in the relevant procedure steps in Table 19.1.5.3.2-1).
– SS-UE2.
– As defined in TS 36.508 [18], configured for and operating as ProSe Direct Communication transmitting and receiving device on the resources configured in the UE for transmission/reception of ProSe Direct Communication when "not served by E-UTRAN".
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.5.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.5.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. 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).
Preamble:
– The UE is in state Generic RB Established, UE Test Mode E Activated (State 3A) according to [18] on Cell 3. During the registration PLMN3 is assigned as Equivalent PLMN.
19.1.5.3.2 Test procedure sequence
Table 19.1.5.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.5.3.2-0: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 3 |
Cell 2 |
Cell 4 |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
"Off" |
"Off" |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
-85 |
"Off" |
|
T2 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
"Off" |
-85 |
|
T3 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
"Off" |
"Off" |
Table 19.1.5.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
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 |
– |
– |
|
2 |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
2A |
The SS-NW sends UPDATE UE LOCATION INFORMATION message which provides location data = to one of the location areas pre-configured in the UE for prose communication (e.g. area 1). |
<– |
UPDATE UE LOCATION INFORMATION |
– |
– |
|
3 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
4 |
The SS configures: SS-NW Cell 3 and Cell 2 parameters according to the row "T1" in table 19.1.5.3.2-0. Cell 2 is transmitting SystemInformationBlockType18 providing resources for transmission in RRC_IDLE. |
– |
– |
– |
– |
|
5 |
Wait for 5 sec to allow the UE to acquire the SystemInformationBlockType18 transmitted on Cell 2. |
||||
|
6 |
Force the UE upper layer application to request continuous transmission and reception of sidelink communication (the transmissions should be 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. |
– |
– |
– |
– |
|
6A |
Wait for 5 sec to allow the UE to start transmission. |
– |
– |
– |
– |
|
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 provided by Cell 2 (commTxPoolNormalCommon/SL-CommResourcePool-r12[1])? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
1 |
P |
|
– |
EXCEPTION: Step 8 is repeated 3 times. |
– |
– |
– |
– |
|
8 |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 on cell 2. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType18/commRxPool-r12/SL-CommResourcePool-r12[3]. Note that SIB18 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. For avoiding testing complexity, the transmission pools in step 11 and 12 are deliberately different to avoid collisions between the transmissions of the UE and the SS-UE1. NOTE: This step verifies TP2 – it is expected that the UE will be able to receive these packets – if they were received is checked in step 25. |
<– |
STCH PDCP SDU packet |
– |
– |
|
9 |
The SS configures: SS-NW Cell 3, Cell 2 and Cell 4 parameters according to the row "T2" in table 19.1.5.3.2-0. Cell 4 is transmitting SystemInformationBlockType18 providing resources for transmission in RRC_IDLE. |
– |
– |
– |
– |
|
10 |
Wait for 5 sec to allow the UE to acquire the SystemInformationBlockType18 transmitted on Cell 4 |
||||
|
11 |
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 provided by Cell 4 (commTxPoolNormalCommon/SL-CommResourcePool-r12[2])? 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 |
|
– |
EXCEPTION: Step 12 is repeated 3 times. |
– |
– |
– |
– |
|
12 |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool) on cell 4. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType18/commRxPool-r12/SL-CommResourcePool-r12[3]. Note that SIB18 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. For avoiding testing complexity, the transmission pools in step 11 and 12 are deliberatelydifferent to avoid collisions between the transmissions of the UE and the SS-UE1. NOTE: This step verifies TP4 – it is expected that the UE will be able to receive these packets – if they were received is checked in step 25. |
<– |
STCH PDCP SDU packet |
– |
– |
|
13-22 |
Void |
– |
– |
– |
– |
|
23 |
Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place |
– |
– |
– |
– |
|
24 |
The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message. |
<– |
UE TEST LOOP PROSE PACKET COUNTER REQUEST |
– |
– |
|
25 |
Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER=6? |
–> |
UE TEST LOOP PROSE PACKET COUNTER RESPONSE |
2,4 |
P |
|
26 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
– |
EXCEPTION: Steps 27a1 – 27a13 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place if the UE is capable of simultaneous transmission/reception of EUTRA and sidelink communication (on different carriers). |
– |
– |
– |
– |
|
27a1 |
IF pc_commSimultaneousTx THEN The SS configures: SS-NW Cell 3, and Cell 4 parameters according to the row "T 3" in table 19.1.5.3.2-0. |
– |
– |
– |
– |
|
27a2 |
Wait for 5 sec to allow the UE to adjust to the cell changes and continue transmission accordingly. |
– |
– |
– |
– |
|
27a3 |
Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place on Cell 3. |
– |
– |
– |
– |
|
27a4-27a7 |
Void. |
– |
– |
– |
– |
|
27a8 |
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 pre-configured for "not served by E-UTRAN" resources on frequency f1? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
7 |
P |
|
27a9 |
Force the UE upper layer application to stop continuous transmission but keep reception of sidelink communication. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 27a9 is repeated 3 times. |
– |
– |
– |
– |
|
27a10 |
SS-UE2 transmits sidelink communication in the next transmission period in accordance with the resources pre-configured in the UE for "not served by E-UTRAN" (on frequency f1). NOTE: This step verifies TP8 – it is expected that the UE will be able to receive these packets – if they were received is checked in step 27a12. |
<– |
STCH PDCP SDU packets |
– |
– |
|
27a11 |
The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message. |
<– |
UE TEST LOOP PROSE PACKET COUNTER REQUEST |
– |
– |
|
27a12 |
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 |
8 |
P |
|
27a13 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
Table 19.1.5.3.2-2: Void
19.1.5.3.3 Specific message contents
Table 19.1.5.3.3-1: 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 { |
|||
|
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.5.3.3-1A: SystemInformationBlockType18 for Cell 4 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[1] |
Not Present |
||
|
SL-CommResourcePool-r12[3] SEQUENCE { |
|||
|
sc-TF-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000011 00000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
} |
|||
|
ue-SelectedResourceConfig-r12 SEQUENCE { |
|||
|
data-TF-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000000 00000000 00000011 1100000000 00000000 |
bs40-r12 |
FDD |
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
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: Different to the pool provided in Cell 2SideLink direct communication supported; resources for transmission in RRC_IDLE provided (commTxPoolNormalCommon – 1 pool, SL-CommResourcePool-r12[2]) – Different to the pool provided in Cell 2; resources for reception in RRC_IDLE provided (commRxPool – 2 pools SL-CommResourcePool-r12[2], SL-CommResourcePool-r12[3]) – different to the pool used on Cell 2. |
|||
Table 19.1.5.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’ |
ProSe direct communication Supported |
|
Table 19.1.5.3.3-3: ATTACH ACCEPT (preamble)
|
Derivation path: 36.508 [18], table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN3 |
Cell 1 |
|
Table 19.1.5.3.3-4: Void
Table 19.1.5.3.3-5: Void
Table 19.1.5.3.3-6: CLOSE UE TEST LOOP (step 1, Table 19.1.5.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.5.3.3-7: UPDATE UE LOCATION INFORMATION (step 2A, Table 19.1.5.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 |
||