19.1.2 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 / 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.2.1 Test Purpose (TP)
(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 indicating the provision of resources for sidelink communication (commRxPool) }
ensure that {
when { UE receives a request from upper layers to receive sidelink communication }
then { UE is able to receive sidelink communication using the configured resources in Cell1/f1/PLMN1 }
}
(2)
Void
(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 (commRxPool) becomes the highest ranked cell, and, UE reselects to Cell2/f1/PLMN4 }
then { UE is able to receive sidelink communication using the configured resources in Cell2/f1/PLMN3}
}
(4)
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, UE having successfully initiated an RRC connection and completed Sidelink UE information procedure requesting sidelink communication reception resources and moved to RRC_IDLE }
ensure that {
when { Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType18 providing resources for sidelink communication (commRxPool includes multiple entries some including and others not including rxParametersNCell) becomes the highest ranked cell, and, UE reselects to Cell4/f1/PLMN2 }
then { UE is able to receive sidelink communication from two different devices one operating on the configured for rxParametersNCell resources in Cell4/f1/PLMN2 and one on the resources not including rxParametersNCell }
}
(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, UE having successfully completed Sidelink UE information procedure indicating the sidelink communication reception frequency of interest and receiving sidelink communication }
ensure that {
when { Cell11/f1/PLMN3 which is broadcasting SystemInformationBlockType18 providing resources for sidelink communication becomes the highest ranked cell, and, UE reselects to Cell11/f1/PLMN3 }
then { UE does not receive sidelink communication on the resources configured in Cell11/f1/PLMN3}
}
(6)
Void
19.1.2.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, TS 36.331, clauses 5.2.2.4, 5.2.2.25, 5.10.1a, 5.10.3. 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;
…
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 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;
[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.
19.1.2.3 Test description
19.1.2.3.1 Pre-test conditions
System Simulator:
SS-NW
– 4 cells with parameters defined in Table 19.1.2.3.1-1.
NOTE: The test only requires at maximum 2 cells to be active at any one instance.
Table 19.1.2.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 transmitting device on the resources provided by different cells (as specified in the relevant procedure steps in Table 19.1.2.3.2-1).
– SS-UE2
– As defined in TS 36.508 [18], configured for and operating as ProSe Direct Communication transmitting device transmitting as well Synchronisation information on the resources provided by different cells (as specified in the relevant procedure steps in Table 19.1.2.3.2-1).
– When SS-UE2 is simulated, SS-UE2 and SS-UE1 transmit simultaneously.
UE:
– ProSe related configuration
– The UE is authorised to perform ProSe Direct Communication; the UE is authorised to perform ProSe Direct Communication; the UE is equipped with a USIM containing values shown in Table 19.1.2.3.1-2, and, relevant to each of the supported services values as specified in TS 36.508 [18], section 4.9.3.1 (e.g. 2 PLMNs are authorised for ProSe Direct 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.2.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. 5 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 RB Established, UE Test Mode Activated (State 3A) with TEST LOOP MODE E being activated on Cell 1 according to TS 36.508 [18]. During the registration PLMN4 is assigned as Equivalent PLMN.
19.1.2.3.2 Test procedure sequence
Table 19.1.2.3.2-0 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" … "Tn" are to be applied subsequently. The exact instants on which these values shall be applied are described elsewhere in the present clause.
Table 19.1.2.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 |
-85 |
"Off" |
-79 |
"Off" |
|
T3 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
-85 |
-79 |
|
T4 |
Void |
|||||
|
T5 |
Void |
Table 19.1.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0 |
Close UE Test Loop with bit E0 in UE test loop mode E LB setup IE set to one (TEST LOOP MODE E, TRIGGER = RECEIVE) 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 |
– |
– |
|
0A |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
0B |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
1 |
Force the UE upper layer application to request reception of sidelink communication. |
– |
– |
– |
– |
|
1A |
Wait for [5] sec to allow the UE to process the request and start reception. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
2-6 |
Void |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 7 is repeated 3 times. |
– |
– |
– |
– |
|
7 |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool provides 2 pool for reception, the SS-UE1 shall use pool 1 (SL-CommResourcePool-r12[1])). NOTE: This step verifies TP1 – it is expected that the UE will be able to receive these packets – if they were received is checked in step 42. |
<– |
STCH PDCP SDU packet |
– |
– |
|
8-22 |
Void |
– |
– |
– |
– |
|
23 |
The SS configures: SS-NW Cell 1 and Cell 2 parameters according to the row "T1" in table 19.1.2.3.2-1-0 in order to simulate the need for cell reselection to Cell2/f1/PLMN4. Cell 2 broadcasts SystemInformationBlockType18 (commRxPool provides 2 pools for reception different to the resources provided on the previous cell on which the UE received ProSe direct communication). |
– |
– |
– |
– |
|
23A |
Wait for 5 sec to allow the UE to adjust to the cell changes |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2. |
– |
– |
– |
– |
|
24-27 |
Void |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 28 is repeated 3 times. |
– |
– |
– |
– |
|
28 |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool provides 2 pool for reception, the SS-UE1 shall use pool 2 – this is to verify that UE can read 2 pools and listen on both). NOTE: This step verifies TP3 – it is expected that the UE will be able to receive these packets – if they were received is checked in step 42. |
<– |
STCH PDCP SDU packet |
– |
– |
|
29-31 |
Void |
– |
– |
– |
– |
|
32 |
The SS configures: SS-NW Cell 2 and Cell 4 parameters according to the row "T2" in table 19.1.2.3.2-1-0 in order to simulate needs for cell reselection to Cell4/f1/PLMN2. Cell 4 transmits SystemInformationBlockType18, commRxPool includes two entries, one entry including and the other not including rxParametersNCell: the resources are different to the resources provided on the previous cell on which the UE received ProSe direct communication. |
– |
– |
– |
– |
|
– |
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 32A the event described in Table 19.1.2.3.2-3 takes place. |
– |
– |
– |
– |
|
32A |
The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place. |
– |
– |
– |
– |
|
33-39 |
Void |
– |
– |
– |
– |
|
40 |
SS-UE configures SS-UE2 to start transmitting Synchronisation information (SLSS and MasterInformationBlock-SL message, in the same subframe as SLSS) utilising the resources indicated in the SystemInformationBlockType18 (commRxPool the entry including rxParametersNCell commRxPool 2 (SL-CommResourcePool-r12[2]) and the relevant SLSSID (commSyncConfig-r12/SL-SyncConfig-r12[2]) ). |
<– |
SLSS MasterInformationBlock-SL |
– |
– |
|
40A |
Wait for 5 sec to allow the UE to receive the synchronisation information. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 40B-40C are repeated 3 times. |
– |
– |
– |
– |
|
40B |
SS-UE2 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool the entry including rxParametersNCell commRxPool 2 (SL-CommResourcePool-r12[2])). 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 42. |
<– |
STCH PDCP SDU packet |
– |
– |
|
40C |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool the entry NOT including rxParametersNCell commRxPool3 (SL-CommResourcePool-r12[3]) ). 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 42. |
<– |
STCH PDCP SDU packet |
– |
– |
|
40D |
SS-UE2 stops transmitting synchronisation information. |
– |
– |
– |
– |
|
40E |
Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place |
– |
– |
– |
– |
|
41 |
The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message. |
<– |
UE TEST LOOP PROSE PACKET COUNTER REQUEST |
– |
– |
|
42 |
Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER=12? NOTE: In this step all received until now packets are counted. |
–> |
UE TEST LOOP PROSE PACKET COUNTER RESPONSE |
1, 2, 3, 4 |
P |
|
42A |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
43 |
The SS configures: SS-NW Cell 4 and Cell 11 parameters according to the row "T3" in table 19.1.2.3.2-1-0 in order to simulate needs for cell reselection to Cell11/f1/PLMN3. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11. |
– |
– |
– |
– |
|
43A |
The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place. |
– |
– |
– |
– |
|
44-47 |
Void |
– |
– |
– |
– |
|
48 |
SS-UE1 transmits sidelink communication in the next transmission period in accordance with the resources indicated in the SystemInformationBlockType18 (commRxPool, commRxPool 1 (SL-CommResourcePool-r12[1])). NOTE: This step verifies TP5 – it is expected that the UE will NOT be able to receive these packets – if they were received is checked in step 50. |
<– |
STCH PDCP SDU packet |
– |
– |
|
48A |
Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place |
– |
– |
– |
– |
|
49 |
The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message. |
<– |
UE TEST LOOP PROSE PACKET COUNTER REQUEST |
– |
– |
|
50 |
Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER>12? |
–> |
UE TEST LOOP PROSE PACKET COUNTER RESPONSE |
5 |
F |
|
51-58 |
Void |
– |
– |
– |
– |
|
59 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
Table 19.1.2.3.2-2: Void
Table 19.1.2.3.2-3: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The UE transmits a SidelinkUEInformation message. |
–> |
SidelinkUEInformation |
– |
– |
9.1.2.3.3 Specific message contents
Table 19.1.2.3.3-1: SystemInformationBlockType18 for cell 1 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 { |
|||
|
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 reception provided in 2 commRxPools. One resource for transmission (SL-CommResourcePool-r12[1]) matching one of the resources for reception is provided and will be used by the SS-UE for transmission. |
|||
Table 19.1.2.3.3-1A: SystemInformationBlockType18 for cell 2 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 { |
|||
|
commRxPool-r12 SEQUENCE (SIZE (1..maxSL-RxPool-r12)) OF SL-CommResourcePool-r12 { |
|||
|
SL-CommResourcePool-r12[2] SEQUENCE { |
RxPool 2 |
||
|
rxParametersNCell-r12 |
Not Present |
||
|
} |
|||
|
SL-CommResourcePool-r12[3] |
Not Present |
||
|
} |
|||
|
commTxPoolExceptional-r12 |
Not Present |
||
|
commSyncConfig-r12 |
Not Present |
||
|
} |
|||
|
} |
|||
|
Note: SideLink direct communication supported; resources for reception provided in 2 commRxPools. The new Pool 2 (SL-CommResourcePool-r12[2]) is what SIB18 on Cell 2 differs to SIB18 on Cell 1 and this pool will be used by the SS-UE for transmission. |
|||
Table 19.1.2.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 { |
|||
|
commRxPool-r12 SEQUENCE (SIZE (1..maxSL-RxPool-r12)) OF SL-CommResourcePool-r12 { |
|||
|
SL-CommResourcePool-r12[2] SEQUENCE { |
RxPool 2 |
||
|
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 11000000 00000000 |
bs40-r12 |
FDD |
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
commTxPoolNormalCommon-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-CommResourcePool-r12 { |
|||
|
SL-CommResourcePool-r12[2] SEQUENCE { |
TxPool 2 |
||
|
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 11000000 00000000 |
bs40-r12 |
FDD |
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
commTxPoolExceptional-r12 |
Not Present |
||
|
} |
|||
|
} |
|||
|
Note 1: SystemInformationBlockType18 providing different resources for sidelink communication reception than those provided on Cell 2 (different SL-CommResourcePool-r12[2] and new in SL-CommResourcePool-r12[3]) with commRxPool 2 (SL-CommResourcePool-r12[2]) also containing rxParametersNCell linked to the commSyncConfig-r12/SL-SyncConfig-r12[2]; the SS-UEs will be transmitting on SL-CommResourcePool-r12[2] and SL-CommResourcePool-r12[3]. |
|||
Table 19.1.2.3.3-3: Message 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.2.3.3-4: ATTACH ACCEPT (preamble)
|
Derivation path: 36.508, table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Equivalent PLMNs |
PLMN4 |
Cell 1 |
|
Table 19.1.2.3.3-5: Message TRACKING AREA UPDATE REQUEST (step 32A, Table 19.1.2.3.2-1; step 4, TS 36.508 [18] Table 4.5A.2.1-1)
|
Derivation path: 36.508 [18] , table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS update type |
|||
|
"Active" flag |
‘1’B |
||
|
UE network capability |
|||
|
ProSe (octet 7, bit 7) |
‘1’ |
ProSe Supported |
|
|
..ProSe direct discovery (ProSe-dd) (octet 7, bit 8) |
‘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.2.3.3-5A: Message TRACKING AREA UPDATE REQUEST (step 43A, Table 19.1.2.3.2-1; step 4, TS 36.508 [18] Table 4.5A.2.1-1)
|
Derivation path: 36.508 [18], table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
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.2.3.3-6: SidelinkUEInformation (step 1, Table 19.1.2.3.2-3)
|
Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-21A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformation-r12-IEs |
|||
|
commRxInterestedFreq-r12 SEQUENCE { |
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 |
Not Present |
NOTE 1 |
|
|
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.2.3.3-7: Void
Table 19.1.2.3.3-8: CLOSE UE TEST LOOP (step 0, Table 19.1.2.3.2-1)
|
Derivation Path: 36.508, 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.2.3.3-9: MasterInformationBlock-SL (step 40, Table 19.1.2.3.2-1)
|
Derivation Path: 36.508 [18], table 4.6.1-4A0 |