19.1.3 ProSe Direct Communication/Pre-configured authorisation / UE in RRC_CONNECTED on an E-UTRAN cell operating on the carrier frequency provisioned for ProSe direct service / Utilisation of the resources of (serving) cells/PLMNs / Transmission / RRC connection reconfiguration with/without mobilityControlInfo / RRC connection re-establishment

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.3.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_CONNECTED on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication }

ensure that {

when { UE receives a request from upper layers to transmit sidelink communication }

then { UE successfully completes a Sidelink UE information procedure to indicate the sidelink communication transmission resources required, and, UE is able to transmit sidelink communication using the configured resources in Cell1/f1/PLMN1 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) }

}

(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_CONNECTED on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having successfully completed Sidelink UE information procedure to indicate the sidelink communication transmission resources required and transmitting sidelink communication using the configured resources in Cell1/f1/PLMN1 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated ) }

ensure that {

when { UE receives RRCConnectionReconfiguration message which does not include mobilityControlInfo and includes commTxResources set to release }

then { UE from the next SC period releases the resources allocated for sidelink communication transmission previously configured by commTxResources in Cell1/f1/PLMN1, and, UE re-starts transmission of sidelink communication when resources become available (commTxResources set to setup, scheduled and resources provided in sc-CommTxConfig }

}

(2A)

with { UE being authorised 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_CONNECTED on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having successfully completed Sidelink UE information procedure requesting sidelink communication transmission resources and transmitting sidelink communication }

ensure that {

when { UE receives a request from upper layers to stop sidelink communication transmission }

then { the UE transmits a SidelinkUEInformation message indicating it does no longer require sidelink communication transmission resources, and, stops sidelink communication transmission on 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_CONNECTED on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having sent a SidelinkUEInformation message requesting sidelink communication transmission resources on Cell1/f1/PLMN1 }

ensure that {

when { UE receives RRCConnectionReconfiguration message which includes mobilityControlInfo (handover) less than 1 sec after the UE transmitted the SidelinkUEInformation message, and, MAC successfully completes the random access procedure to the targeted PCell Cell2/f1/PLMN4 (equivalent PLMN) which is broadcasting SystemInformationBlockType18 }

then { UE initiates a Sidelink UE information procedure in Cell2/f1/PLMN4 requesting sidelink communication transmission resources, and, UE is able to transmit sidelink communication using the configured resources in Cell2/f1/PLMN4 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) }

}

(4)

with { UE being authorised 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_CONNECTED on Cell2/f1/PLMN4 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having sent a SidelinkUEInformation message requesting sidelink communication transmission resources on Cell2/f1/PLMN4 }

ensure that {

when { UE detects radio link failure >1 sec after the UE transmitted the SidelinkUEInformation message, and, T301 is running and the cell on which the UE initiated connection re-establishment (Cell1/f1/PLMN1) broadcasts SystemInformationBlockType18 including commTxPoolExceptional }

then { UE transmits sidelink communication using the pool of resources indicated by the first entry in commTxPoolExceptional on Cell1/f1/PLMN1, and, after the T301 expires UE initiates a Sidelink UE information procedure requesting sidelink communication transmission resources, and, UE is able to transmit sidelink communication using the configured resources in Cell1/f1/PLMN1 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) }

}

(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_CONNECTED on Cell1/f1/PLMN1 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE transmitting and receiving sidelink communication using the configured resources in Cell1/f1/PLMN1 (commTxPoolNormalDedicated and commRxPool) }

ensure that {

when { UE receives RRCConnectionReconfiguration message which includes mobilityControlInfo (handover), and, MAC successfully completes the random access procedure to the targeted PCell Cell4/f1/PLMN2 and the cell is broadcasting SystemInformationBlockType18 }

then { UE successfully completes a Sidelink UE information procedure requesting sidelink communication transmission resources, and, UE is able to transmit sidelink communication using the configured resources in Cell4/f1/PLMN2 }

}

(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_CONNECTED on Cell4/f1/PLMN2 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having successfully completed Sidelink UE information procedure requesting sidelink communication transmission resources and transmitting sidelink communication }

ensure that {

when { UE is in RRC_CONNECTED, and, networkControlledSyncTx is configured and set to on }

then { UE transmits SLSS and MasterInformationBlock-SL message in the same subframe }

}

(7)

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_CONNECTED on Cell4/f1/PLMN2 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having successfully completed Sidelink UE information procedure requesting sidelink communication transmission resources and transmitting sidelink communication }

ensure that {

when { UE is in RRC_CONNECTED, and, networkControlledSyncTx is not configured; and syncTxThreshIC is included in SystemInformationBlockType18, and, 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 }

}

(8) Void

(9)

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_CONNECTED on Cell4/f1/PLMN2 which is operating on the same carrier frequency as the one pre-configured in the UE and is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication, and, UE having successfully completed Sidelink UE information procedure requesting sidelink communication transmission resources and transmitting sidelink communication }

ensure that {

when { UE receives RRCConnectionReconfiguration message including mobilityControlInfo, and, MAC successfully completes the random access procedure to the targeted PCell Cell11/f1/PLMN3 which is broadcasting SystemInformationBlockType18 }

then { UE 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 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated) }

}

(10)

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", and, UE in RRC_CONNECTED on Cell11/f1/PLMN3 which is broadcasting SystemInformationBlockType18 indicating the provision of resources for sidelink communication on the serving PLMN, and, UE has previously successfully completed a Sidelink UE information procedure requesting sidelink communication transmission resources }

ensure that {

when { UE receives RRCConnectionReconfiguration message including mobilityControlInfo, and, MAC successfully completes the random access procedure to the targeted PCell Cell1/f1/PLMN1 which is NOT broadcasting SystemInformationBlockType18 }

then { UE does not transmit a SidelinkUEInformation message to indicate the transmission resources required, and, does not transmit sidelink communication over the PC5 in Cell1/f1/PLMN1 }

}

19.1.3.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.3.5.3, 5.3.5.4, 5.3.7.5, 5.3.10.15, 5.10.1a, 5.10.2.1, 5.10.2.2, 5.10.2.3, 5.10.4, 5.10.7.1, 5.10.7.2, 5.10.7.3, 5.10.7.4, 5.10.9.1, 5.10.9.2. Unless otherwise stated these are Rel-12 requirements.

[TS 24.334, clause 5.1.1]

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

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

[TS 24.334, clause 5.1.2]

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

[TS 24.334, clause 10.2.1]

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

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.

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

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.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

…

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

…

2> if SystemInformationBlockType18 is broadcast by the target PCell; and the UE transmitted a SidelinkUEInformation message including commRxInterestedFreq or commTxResourceReq during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or:

…

3> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;

[TS 36.331, clause 5.3.7.5]

NOTE 1: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> consider the current cell to be the PCell;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

…

1> if SystemInformationBlockType18 is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message including commRxInterestedFreq or commTxResourceReq during the last 1 second preceding detection of radio link failure; or

…

2> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;

[TS 36.331, clause 5.3.10.15]

The UE shall:

1> if the RRCConnectionReconfiguration message includes the sl-CommConfig:

2> if commTxResources is included and set to setup:

3> from the next SC period use the resources indicated by commTxResources for sidelink communication transmission, as specified in 5.10.4;

2> else if commTxResources is included and set to release:

3> from the next SC period, release the resources allocated for sidelink communication transmission previously configured by commTxResources;

[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.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> if the UE is in RRC_CONNECTED and uses the PCell for sidelink communication:

4> if the UE is configured, by the current PCell/ the PCell in which physical layer problems or radio link failure was detected, with commTxResources set to scheduled:

5> if T310 or T311 is running; and if the PCell at which the UE detected physical layer problems or radio link failure broadcasts SystemInformationBlockType18 including commTxPoolExceptional; or

5> if T301 is running and the cell on which the UE initiated connection re-establishment broadcasts SystemInformationBlockType18 including commTxPoolExceptional:

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 commTxPoolExceptional;

5> else:

6> configure lower layers to request E-UTRAN to assign transmission resources for sidelink communication;

4> else if the UE is configured with commTxPoolNormalDedicated:

5> configure lower layers to transmit the sidelink control information and the corresponding data using the pool of resources indicated by the first entry in commTxPoolNormalDedicated;

[TS 36.331, clause 5.10.7.1]

Figure 5.10.7.1-1: Synchronisation information transmission for sidelink communication, in (partial) coverage

…

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

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

[TS 36.331, clause 5.10.7.2]

A UE capable of sidelink communication that is configured by upper layers to transmit sidelink communication shall, irrespective of whether or not it has data to transmit:

1> if the conditions for sidelink operation as defined in 5.10.1a are met:

2> if in RRC_CONNECTED; and if networkControlledSyncTx is configured and set to on:

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

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

A UE shall, when transmitting sidelink communication in accordance with 5.10.4 and when the following conditions are met:

1> if in coverage on the frequency used for sidelink communication, as defined in TS 36.304 [4, 11.4]:

2> if the UE is in RRC_CONNECTED; and networkControlledSyncTx is not configured; and syncTxThreshIC is included in SystemInformationBlockType18; and the RSRP measurement of the cell chosen for sidelink communication transmission is below the value of syncTxThreshIC; or

2> if the UE is in RRC_IDLE; and syncTxThreshIC is included in SystemInformationBlockType18; and the RSRP measurement of the cell chosen for sidelink communication transmission is below the value of syncTxThreshIC:

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

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

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

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

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

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

[TS 36.331, clause 5.10.7.3]

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

…

1> if triggered by sidelink communication:

2> if in coverage on the frequency used for sidelink communication, as defined in TS 36.304 [4, 11.4]:

3> select the SLSSID included in the entry of commSyncConfig that is included in the received SystemInformationBlockType18 and includes txParameters;

3> use syncOffsetIndicator corresponding to the selected SLSSID;

3> if in RRC_CONNECTED; and if networkControlledSyncTx is configured and set to on:

4> select the subframe(s) indicated by syncOffsetIndicator;

3> else (when transmitting communication):

4> select the subframe(s) indicated by syncOffsetIndicator within the SC period in which the UE intends to transmit sidelink control information or data;

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

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

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

3> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlock-SL message received from this UE is set to FALSE while the SLSS from this UE is part of the set defined for out of coverage, see TS 36.211 [21]:

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

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

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

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

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

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

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

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

[TS 36.331, clause 5.10.7.4]

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

1> if in coverage on the frequency used for sidelink communication, as defined in TS 36.304 [4, 11.4]:

2> set inCoverage to TRUE;

2> set sl-Bandwidth to the value of ul-Bandwidth as included in the received SystemInformationBlockType2 of the cell chosen for sidelink communication;

2> if tdd-Config is included in the received SystemInformationBlockType1:

3> set subframeAssignmentSL to the value representing the same meaning as of subframeAssignment that is included in tdd-Config in the received SystemInformationBlockType1;

2> else:

3> set subframeAssignmentSL to none;

2> if syncInfoReserved is included in an entry of commSyncConfig from the received SystemInformationBlockType18;

3> set reserved to the value of syncInfoReserved in the received SystemInformationBlockType18;

2> else:

3> set all bits in reserved to 0;

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

2> set inCoverage to FALSE;

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

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

2> set inCoverage to FALSE;

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

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

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

[TS 36.331, clause 5.10.9.1]

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

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

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

A UE configured to receive or transmit sidelink communication shall:

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

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

[TS 36.331, clause 5.10.9.2]

Upon receiving MasterInformationBlock-SL, the UE shall:

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

19.1.3.3 Test description

19.1.3.3.1 Pre-test conditions

System Simulator:

SS-NW

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

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

Table 19.1.3.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
PLMN2: PLMN2 in USIM EFPROSE_PLMN
PLMN3: MCC = MCC of PLMN1 in USIM EFPROSE_PLMN; MNC=03.
PLMN4 is an equivalent PLMN to PLMN1; MCC = MCC of PLMN1 in USIM EFPROSE_PLMN; MNC=04.

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 and operating for/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.3.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.3.3.3-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.3.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. 12 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 2 RRC_IDLE on Cell 1 according to TS 36.508 [18]. During the registration PLMN4 is assigned as Equivalent PLMN.

19.1.3.3.2 Test procedure sequence

Table 19.1.3.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.3.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"

"Off"

"Off"

T3

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

-79

"Off"

T4

Cell-specific RS EPRE

dBm/15kHz

"Off"

"Off"

-87

"Off"

T5

Cell-specific RS EPRE

dBm/15kHz

"Off"

"Off"

-87

-79

T6

Cell-specific RS EPRE

dBm/15kHz

-79

"Off"

"Off"

-85

Table 19.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

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.

–

–

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1.

–

–

–

–

2-5

Void.

–

–

–

–

6

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in RRC_CONNECTED in the next 5 sec?

–>

SidelinkUEInformation

1

P

7

SS-NW transmits an RRCConnectionReconfiguration message assigning sidelink communication transmission resources for RRC_CONNECTED (commTxResources set to setup, ue-Selected and resources provided in commTxPoolNormalDedicated; the provided Tx resources are different to the Tx resources for RRC_IDLE provided in SIB18).

<–

RRCConnectionReconfiguration

–

–

8

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

9

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 RRCConnectionReconfiguration?

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

10

SS-NW transmits an RRCConnectionReconfiguration message requesting the UE to release the resources allocated for sidelink communication transmission in RRC_CONNECTED (commTxResources set to release).

<–

RRCConnectionReconfiguration

–

–

11

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

12

Check: Does the UE transmit during the next 3 transmission periods sidelink communication data over the PC5 interface on the requested to be released resources in the next transmission period?

–>

–

2

F

13

SS-NW transmits an RRCConnectionReconfiguration message providing new resources for sidelink communication transmission in RRC_CONNECTED (commTxResources set to setup , scheduled and resources provided in sc-CommTxConfig; the provided Tx resources are different to the Tx resources for RRC_IDLE provided in SIB18).

<–

RRCConnectionReconfiguration

–

–

14

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

14A

Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface accordance with the resources indicated in the RRCConnectionReconfiguration?

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

14B

Force the UE upper layer application to request stop of sidelink communication.

–

–

–

–

14C

Check: Does the UE transmit a SidelinkUEInformation message indicating it does no longer require sidelink communication transmission resources in the next 5 sec?

–>

SidelinkUEInformation

2A

P

–

EXCEPTION: Step 14D is repeated 3 times.

NOTE: Depending on the size of the sidelink communication data a STCH PDCP SDU may fit in one sidelink transmission period but may as well be fragmented over multiple transmissions periods.

–

–

–

–

14D

Check: Does the UE transmit during the next 3 transmission periods sidelink communication data over the PC5 interface in the next transmission period in accordance with the resources indicated in the last RRCConnectionReconfiguration message?

–>

–

2A

F

14E

Force the UE upper layer application to request continuous transmission of sidelink communication.

–

–

–

–

15

The UE transmits a SidelinkUEInformation message requesting resources for transmission of sidelink communication.

–>

SidelinkUEInformation

–

–

16

The SS configures:

SW-NW

Cell 1 and Cell 2 parameters according to the row "T1" in table 19.1.3.3.2-0 in order to simulate needs for handover.

Cell 2 broadcasts SystemInformationBlockType18 including commTxPoolExceptional.

–

–

–

–

17

SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover).

NOTE: To achieve the TP this message shall be sent less than 1 sec after the message in step 15.

<–

RRCConnectionReconfiguration

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2.

–

–

–

–

18

The UE submits RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

19

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 1 sec?

–>

SidelinkUEInformation

3

P

20

SS-NW transmits an RRCConnectionReconfiguration message assigning sidelink communication transmission scheduled resources (commTxResources set to setup, scheduled and resources provided in sc-CommTxConfig).

<–

RRCConnectionReconfiguration

–

–

21

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

22

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 RRCConnectionReconfiguration?

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

23

The SS configures:

SS-NW

Cell 1 and Cell 2 parameters according to the row "T2" in table 19.1.3.3.2-0 in order to simulate radio link failure.

–

–

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1.

–

–

–

–

24

UE sends RRCConnectionReestablishmentRequest message.

–>

RRCConnectionReestablishmentRequest

25

Wait for time=(T301)/2

–

–

–

–

26

Check: Does the UE transmit during the re-establishment procedure one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources indicated in the broadcasted on Cell 2 SystemInformationBlockType18 commTxPoolExceptional?

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

27

The SS-NW transmits RRCConnectionReestablishment message.

<–

RRCConnectionReestablishment

–

–

28

The UE transmits RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

–

–

29

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 1 sec?

–>

SidelinkUEInformation

4

P

30

SS-NW transmits an RRCConnectionReconfiguration message assigning sidelink communication transmission scheduled resources (commTxResources set scheduled).

<–

RRCConnectionReconfiguration

–

–

31

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

32

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 RRCConnectionReconfiguration?

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

33

The SS configures:

SW-NW

Cell 1 and Cell 4 parameters according to the row "T3" in table 19.1.3.3.2-0 in order to simulate needs for handover.

Cell 4 broadcasts SystemInformationBlockType18 in which in addition to all other settings the syncTxThreshIC is included with value 7 (this is needed for TP7).

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).

–

–

–

–

34

SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover to Cell 4).

<–

RRCConnectionReconfiguration

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4.

–

–

–

–

35

The UE submits RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

–

EXCEPTION: In parallel to the procedure described in steps 36 – 42 the procedure described in Table 19.1.3.3.2-2 takes place.

–

–

–

–

36

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 1 sec?

–>

SidelinkUEInformation

5

P

37

SS-NW transmits an RRCConnectionReconfiguration message assigning sidelink communication transmission scheduled resources (commTxResources set to setup and resources provided in commTxPoolNormalDedicated), and, networkControlledSyncTx is configured and set to on.

<–

RRCConnectionReconfiguration

–

–

38

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

39

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 RRCConnectionReconfiguration.

NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.

–>

STCH PDCP SDU packet

5

P

–

EXCEPTION: Steps 40 – 41 are repeated 3 times.

–

–

–

–

40

Check: Does the UE transmit SLSS 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) in the next transmission period?

–>

SLSS

6

P

41

Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 40?

–>

MasterInformationBlock-SL

6

P

42

SS-NW transmits an RRCConnectionReconfiguration networkControlledSyncTx is configured and set to off.

<–

RRCConnectionReconfiguration

–

–

43

The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration.

–>

RRCConnectionReconfigurationComplete

–

–

44

Check: Does the UE transmit during the next 3 transmission periods a SLSS?

–>

SLSS

7

F

45

Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS (step 44)?

–>

MasterInformationBlock-SL

7

F

46

The SS configures:

SW-NW

Cell 1 and Cell 4 parameters according to the row "T4" in table 19.1.3.3.2-0.

NOTE: 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 included in SystemInformationBlockType18.

–

–

–

–

–

EXCEPTION: Steps 47 – 48 are repeated 3 times.

–

–

–

–

47

Check: Does the UE transmit SLSS 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) in the next transmission period?

–>

SLSS

7

P

48

Check: Does the UE transmit MasterInformationBlock-SL message in the same subframe as the SLSS in step 47?

–>

MasterInformationBlock-SL

7

P

49-55

Void.

–

–

–

–

56

The SS configures:

SW-NW

Cell 4 and Cell 11 parameters according to the row "T5" in table 19.1.3.3.2-0 in order to simulate needs for handover to Cell 11.

–

–

–

–

57

SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover to Cell 11).

<–

RRCConnectionReconfiguration

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11.

–

–

–

–

58

The UE submits RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

–

EXCEPTION: In parallel to the procedure described in steps 59 – 60 the procedure described in Table 19.1.3.3.2-2 takes place.

–

–

–

–

59

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication and/or indicating the sidelink communication reception frequency of interest in the next 1 sec?

–>

SidelinkUEInformation

9

F

60

Check: Does the UE transmit during the next 3 transmission periods sidelink communication data over the PC5 interface in accordance with the resources indicated on Cell 11?

–>

–

9

F

61

The SS configures:

SW-NW

Cell 1 and Cell 11 parameters according to the row "T6" in table 19.1.3.3.2-0 in order to simulate needs for handover.

Cell 1 does nor transmit SystemInformationBlockType18.

–

–

–

–

62

SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover to Cell 1).

<–

RRCConnectionReconfiguration

–

–

–

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1.

–

–

–

–

63

The UE submits RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

64

Void

–

–

–

–

–

EXCEPTION: In parallel to the procedure described in step 65 the procedure described in Table 19.1.3.3.2-2 takes place.

–

–

–

–

65

Check: Does the UE transmit a SidelinkUEInformation message in the next 1 sec?

–>

SidelinkUEInformation

10

F

66

Force the UE upper layer application to request transmission of sidelink communication.

–

–

–

–

67

Check: Does the UE transmit a SidelinkUEInformation in the next 5 sec?

–>

SidelinkUEInformation

10

F

–

EXCEPTION: Step 68 is repeated 3 times.

–

–

–

–

68

Check: Does the UE transmit in the next 3 transmission periods sidelink communication data over the PC5 interface in accordance with the pre-configured in the UE for out of coverage resources?

–>

–

10

F

70

The SS-NW releases the connection.

<–

RRCConnectionRelease

–

–

Table 19.1.3.3.2-2: Parallel behaviour – TAU

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

–

–

2

SS-NW responds with TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

–

–

3

The UE transmits a TRACKING AREA UPDATE COMPLETE.

–>

TRACKING AREA UPDATE COMPLETE

–

–

Table 19.1.3.3.2-3: Void

Table 19.1.3.3.2-4: Void

19.1.3.3.3 Specific message contents

Table 19.1.3.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 {

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: 3 commRxPools are provided for reception in RRC_IDLE and RRC_CONNECTED; 1 pool is provided for transmission in RRC_IDLE which matches one of the Rx pools, the other 2 Rx pools will be allocated for transmission in RRC_CONNECTED; no resources for commTxPoolExceptional.

Table 19.1.3.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 {

commTxPoolNormalCommon-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-CommResourcePool-r12 {

SL-CommResourcePool-r12[1]

Not Present

}

commSyncConfig-r12

Not Present

}

}

Note 1: 3 commRxPools are provided for reception in RRC_IDLE and RRC_CONNECTED; 1 pool is provided for transmission in RRC_IDLE (SL-CommResourcePool-r12[2]) which matches one of the Rx pools; resources for commTxPoolExceptional are provided and one of the reception resources (SL-CommResourcePool-r12[3]) matches it (to be used for link failure case); the other resources for reception (SL-CommResourcePool-r12[1]) will be allocated for transmission in RRC_CONNECTED.

Table 19.1.3.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[1]

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: 2 commRxPools are provided for reception in RRC_IDLE and RRC_CONNECTED; 1 pool is provided for transmission in RRC_IDLE (SL-CommResourcePool-r12[2]) which matches one of the Rx pools; no resources for commTxPoolExceptional; the resources for reception (SL-CommResourcePool-r12[1]) will be allocated for transmission in RRC_CONNECTED.

Note 1: Entry 1 in SL-SyncConfig sets syncTxThreshIC-r12 to 7 (see 36.508 [18] Table 4.4.3.3-17), i.e. -85dBm is the threshold for starting transmission of SLSS.

Table 19.1.3.3.3-3: 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.3.3.3-4: ATTACH ACCEPT (preamble)

Derivation path: 36.508 [18], table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN4

Cell 1

Table 19.1.3.3.3-5: TRACKING AREA UPDATE REQUEST (step 1, Table 19.1.3.3.2-2 when it is transmitted in parallel with step 36, Table 19.1.3.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.3.3.3-5A: TRACKING AREA UPDATE REQUEST (step 1, Table 19.1.3.3.2-2 when it is transmitted in parallel with steps 59 and 65, Table 19.1.3.3.2-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.3.3.3-6: SidelinkUEInformation (steps 6, 15, 19, 29, 36, Table 19.1.3.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.3.3.3-7: SidelinkUEInformation (step 14C, Table 19.1.3.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 {

carrierFreq-r12

omit

No interest in prose communication transmission

destinationInfoList-r12

Not present

}

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.3.3.3-8: RRCConnectionReconfiguration (step 7, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-8 A, condition [COMM AND SETUP AND UE-SELECTED]

Table 19.1.3.3.3-9: RRCConnectionReconfiguration (step 10, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-8 A, condition [COMM AND RELEASE]

Table 19.1.3.3.3-10: RRCConnectionReconfiguration (step 20, Table 19.1.3.3.2-1)

Derivation Path: 36.508 table 4.6.1-8 A, condition [COMM AND SETUP AND SCHEDULED

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sl-CommConfig-r12 SEQUENCE {

COMM

commTxResources-r12 CHOICE {

setup CHOICE {

SETUP

scheduled-r12 SEQUENCE {

SCHEDULED

sc-CommTxConfig-r12 SEQUENCE {

sc-TF-ResourceConfig-r12 SEQUENCE {

subframeBitmap-r12

11000000

00000000

00000000

00000000

00000000

bs40-r12

FDD

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 19.1.3.3.3-11: RRCConnectionReconfiguration (steps 13, 30, 42, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-8 A, condition [COMM AND SETUP AND SCHEDULED]

Table 19.1.3.3.3-12: RRCConnectionReconfiguration (steps 17, 34, 57, 62, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-8, condition HO

Table 19.1.3.3.3-13: RRCConnectionReconfiguration (step 37, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-8 A, condition [COMM AND SETUP AND SCHEDULED]

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sl-SyncTxControl-r12 SEQUENCE {

networkControlledSyncTx-r12

on

}

}

}

}

}

}

}

}

}

}

Table 19.1.3.3.3-14: Void

Table 19.1.3.3.3-15: RRCConnectionReestablishmentRequest (step 24, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentRequest-r8 SEQUENCE {

ue-Identity SEQUENCE {

c-RNTI

the value of the C-RNTI of the UE

physCellId

PhysicalCellIdentity of Cell 2

shortMAC-I

The same value as the 16 least significant bits of the XMAC-I value calculated by SS

}

reestablishmentCause

otherFailure

}

}

}

Table 19.1.3.3.3-16: MasterInformationBlock-SL (steps 40, 44, 47, Table 19.1.3.3.2-1)

Derivation Path: 36.508 [18], table 4.6.1-4A0