19.2.3 ProSe Direct Discovery Announcing/Pre-configured authorisation / Announcing and SLSS transmission in RRC_CONNECTED / RRC connection reconfiguration with/without the 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.2.3.1 Test Purpose (TP)
(1)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE is in RRC_CONNECTED, and, UE is configured with discTxResources set to scheduled }
then { UE is able to transmit the sidelink discovery announcement using the assigned/configured resources in Cell1/f1/PLMN1 }
}
(2)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE is in RRC_CONNECTED, and, UE is configured with discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased }
then { UE is able to transmit the sidelink discovery announcement using the assigned/configured resources in Cell1/f1/PLMN1 selecting for the transmission an entry of poolToAddModList for which the RSRP measurement of the PCell, after applying the layer 3 filter defined by quantityConfig is in-between threshLow and threshHigh }
}
(3)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE receives RRCConnectionReconfiguration message not including the mobilityControlInfo which includes the sl-DiscConfig and discTxResources set to release }
then { UE release the resources allocated for sidelink discovery announcement previously assigned/configured in Cell1/f1/PLMN1 by discTxResources from the next discovery period, as defined by discPeriod, and, UE re-starts announcing when resources become available }
}
(3A)
with { UE being authorised for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE receives a request from upper layers to stop sidelink discovery announcement }
then { the UE transmits a SidelinkUEInformation message indicating it does no longer require sidelink discovery announcement resources, and, stops sidelink discovery announcement on Cell1/f1/PLMN1 }
}
(4)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE receives RRCConnectionReconfiguration message including mobilityControlInfo and sl-DiscConfig less than 1 sec after the UE transmitted a SidelinkUEInformation message including discRxInterest on Cell1/f1/PLMN1, and, MAC successfully completes the random access procedure to the targeted PCell Cell2/f1/PLMN1 which is broadcasting SystemInformationBlockType19 }
then { UE does not initiate a new Announce request procedure, and, transmits a SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, is able to transmit sidelink discovery announcements using the assigned/configured resources in Cell2/f1/PLMN1 }
}
(5)
with { UE being authorised for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell2/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE detects radio link failure >1 sec after the UE transmitted a SidelinkUEInformation message including discRxInterest on Cell2/f1/PLMN1, and, UE completes RRC connection re-establishment on Cell1/f1/PLMN1 }
then { UE does not initiate a new Announce request procedure, and, does not transmit a SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, continue announcing on Cell1/f1/PLMN1 }
}
(6)
with { UE being authorised for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE receives RRCConnectionReconfiguration message including mobilityControlInfo (handover), and, MAC successfully completes the random access procedure to the targeted PCell Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 }
then { UE initiates and successfully completes an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements }
}
(7)
with { UE capable of SLSS transmission, and, being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE is in RRC_CONNECTED, and, networkControlledSyncTx is configured and set to on }
then { UE transmits SLSS }
}
(8)
with { UE capable of SLSS transmission, and, being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
ensure that {
when { UE is in RRC_CONNECTED, and, networkControlledSyncTx is not configured; and syncTxThreshIC is included in SystemInformationBlockType19, and, the RSRP measurement of the serving cell is below the value of syncTxThreshIC }
then { UE transmits SLSS }
}
(9)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
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 SystemInformationBlockType19 }
then { UE does not initiates an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements and, does not announce over the PC5 in the assigned resources in Cell11/f1/PLMN3 }
}
(10)
with { UE being authorized for performing ProSe Direct Discovery Announcing in two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell11/f1/PLMN3 which is broadcasting SystemInformationBlockType19 indicating the provision of resources for sidelink discovery announcement on the serving PLMN, and, UE has previously successfully completed an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements, and, the timer T4000 associated with the ProSe Application Code allocated during the procedure has not expired }
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 SystemInformationBlockType19 }
then { UE does not initiates an Announce request procedure including the transmission of SidelinkUEInformation message to request assignment of transmission resources for sidelink discovery announcements and, does not announce over the PC5 in the assigned resources in Cell1/f1/PLMN1 }
}
19.2.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.303, clause 5.3.1.1, TS 24.334, clauses 5.1.1, 5.1.2, 6.1.1, 6.2.2.2, 6.2.2.4, TS 36.331, clauses 5.2.2.4, 5.3.3.1a, 5.3.5.3, 5.3.5.4, 5.3.7.5, 5.3.10.15, 5.10.2.1, 5.10.2.2, 5.10.2.3, 5.10.6, 5.10.7.1, 5.10.7.2, 5.10.7.3. Unless otherwise stated these are Rel-12 requirements.
[TS 23.303, clause 5.3.1.1]
The UE can act as "announcing UE" only in the band designated by the serving PLMN but may act as a "monitoring" UE also in the resources of the serving PLMN and Local PLMNs.
ProSe-enabled UEs which have obtained authorization to participate in ProSe Direct Discovery procedures shall not continue in participating in ProSe Direct Discovery procedures as soon as they detect loss of E-UTRA coverage in the serving PLMN.
[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
2) transferred between the UE and the ProSe Function over the PC3 interface with the ProSe Direct Services Provisioning Management Object or the ProSe Public Safety Direct Services Provisioning Management Object as specified in 3GPPÂ TSÂ 24.333Â [9].
…
The service authorisation provided by the ProSe Function of the HPLMN for ProSe direct discovery contains a list of PLMNs in which the UE is authorised to use ProSe direct discovery.
…
The UE discovers the IP address of the ProSe Functions of the HPLMN as specified in subclause 5.1.2.
[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 6.1.1]
The UE and ProSe Function shall use HTTPÂ 1.1 as specified in IETFÂ RFCÂ 7230Â [18] and IETFÂ RFCÂ 7231Â [19] as the transport protocol for ProSe messages over the PC3 interface. The ProSe messages described here shall be included in the body of either an HTTP request message or an HTTP response message. The following rules apply:
– The UE initiates ProSe transactions with an HTTP request message containing the PC3 request(s);
– The ProSe Function responds to the requests with an HTTP response message containing the PC3 response(s) for the PC3 request(s); and
– HTTP POST methods are used for PC3 direct discovery procedures.
Optionally, the operator can configure the UE with configuration parameters for establishment of the PDN connection for reaching the HPLMN ProSe Function. If the UE is configured with the configuration parameter for establishment of the PDN connection for reaching the HPLMN ProSe Function (see 3GPPÂ TSÂ 24.333Â [9]):
a) if a PDN connection for reaching the HPLMN ProSe Function is not established yet, the UE shall establish the PDN connection for reaching the HPLMN ProSe Function according to the UE configuration and shall send the HTTP request message via the PDN connection for reaching the HPLMN ProSe Function; and
b) if a PDN connection for reaching the HPLMN ProSe Function is already established (e.g. either due to other ProSe feature or due to other application), the UE shall send the HTTP request message via the PDN connection for reaching the HPLMN ProSe Function;
[TS 24.334, clause 6.2.2.2]
Before initiating the announce request procedure, the UE is configured with the data structure of the ProSe Application IDs appropriate for its HPLMN. This step is performed using mechanisms out of scope of 3GPP.
If the UE is authorised to perform ProSe direct discovery announcing in the registered PLMN, it shall initiate an announce request procedure:
a) when the UE is triggered by an upper layer application to announce a ProSe Application ID and the UE has no valid corresponding ProSe Application Code for that upper layer application;
b) when the validity timer T4000 assigned by the ProSe Function to a ProSe Application Code has expired and the request from upper layers to announce the ProSe Application ID corresponding to that ProSe Application Code is still in place; or
c) when the UE selects a new PLMN while announcing a ProSe Application Code and the UE is authorised for ProSe direct discovery announcing in the new PLMN.
When the UE selects a new PLMN while announcing a ProSe Application Code and the UE is not yet authorised for ProSe direct discovery announcing in the new PLMN, the UE shall initiate an announce request procedure only after the UE is authorised for ProSe direct discovery announcing in the new PLMN.
NOTEÂ 1: To ensure service continuity if the UE needs to keep announcing a ProSe Application Code corresponding to the same ProSe Application ID, the UE can initiate the announce request procedure before the TTL timer T4000 assigned by the ProSe Function for a Prose Application Code expires.
The UE initiates the announce request procedure by sending a DISCOVERY_REQUEST message with a new transaction ID, the ProSe Application ID set to the ProSe Application ID received from upper layers, the command set to "announce", the UE identity set to the UE’s IMSI, and the Application Identity set to the Application Identity of the upper layer application that requested the announcing.
NOTEÂ 2: A UE can include one or multiple transactions in one DISCOVERY_REQUEST message for different ProSe Application IDs, and receive corresponding <response-announce> element or <response-reject> element in a DISCOVERY_RESPONSE message for each respective transaction. In the following description of the announce request procedure, only one transaction is included.
Figure 6.2.2.2.1 illustrates the interaction of the UE and the ProSe Function in the announce request procedure.
Figure 6.2.2.2.1: Announce request procedure
[TS 24.334, clause 6.2.2.4]
Upon receipt of the DISCOVERY_RESPONSE message, if the transaction ID contained in the <response-announce> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "announce", the UE shall, for each ProSe Application Code received in the DISCOVERY_RESPONSE message, stop the validity timer T4000 if running and start the validity timer T4000 with the received value. Otherwise the UE shall discard the DISCOVERY_RESPONSE message and shall not perform the procedures below.
The UE may perform direct discovery announcing as described below.
The UE requests the parameters from the lower layers for Prose direct discovery announcing (see 3GPPÂ TSÂ 36.331Â [12]). The UE shall perform direct discovery announcing only if the lower layers indicate that ProSe direct discovery is supported by the network. If the UE in EMM-IDLE mode has to request resources for ProSe direct discovery announcing 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]. The UE shall obtain the UTC time for the next discovery transmission opportunity for ProSe direct discovery from the lower layers.
If a valid UTC time is obtained, the UE shall generate the UTC-based counter corresponding to this UTC time as specified in subclause 12.2.2.18, and then use the UTC-based counter to compute the MIC field for the PC5_DISCOVERY message as described in 3GPPÂ TSÂ 33.303Â [6].
The UE shall use the ProSe Application Code received in the DISCOVERY_RESPONSE message, along with the MIC and the four least significant bits of the UTC-based counter, in order to construct a PC5_DISCOVERY message, according to the format defined in subclause 11.2.5.
The UE then passes the PC5_DISCOVERY message to the lower layers for transmission if:
– the UE is currently authorised to perform direct discovery announcing in the registered PLMN;
– the validity timer T4000 for the allocated ProSe Application Code has not expired; and
– a request from upper layers to announce the ProSe Application ID associated with both the ProSe Application Code and the authorised Application Identity is still in place.
The UE shall ensure that it keeps on passing PC5_DISCOVERY messages to the lower layers for transmission until the validity timer T4000 of the ProSe Application Code expires. How this is achieved is left up to UE implementation.
During the announcing operation, if one of the above conditions is no longer met, the UE may instruct the lower layers to stop announcing. When the UE stops announcing, if the lower layers indicate that the UE is required to send a discovery indication to the eNodeB and the UE is in EMM-CONNECTED mode, the UE shall trigger the corresponding procedure in lower layers as specified in 3GPPÂ TSÂ 36.331Â [12].
[TS 36.331, clause 5.2.2.4]
1> if the UE is capable of sidelink discovery and is configured by upper layers to receive or transmit sidelink discovery announcements on the primary frequency:
2> if schedulingInfoList indicates that SystemInformationBlockType19 is present and the UE does not have stored a valid version of this system information block:
3> acquire SystemInformationBlockType19;
[TS 36.331, clause 5.3.3.1a]
For sidelink discovery an RRC connection is initiated only in the following case:
1> if configured by upper layers to transmit sidelink discovery announcements:
2> if SystemInformationBlockType19 is broadcast by the cell on which the UE camps: and if the valid version of SystemInformationBlockType19 does not include discTxPoolCommon;
NOTE: Upper layers initiate an RRC connection. The interaction with NAS is left to UE implementation.
[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 SystemInformationBlockType19 is broadcast by the target PCell; and the UE transmitted a SidelinkUEInformation message including discRxInterest or discTxResourceReq during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo:
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 SystemInformationBlockType19 is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message including discRxInterest or discTxResourceReq during the last 1 second preceding detection of radio link failure:
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-DiscConfig:
2> if discTxResources is included and set to setup:
3> from the next discovery period, as defined by discPeriod, use the resources indicated by discTxResources for sidelink discovery announcement, as specified in 5.10.6;
2> else if discTxResources is included and set to release:
3> from the next discovery period, as defined by discPeriod, release the resources allocated for sidelink discovery announcement previously configured by discTxResources;
[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 SystemInformationBlockType19 is broadcast by the PCell:
2> ensure having a valid version of SystemInformationBlockType19 for the PCell;
…
2> if the UE is configured by upper layers to transmit sidelink discovery announcements:
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 SystemInformationBlockType19; or
3> if the last transmission of the SidelinkUEInformation message did not include discTxResourceReq; or if the sidelink discovery announcement resources required by the UE have changed (i.e. resulting in a change of discTxResourceReq) since the last transmission of the SidelinkUEInformation message:
4> initiate transmission of the SidelinkUEInformation message to indicate the sidelink discovery announcement resources required by the UE in accordance with 5.10.2.3;
2> else:
3> if the last transmission of the SidelinkUEInformation message included discTxResourceReq:
4> initiate transmission of the SidelinkUEInformation message to indicate it does no longer require sidelink discovery announcement 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 SystemInformationBlockType19 is broadcast by the PCell:
…
2> if the UE is configured by upper layers to transmit sidelink discovery announcements:
3> include discTxResourceReq and set it to indicate the number of discovery messages for sidelink discovery announcement(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.6]
A UE capable of sidelink discovery that is configured by upper layers to transmit sidelink discovery announcements shall:
NOTE 1: In case the configured resources are insufficient it is up to UE implementation to decide which sidelink discovery announcements to transmit.
1> if the UE’s serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is suitable as defined in TS 36.304 [4]:
2> if the UE is in RRC_CONNECTED (i.e. PCell is used for sidelink discovery announcement):
3> if the UE is configured with discTxResources set to scheduled:
4> configure lower layers to transmit the sidelink discovery announcement using the assigned resources indicated by scheduled in discTxResources;
3> else if the UE is configured with discTxPoolDedicated (i.e. discTxResources set to ue-Selected):
4> if poolSelection within poolToAddModList is set to rsrpBased:
5> select an entry of poolToAddModList for which the RSRP measurement of the PCell, after applying the layer 3 filter defined by quantityConfig as specified in 5.5.3.2 , is in-between threshLow and threshHigh;
4> else:
5> randomly select, using a uniform distribution, an entry of poolToAddModList;
4> configure lower layers to transmit the sidelink discovery announcement using the selected pool of resources:
[TS 36.331, clause 5.10.7.1]
Figure 5.10.7.1-3: Synchronisation information transmission for sidelink discovery
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 SLSS transmission shall, when transmitting sidelink discovery announcements in accordance with 5.10.6 and when the following conditions are met:
1> if the UE’s serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is suitable as defined in TS 36.304 [4]:
2> if in RRC_CONNECTED; and if networkControlledSyncTx is configured and set to on; or
2> if networkControlledSyncTx is not configured; and syncTxThreshIC is included in SystemInformationBlockType19; and the RSRP measurement of the serving cell (RRC_IDLE) or PCell (RRC_CONNECTED) is below the value of syncTxThreshIC:
3> transmit SLSS in accordance with 5.10.7.3 and TS 36.211 [21], unless the UE uses the selected subframe for regular uplink transmission;
[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 discovery announcement:
2> select the SLSSID included in the entry of discSyncConfig included in the received SystemInformationBlockType19, that includes txParameters;
2> use syncOffsetIndicator corresponding to the selected SLSSID;
2> for each pool used for the transmission of discovery announcements (each corresponding to the selected SLSSID):
3> if a subframe indicated by syncOffsetIndicator corresponds to the first subframe of the discovery transmission pool;
4> select the concerned subframe;
3> else
4> select the subframe indicated by syncOffsetIndicator that precedes and which, in time domain, is nearest to the first subframe of the discovery transmission pool;
19.2.3.3 Test description
19.2.3.3.1 Pre-test conditions
System Simulator:
SS-NW
– 4 cells with parameters defined in Table 19.2.3.3.1-1.
NOTE: The test only requires at maximum 2 cells to be active at any one instant.
Table 19.2.3.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
1 |
f1 |
HPLMN (PLMN1) |
|
2 |
f1 |
HPLMN (PLMN1) |
|
4 |
f1 |
PLMN2 |
|
11 |
f1 |
PLMN3 |
|
Note 1: PLMN1: PLMN1 in USIM EFPROSE_ANN Note 2: 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 24 as defined in TS 36.508 [18] clause 4.4.3.1 is used in all active cells.
SS-UE
– SS-UE 1.
– As defined in TS 36.508 [18], configured and operating for/as ProSe Direct Discovery Monitoring on the resources which the UE is expected to use for transmission (as specified in the relevant procedure steps in Table 19.2.3.3.2-1).
UE:
– ProSe related configuration
– The UE is equipped with a USIM containing values shown in Table 19.2.3.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 Discovery Announcing).
Table 19.2.3.3.1-2: USIM Configuration
|
USIM field |
Value |
|
EFUST |
Service n°101 (ProSe) supported. |
|
EFPST |
Service n°1 (ProSe direct discovery parameters) supported |
|
Service n°5 (ProSe Direct Discovery announcing radio parameters) 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 |
Depending on implementation, a Rel-12 UE may not support USIM settings for ProSe Direct Discovery Announcing (pc_disc_public_safety=FALSE, i.e. ProSe Discovery for Public Safety not supported) . Such UEs are expected to provide means for pre-configuring the PLMNs which are authorised for ProSe Direct Discovery Announcing (e.g. via MMI). The values specified for EFPROSE_ANN in TS 36.508 [18], section 4.9.3.1 shall be preconfigured.
– For each PLMN a timer T4005 is assigned long enough not to expire before the TC is completed, e.g. 5min (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).
– The UE is configured with the data structure of the ProSe Application ID (px_ProSeAnnApplicationIdentity1) it wants to announce (This step is performed using UE implementation dependent mechanisms, e.g. MMI command, or, may be pre-loaded in the UE).
– The UE has no valid ProSe Application Code corresponding to the configured ProSe Application ID (px_ProSeAnnApplicationIdentity1).
Preamble:
– The UE is in state Generic Radio Bearer Established (State 3) according to TS 36.508 [18] on Cell 1.
19.2.3.3.2 Test procedure sequence
Table 19.2.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.2.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 |
-91 |
"Off" |
"Off" |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-77 |
"Off" |
"Off" |
|
T2 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
"Off" |
"Off" |
"Off" |
|
T3 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
"Off" |
-77 |
"Off" |
|
T4 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
-87 |
"Off" |
|
T5 |
Cell-specific RS EPRE |
dBm/15kHz |
"Off" |
"Off" |
"Off" |
-79 |
|
T6 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
"Off" |
"Off" |
-85 |
Table 19.2.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity1 to initiate continuous ProSe direct discovery announcing. NOTE: Although the UE is expected to transmit continuously, only the PC5_DISCOVERY messages which need to be checked are shown explicitly in the step sequence. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
2-2C |
Check: Do steps 8 – 11 from t he generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22 take place (UE performs Announce request procedure and requests assignment of dedicated resources for direct discovery announcing) ? |
– |
– |
1 |
P |
|
– |
EXCEPTION: Steps 3a1 – 3a3 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that takes place if the UE supports transmission of discovery announcements based on network scheduled resource allocation. |
– |
– |
– |
– |
|
3a1 |
IF pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission scheduled resources to the UE (i.e. discTxResources set to scheduled). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
3a2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 3a3 is repeated 3 times . |
– |
– |
– |
– |
|
3a3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? |
–> |
PC5_DISCOVERY |
1 |
P |
|
– |
EXCEPTION: Steps 4a1 – 4a3 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that takes place if the UE supports transmission of discovery announcements based on UE autonomous resource selection. |
– |
– |
– |
– |
|
4a1 |
IF pc_discUESelectedResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission resources for UE autonomous resource selection: discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased. The DiscTxPoolList contains 2 Pools each providing different sets of threshLow and threshHigh. One of these sets is defined so that RSRP measurement of the serving cell will result in the RSRP being in-between the threshLow and threshHigh, whereas for the other it will be out. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
4a2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 4a3 is repeated 3 times . |
– |
– |
– |
– |
|
4a3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? NOTE: The UE uses for the transmission the –DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is in-between the set for that pool threshLow and threshHigh (ue-Selected-r12/SL-DiscTxPoolToAddMod-r12[1]). |
–> |
PC5_DISCOVERY |
2 |
P |
|
5 |
SS-NW transmits an RRCConnectionReconfiguration message requesting the UE to release the resources allocated for sidelink discovery announcement previously configured by discTxResources (i.e. discTxResources is included and set to release). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
6 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Steps 7a1 – 7b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. |
– |
– |
– |
– |
|
7a1 |
IF (pc_discScheduledResourceAlloc AND NOT pc_discUESelectedResourceAlloc) THEN Check: Does the UE transmit during the next 10 discovery periods a PC5_DISCOVERY message utilising the resources used for transmission in step 3a3? |
–> |
PC5_DISCOVERY |
3 |
F |
|
7b1 |
IF pc_discUESelectedResourceAlloc THEN Check: Does the UE transmit during the next 10 discovery periods a PC5_DISCOVERY message utilising the resources used for transmission in step 4a3? |
–> |
PC5_DISCOVERY |
3 |
F |
|
– |
EXCEPTION: Steps 7Aa1 – 7Ab3 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. NOTE: In comparison to the similar sequences earlier in the step sequence testing only one of the 2 options here is enough to satisfy the TP. |
– |
– |
– |
– |
|
7Aa1 |
IF pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission scheduled resources to the UE (i.e. discTxResources set to scheduled). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
7Aa2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 7Aa3 is repeated 3 times. |
– |
– |
– |
– |
|
7Aa3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? |
–> |
PC5_DISCOVERY |
3 |
P |
|
7Ab1 |
IF (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission resources for UE autonomous resource selection: discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
7Ab2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 7Ab3 is repeated 3x times. |
– |
– |
– |
– |
|
7Ab3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? NOTE: The UE uses for the transmission the -DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is in-between the set for that pool threshLow and threshHigh (ue-Selected-r12/SL-DiscTxPoolToAddMod-r12[1]). |
–> |
PC5_DISCOVERY |
3 |
P |
|
8 |
Force the UE upper layer application to request stop of sidelink direct discovery announcing.. |
– |
– |
– |
– |
|
8A |
Check: Does the UE transmit a SidelinkUEInformation message indicating it does no longer require resources for sidelink direct discovery announcing transmission in the next 1 sec? |
–> |
SidelinkUEInformation |
3A |
P |
|
9 |
Force the UE upper layer application to request restart of sidelink direct discovery announcing. |
– |
– |
– |
– |
|
10 |
The UE transmit a SidelinkUEInformation message requesting resources for Announcing. |
–> |
SidelinkUEInformation |
– |
– |
|
11 |
The SS configures: SW-NW Cell 1 and Cell 2 parameters according to the row "T1" in table 19.2.3.3.2-0 in order to simulate needs for handover. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 12a1 – 12b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. |
– |
– |
– |
– |
|
12a1 |
IF pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover) and sl-DiscConfig assigning announce transmission scheduled resources to the UE (i.e. discTxResources set to scheduled). The message is sent less than 1 sec after the SidelinkUEInformation message sent in Step 10. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
12b1 |
IF (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN SS-NW transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover) and sl-DiscConfig announce transmission resources for UE autonomous resource selection: discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased. The message is sent less than 1 sec after the SidelinkUEInformation message sent in Sep 10. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2. |
– |
– |
– |
– |
|
13 |
The UE submits RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 14 the event described in Table 19.2.3.3.2-4 takes place. |
– |
– |
– |
– |
|
14 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing? |
–> |
SidelinkUEInformation |
4 |
P |
|
– |
EXCEPTION: Steps 15a1 – 15b3 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. NOTE: In comparison to the similar sequences earlier in the step sequence testing only one of the 2 options here is enough to satisfy the TP. |
– |
– |
– |
– |
|
15a1 |
IF pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission scheduled resources to the UE (i.e. discTxResources set to scheduled). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
15a2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 15a3 is repeated 3 times . |
– |
– |
– |
– |
|
15a3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? |
–> |
PC5_DISCOVERY |
4 |
P |
|
15b1 |
IF (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN SS-NW transmits an RRCConnectionReconfiguration message assigning announce transmission resources for UE autonomous resource selection: discTxResources set to ue-Selected and poolSelection within poolToAddModList is set to rsrpBased. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
15b2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 15b3 is repeated 3 times . |
– |
– |
– |
– |
|
15b3 |
Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? NOTE: The UE uses for the transmission the -DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is in-between the set for that pool threshLow and threshHigh (ue-Selected-r12/SL-DiscTxPoolToAddMod-r12[2]). |
–> |
PC5_DISCOVERY |
4 |
P |
|
16 |
The SS configures SS-NW Cell 1 and Cell 2 parameters according to the row "T2" in table 19.2.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. |
– |
– |
– |
– |
|
17 |
The UE sends RRCConnectionReestablishmentRequest message. |
–> |
RRCConnectionReestablishmentRequest |
||
|
18 |
The SS-NW transmits RRCConnectionReestablishment message. |
<– |
RRCConnectionReestablishment |
||
|
19 |
The UE transmits RRCConnectionReestablishmentComplete message. |
–> |
RRCConnectionReestablishmentComplete |
||
|
– |
EXCEPTION: In parallel to the event described in step 20 the event described in Table 19.2.3.3.2-4 takes place. |
– |
– |
– |
– |
|
20 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing in the next 1 sec? |
–> |
SidelinkUEInformation |
5 |
F |
|
– |
EXCEPTION: Steps 21a1 – 21b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place if the UE supports transmission of discovery announcements based on network scheduled resource allocation. NOTE: Which of the resources the UE will use depends on which was the last resources assigned in steps 15a1 or 15b1 above. |
– |
– |
– |
– |
|
– |
EXCEPTION: When the condition matches, step 21a1 is repeated 3 times . |
– |
– |
– |
– |
|
21a1 |
IF pc_discUESelectedResourceAlloc THEN Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? NOTE: The UE uses for the transmission the -DiscResourcePool entry in discTxPoolCommon for which RSRP measurement of the serving cell is in-between the set for that pool threshLow and threshHigh (ue-Selected-r12/SL-DiscTxPoolToAddMod-r12[1]). |
–> |
PC5_DISCOVERY |
5 |
P |
|
– |
EXCEPTION: When the condition matches, step 21b1 is repeated 3 times . |
– |
– |
– |
– |
|
21b1 |
IF (pc_discScheduledResourceAlloc AND NOT pc_discUESelectedResourceAlloc) Check: Does the UE transmit in the next transmission period a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 2) and utilising the resources configured in the RRCConnectionReconfiguration message? |
–> |
PC5_DISCOVERY |
5 |
P |
|
22 |
The SS configures: SW-NW Cell 1 and Cell 4 parameters according to the row "T3" in table 19.2.3.3.2-0 in order to simulate needs for handover. Cell 4 broadcasts SystemInformationBlockType19 providing different resources for Announcing than those provided on Cell 1. 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). |
– |
– |
– |
– |
|
23 |
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. |
– |
– |
– |
– |
|
24 |
The UE submits RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: In parallel to the procedure described in steps 25 – 27 the procedure described in Table 19.2.3.3.2-2 takes place. |
– |
– |
– |
– |
|
25 |
Check: Does the UE transmit a DISCOVERY_REQUEST message over the PC3 (UE to ProSe Function) interface? |
–> |
DISCOVERY_REQUEST |
6 |
P |
|
26 |
The SS-NW transmits a DISCOVERY_RESPONSE message over the PC3 (UE to ProSe Function) interface. |
<– |
DISCOVERY_RESPONSE |
– |
– |
|
27 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing? |
–> |
SidelinkUEInformation |
6 |
P |
|
– |
EXCEPTION: Steps 28a1 – 28a9 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that takes place if the UE is capable of SLSS transmission. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 28a1a1 – 28a1b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. |
– |
– |
– |
– |
|
28a1 a1 |
IF pc_discSLSS AND pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration networkControlledSyncTx is configured and set to on, discTxResources set to scheduled. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
28a1b1 |
IF pc_discSLSS AND (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN SS-NW transmits an RRCConnectionReconfiguration networkControlledSyncTx is configured and set to on, discTxResources set to ue-selected. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
28a2 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: Step 28a3 is repeated 3 times. |
– |
– |
– |
– |
|
28a3 |
Check: Does the UE transmit in the next transmission period SLSS in accordance with the information provided in the SystemInformationBlockType19 (SLSSID, a subframe indicated by syncOffsetIndicator does not corresponds to the first subframe of the discovery transmission pool)? |
–> |
SLSS |
7 |
P |
|
– |
EXCEPTION: Steps 28a4a1 – 28a4b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place depending on the type of resource selection UE supports for transmission of discovery announcements. |
– |
– |
– |
– |
|
28a4 a1 |
IF pc_discScheduledResourceAlloc THEN SS-NW transmits an RRCConnectionReconfiguration networkControlledSyncTx is configured and set to off, discTxResources set to scheduled. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
28a4b1 |
IF (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN SS-NW transmits an RRCConnectionReconfiguration networkControlledSyncTx is configured and set to off, discTxResources set to ue-selected. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
28a5 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
28a6 |
Check: Does the UE transmit during the next3 transmission periods SLSS? |
–> |
SLSS |
7 |
F |
|
28a7 |
The SS configures: SW-NW Cell 1 and Cell 4 parameters according to the row "T4" in table 19.2.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 (7 (-85dBm)) included in SystemInformationBlockType19. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 28a9 is repeated 3 times. |
– |
– |
– |
– |
|
28a9 |
Check: Does the UE transmit in the next transmission period SLSS in accordance with the information provided in the SystemInformationBlockType19 (SLSSID, a subframe indicated by syncOffsetIndicator does not corresponds to the first subframe of the discovery transmission pool)? |
–> |
SLSS |
8 |
P |
|
29 |
The SS configures: SW-NW Cell 4 and Cell 11 parameters according to the row "T5" in table 19.2.3.3.2-0 in order to simulate needs for handover. |
– |
– |
– |
– |
|
30 |
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. |
– |
– |
– |
– |
|
31 |
The UE submits RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: In parallel to the procedure described in steps 32 – 33 the procedure described in Table 19.2.3.3.2-2 takes place. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 32 the event described in Table 19.2.3.3.2-4 takes place. |
– |
– |
– |
– |
|
32 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing in the next 1 sec? |
–> |
SidelinkUEInformation |
9 |
F |
|
– |
EXCEPTION: Steps 33a1 – 33b1 describe behaviour that depends on UE capabilities; the "lower case letter" identifies a step sequence that take place if the UE supports transmission of discovery announcements based on network scheduled resource allocation. |
– |
– |
– |
– |
|
33 a1 |
IF pc_discScheduledResourceAlloc THEN Check: Does the UE transmit during the next10 transmission periods a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 26) over the resources it last transmitted on cell 4 (provided in step 28a1a1)? |
–> |
PC5_DISCOVERY |
9 |
F |
|
33b1 |
IF (pc_discUESelectedResourceAlloc AND NOT pc_discScheduledResourceAlloc) THEN Check: Does the UE transmit during the next 10 transmission periods a PC5_DISCOVERY message containing the ProSe Application Code (provided in the DISCOVERY_RESPONSE in step 26) over the resources it last transmitted on cell 4 (provided in step 28a1b1) (ue-Selected-r12/SL-DiscTxPoolToAddMod-r12[2])? |
–> |
PC5_DISCOVERY |
9 |
F |
|
34 |
The SS configures: SW-NW Cell 1 and Cell 11 parameters according to the row "T6" in table 19.2.3.3.2-0 in order to simulate needs for handover. Cell 1 does not transmit SystemInformationBlockType19. |
– |
– |
– |
– |
|
35 |
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. |
– |
– |
– |
– |
|
36 |
The UE submits RRCConnectionReconfigurationComplete message on Cell 1. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
EXCEPTION: In parallel to the procedure described in step 37 the procedure described in Table 19.2.3.3.2-2 takes place. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 37 the event described in Table 19.2.3.3.2-4 takes place. |
– |
– |
– |
– |
|
37 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing in the next 1 sec? |
–> |
SidelinkUEInformation |
10 |
F |
|
38-39 |
Void |
– |
– |
– |
– |
|
40 |
Force the UE upper layer application corresponding to ProSe Application ID px_ProSeAnnApplicationIdentity1 to initiate ProSe direct discovery announcing. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 41 the event described in Table 19.2.3.3.2-4 takes place. |
– |
– |
– |
– |
|
41 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for Announcing in the next 1 sec? |
–> |
SidelinkUEInformation |
10 |
F |
|
42 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
Table 19.2.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.2.3.3.2-3: Void
Table 19.2.3.3.2-4: Parallel behaviour – Discovery request
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Check: Does the UE transmit a DISCOVERY_REQUEST message over the PC3 (UE to ProSe Function) interface? |
–> |
DISCOVERY_REQUEST |
4,5,9,10 |
F |
19.2.3.3.3 Specific message contents
Table 19.2.3.3.3-1: SystemInformationBlockType19 for cells 1 and 2 when active
|
Derivation Path: 36.508 [18] Table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType19-r12 ::= SEQUENCE { |
|||
|
discConfig-r12 SEQUENCE { |
|||
|
discRxPool-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[3] SEQUENCE { |
RxPool 3 |
||
|
cp-Len-r12 |
normal |
||
|
discPeriod-r12 |
rf128 |
||
|
numRetx-r12 |
0 |
||
|
numRepetition-r12 |
1 |
||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
prb-Num-r12 |
12 |
BW5 |
|
|
24 |
BW10 |
||
|
prb-Start-r12 |
0 |
||
|
prb-End-r12 |
23 |
BW5 |
|
|
48 |
BW10 |
||
|
offsetIndicator-r12 |
160 |
small-r12 |
FDD |
|
163 |
TDD |
||
|
subframeBitmap-r12 |
00001111 11111111 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00001111 11111111 |
bs16-r12 |
TDD |
|
|
} |
|||
|
txParameters-r12 |
Not present |
||
|
rxParameters-r12 |
Not present |
||
|
} |
|||
|
} |
|||
|
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[2] |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: It is assumed that the pools allocated for announcing need to be provided for monitoring. The Rx Pool 3 is the pool allocated for the Tx resources allocated in the various RRCConnectionReconfiguration messages sent during the TC when the UE is on Cell 1 or Cell 2. |
|||
Table 19.2.3.3.3-2: SystemInformationBlockType19 for cells 4 and 11 when active
|
Derivation Path: 36.508 [18] Table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType19-r12 ::= SEQUENCE { |
|||
|
discConfig-r12 SEQUENCE { |
|||
|
discRxPool-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[3] SEQUENCE { |
RxPool 3 |
||
|
cp-Len-r12 |
normal |
||
|
discPeriod-r12 |
rf128 |
||
|
numRetx-r12 |
0 |
||
|
numRepetition-r12 |
1 |
||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
prb-Num-r12 |
12 |
BW5 |
|
|
24 |
BW10 |
||
|
prb-Start-r12 |
0 |
||
|
prb-End-r12 |
23 |
BW5 |
|
|
48 |
BW10 |
||
|
offsetIndicator-r12 |
160 |
small-r12 |
FDD |
|
163 |
TDD |
||
|
subframeBitmap-r12 |
00000000 11110011 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000000 11110011 |
bs16-r12 |
TDD |
|
|
} |
|||
|
txParameters-r12 |
Not present |
||
|
rxParameters-r12 |
Not present |
||
|
} |
|||
|
} |
|||
|
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[1] |
Not Present |
||
|
SL-DiscResourcePool-r12[2] SEQUENCE { |
|||
|
rxParameters-r12 SEQUENCE { |
|||
|
syncConfigIndex-r12 |
2 |
Entry 2 in discSyncConfig-r12 (Note 1) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note 1: Entry 2 in discSyncConfig-r12 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, which with the Cell 4 settings to -79dBm and -87dBm in Table 19.2.2.3.2-0 should ensure that for "T3" there should be no SLSS transmission and for "T4" there should be SLSS transmission; The Rx Pool 3 is the pool allocated for the Tx resources allocated in the various RRCConnectionReconfiguration messages sent during the TC when the UE is on Cell 4. |
|||
Table 19.2.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) |
‘1’ |
ProSe direct discovery Supported |
|
|
ProSe direct communication (ProSe-dc) (octet 8, bit 1) |
‘0’ or ‘1’ |
The UE may, but need not to, support also ProSe direct communication |
|
Table 19.2.3.3.3-4: TRACKING AREA UPDATE REQUEST (step 1, Table 19.2.3.3.2-2)
|
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) |
‘1’ |
ProSe direct discovery Supported |
|
|
ProSe direct communication (ProSe-dc) (octet 8, bit 1) |
‘0’ or ‘1’ |
The UE may, but need not to, support also ProSe direct communication |
|
Table 19.2.3.3.3-5: DISCOVERY_REQUEST (step 2, Table 19.2.3.3.2-1; step 10a1, TS 36.508 [18] Table 4.5A.22-1, step 27, Table 19.2.3.3.2-1)
|
Derivation path: 36.508 [18] , table 4.7F.1-1. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
discovery-request[1] { |
|||
|
command |
1 |
announce |
|
|
} |
|||
Table 19.2.3.3.3-6: DISCOVERY_RESPONSE (step 2, Table 19.2.3.3.2-1; step 10a2, TS 36.508 [18] Table 4.5A.22-1, step 28, Table 19.2.3.3.2-1)
|
Derivation path: 36.508 [18] , table 4.7F.1-1. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
response-monitor[1] |
Not Present |
||
|
response-announce[1] { |
|||
|
validity-timer-T4000 |
2 min |
Note: Value of 2 min has been arbitrary chosen with the aim from one side not to prolong unnecessarily the TC when the expiration of the timer is checked, and, on another not to trigger not relevant to the TPs ANNOUNCE REQUEST procedure. |
|
|
} |
|||
Table 19.2.3.3.3-7: SidelinkUEInformation (steps 2, 10, 14, 27, 37, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-21A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformation-r12-IEs ::= SEQUENCE { |
|||
|
commRxInterestedFreq-r12 |
Not Present |
Note 1 |
|
|
commTxResourceReq-r12 |
Not Present |
Note 1 |
|
|
discRxInterest-r12 |
Not Present |
Note 1 |
|
|
discTxResourceReq-r12 |
1 |
Indicates the number of separate discovery message(s) the UE wants to transmit every discovery period. Note 2 |
|
|
} |
|||
|
Note 1: It is assumed that it will be possible to trigger in the UE an Application that requests only Announcing. Note 2 This TC assumes that the UE is triggering ProSe Direct Discovery Announcing for only one ProSe Application px_ProSeAnnApplicationIdentity1. |
|||
Table 19.2.3.3.3-7A: SidelinkUEInformation (step 8A, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-21A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformation-r12-IEs ::= SEQUENCE { |
|||
|
commRxInterestedFreq-r12 |
Not Present |
Note 1 |
|
|
commTxResourceReq-r12 |
Not Present |
Note 1 |
|
|
discRxInterest-r12 |
Not Present |
Note 1 |
|
|
discTxResourceReq-r12 |
Not Present |
Note 2 |
|
|
} |
|||
|
Note 1: It is assumed that it will be possible to trigger in the UE an Application that requests only Announcing. Note 2: Not including the TxResourceReq after the UE has submitted a SidelinkUEInformation which included one, is assumed as indication the UE does no longer require sidelink discovery announcement resources. |
|||
Table 19.2.3.3.3-8: PC5_DISCOVERY (steps 3a3, 4a3, 15a3, 15b3, 21a1, 21b1, Table 19.2.3.3.2-1)
|
Derivation path: 36.508 [18] , table 4.7F.1-5. |
Table 19.2.3.3.3-9: RRCConnectionReconfiguration (steps 3a1, 7Aa1, 28a4a1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND SETUP AND SCHEDULED] |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Note: The discTxResources set to setup, scheduled, one transmission pool SL-DiscResourcePool-r12. The transmission pool provides different settings in comparison to the transmission pool set in the broadcasted on the serving cell SystemInformationBlockType19 (see Table 19.2.3.3.3-1 or Table 19.2.3.3.3-2). |
|||
Table 19.2.3.3.3-10: RRCConnectionReconfiguration (step 4a1, 7Ab1, 28a4b1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND SETUP AND UE-SELECTED] |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Note: The discTxResources set to setup, ue-Selected and poolSelection within poolToAddModList is set to rsrpBased with threshLow and threshHigh and the serving cell power levels set to ensure that the RSRP measurement of the PCell, after applying the layer 3 filter defined by quantityConfig (part of MeasConfig) is in-between threshLow and threshHigh of exactly one of the provided pools. The transmission pools provides different settings in comparison to the transmission pool set in the broadcasted on the serving cell SystemInformationBlockType19 (see Table 19.2.3.3.3-1 or Table 19.2.3.3.3-2). |
|||
Table 19.2.3.3.3-11: RRCConnectionReconfiguration (step 5, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND RELEASE] |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Note: The poolToReleaseList-r12 indicates the release of the pool used for transmission until this time, all pools are released to ensure that the UE will ask for resources. |
|||
Table 19.2.3.3.3-12: RRCConnectionReconfiguration (step 12a1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND SETUP AND SCHEDULED AND HO] |
|||
|
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-DiscConfig-r12 SEQUENCE { |
|||
|
discTxResources-r12 CHOICE { |
|||
|
setup CHOICE { |
SETUP |
||
|
scheduled-r12 SEQUENCE { |
SCHEDULED |
||
|
discTxConfig-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000000 00001100 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000000 00001100 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: Including mobilityControlInfo (handover) and sl-DiscConfig, discTxResources set to setup, scheduled, one pool SL-DiscResourcePool-r12; Different settings to the pool(s) used before the release (set in step 3a1 and 7Aa1), different settings to the pool(s) set in the transmitted on the serving cell SystemInformationBlockType19. |
|||
Table 19.2.3.3.3-13: RRCConnectionReconfiguration (step 12b1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND SETUP AND UE-SELECTED AND HO] |
|||
|
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-DiscConfig-r12 SEQUENCE { |
|||
|
discTxResources-r12 CHOICE { |
|||
|
setup CHOICE { |
SETUP |
||
|
ue-Selected-r12 SEQUENCE { |
UE-SELECTED |
||
|
discTxPoolDedicated-r12 SEQUENCE { |
|||
|
poolToAddModList-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-DiscTxPoolToAddMod-r12 |
SETUP |
||
|
SL-DiscTxPoolToAddMod-r12[1] ::= SEQUENCE { |
TxPool 1 |
||
|
poolIdentity-r12 |
1 |
||
|
pool-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000011 00000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000011 00000000 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
SL-DiscTxPoolToAddMod-r12[2] ::= SEQUENCE { |
TxPool 2 |
||
|
poolIdentity-r12 |
2 |
||
|
pool-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00001100 00000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00001100 00000000 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: Including mobilityControlInfo (handover) and the discTxResources set to setup, ue-Selected and poolSelection within poolToAddModList is set to rsrpBased with threshLow and threshHigh and the serving cell power levels set to ensure that the RSRP measurement of the PCell, after applying the layer 3 filter defined by quantityConfig (part of MeasConfig) is in-between threshLow and threshHigh of exactly one of the provided pools. The transmission pools provides different settings in comparison to the transmission pool set in the broadcasted on the serving cell SystemInformationBlockType19 (see Table 19.2.3.3.3-1 or Table 19.2.3.3.3-2). |
|||
Table 19.2.3.3.3-14: RRCConnectionReconfiguration (step 15a1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC 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-DiscConfig-r12 SEQUENCE { |
|||
|
discTxResources-r12 CHOICE { |
|||
|
setup CHOICE { |
SETUP |
||
|
scheduled-r12 SEQUENCE { |
SCHEDULED |
||
|
discTxConfig-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000000 00001100 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000000 00001100 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: The same as step 12a1, Table 19.2.3.3.3-12, without the handover part. |
|||
Table 19.2.3.3.3-15: RRCConnectionReconfiguration (step 15b1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-8 A, condition [DISC AND SETUP AND UE-SELECTED] |
|||
|
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-DiscConfig-r12 SEQUENCE { |
|||
|
discTxResources-r12 CHOICE { |
|||
|
setup CHOICE { |
SETUP |
||
|
ue-Selected-r12 SEQUENCE { |
UE-SELECTED |
||
|
discTxPoolDedicated-r12 SEQUENCE { |
|||
|
poolToAddModList-r12 SEQUENCE (SIZE (1..maxSL-TxPool-r12)) OF SL-DiscTxPoolToAddMod-r12 |
SETUP |
||
|
SL-DiscTxPoolToAddMod-r12[1] ::= SEQUENCE { |
TxPool 1 |
||
|
poolIdentity-r12 |
1 |
||
|
pool-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000011 00000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000011 00000000 |
bs42-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
SL-DiscTxPoolToAddMod-r12[2] ::= SEQUENCE { |
TxPool 2 |
||
|
poolIdentity-r12 |
2 |
||
|
pool-r12 SEQUENCE { |
|||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00001100 00000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00001100 00000000 |
bs42-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: The same as step 12b1, Table 19.2.3.3.3-13, without the handover part. |
|||
Table 19.2.3.3.3-16: RRCConnectionReconfiguration (steps 23, 30, 35, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8, condition HO |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Note: A "standard" message for handover, including mobilityControlInfo but no sl-DiscConfig or any other DISC related IEs. |
|||
Table 19.2.3.3.3-17: RRCConnectionReconfiguration (step 28a1 a1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC 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.2.3.3.3-18: RRCConnectionReconfiguration (step 28a1b1, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, table 4.6.1-8 A, condition [DISC AND SETUP AND UE-SELECTED] |
|||
|
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.2.3.3.3-19: RRCConnectionReestablishmentRequest (step 17, Table 19.2.3.3.2-1)
|
Derivation Path: 36.508, 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 |
||
|
} |
|||
|
} |
|||
|
} |
|||