19.2.1 ProSe Direct Discovery Monitoring/Pre-configured authorisation / Monitoring / Handling of validity timers / Utilisation of the resources of different cells/PLMNs
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.1.1 Test Purpose (TP)
(1)
with { UE supporting ProSe direct discovery monitoring }
ensure that {
when { UE performs Attach procedure, or, Normal tracking area updating procedure }
then { UE announces its ProSe capabilities }
}
(2)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is NOT transmitting SystemInformationBlockType19 }
ensure that {
when { UE is triggered by an upper layer application to perform ProSe direct discovery monitoring corresponding to a ProSe Application ID and the UE has no valid Discovery Filters corresponding to the requested ProSe Application ID for that upper layer application }
then { UE does not initiate Monitoring request procedure }
}
(3)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies }
ensure that {
when { UE is triggered by an upper layer application to perform ProSe direct discovery monitoring corresponding to a ProSe Application ID and the UE has no valid Discovery Filters corresponding to the requested ProSe Application ID for that upper layer application }
then { UE successfully completes a Monitoring request procedure including the transmission of SidelinkUEInformation message indicating it is interested in sidelink discovery reception }
}
(4)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE has successfully completed Monitoring request procedure, and, the TTL timer T4002 associated with the Discovery Filter allocated during the procedure has not expired }
ensure that {
when { UE is monitoring for ProSe Announcements in the assigned resources on Cell1/f1/PLMN1 }
then { UE is able to receive messages announced over the PC5 in the assigned resources in Cell1/f1/PLMN1 }
}
(5)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell1/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired }
ensure that {
when { there is a match event of one of the ProSe Application Codes received from the lower layers, and the UE does not have a corresponding ProSe Application ID already locally stored }
then { the UE successfully performs a Match report procedure }
}
(6)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell1/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired, and, UE having successfully performed a Match report procedure }
ensure that {
when { UE has a locally stored mapping for the ProSe Application Code that resulted in the match event, but the match report refresh timer T4006 of the ProSe Application Code has expired }
then { the UE initiates the match report procedure }
}
(7)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell1/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired, and, the UE having successfully performed a Match report procedure }
ensure that {
when { UE has a locally stored mapping for the ProSe Application Code that resulted in the match event, but the validity timer T4004 of the ProSe Application Code has expired }
then { the UE initiates the match report procedure }
}
(8)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell1/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell1/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired }
ensure that {
when { UE moves to a new Cell2/f1/PLMN1 which is transmitting SystemInformationBlockType19 }
then { the UE continues successful monitoring without initiating a new Monitoring request procedure, and, is able to receive messages announced over the PC5 in the assigned resources in Cell2/f1/PLMN1 }
}
(9)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell2/f1/PLMN1 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell2/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired }
ensure that {
when { UE moves to a new Cell4/f1/PLMN2 (new PLMN)authorized for ProSe Direct Discovery Monitoring and transmitting SystemInformationBlockType19 providing Direct Discovery monitoring resources on the serving cell }
then { the UE initiates and successfully completes a new Monitoring request procedure, and, is able to receive messages announced over the PC5 in the assigned resources in Cell4/f1/PLMN2 }
}
(10)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements on Cell1/f1/PLMN1, and, the TTL timer T4002 associated with the Discovery Filter has not expired, and, monitoring for announcements on the resources of Cell4/f1/PLMN2 }
ensure that {
when { TTL timer T4002 expires }
then { the UE initiates and successfully completes a new Monitoring request procedure, and, is able to receive messages announced over the PC5 in the assigned resources in Cell4/f1/PLMN2 }
}
(11) Void
(12) Void
(13)
with { UE being authorized for performing ProSe Direct Discovery Monitoring on two PLMNs (PLMN1 and PLMN2) operating on the same frequency, and, UE attached to Cell4/f1/PLMN2 which is transmitting SystemInformationBlockType19 indicating the provision of Direct Discovery monitoring resources on the two PLMNs/frequencies, and, UE monitoring for ProSe Announcements, and, the TTL timer T4002 associated with the Discovery Filter allocated during the most recent Monitoring request procedure has not expired }
ensure that {
when { UE moves to a new Cell11/f1/PLMN3 transmitting SystemInformationBlockType19 however UE is not authorized for ProSe Direct Discovery Monitoring on PLMN3 }
then { the UE does not initiate Monitoring request procedure, and, does not monitor for messages announced over the PC5 in the assigned resources in Cell11/f1/PLMN3 }
}
19.2.1.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.301, clauses 5.5.1.2.2, 5.5.3.2.2, 6.1.1, TS 24.334, clauses 5.1.1, 5.1.2, 6.2.3.2, 6.2.3.4, 6.2.4.2, 6.2.4.4, TS 36.331, clauses 5.2.2.4, 5.2.2.26, 5.10.2.1, 5.10.2.2, 5.10.2.3, 5.10.5. 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.301, clause 5.5.1.2.2]
If the UE supports ProSe direct discovery, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct discovery bit to "ProSe direct discovery supported" in the UE network capability IE of the ATTACH REQUEST message.
[TS 24.301, clause 5.5.3.2.2]
The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME,
…
b) when the periodic tracking area updating timer T3412 expires;
…
If the UE has to request resources for ProSe direct discovery or Prose direct communication (see 3GPP TS 36.331 [22]), then the UE shall set the "active" flag to 1 in the TRACKING AREA UPDATE REQUEST message.
…
For all cases except case b, if the UE supports ProSe direct communication, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct communication bit to "ProSe direct communication supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message.
[TS 24.334, clause 5.1.1]
The service authorisation for ProSe direct discovery and ProSe direct communication determines whether the UE is authorised to use ProSe direct discovery announcing or ProSe direct discovery monitoring or both, and to use ProSe direct communication, in a particular PLMN or when not served by E-UTRAN. In this release of the specification, ProSe direct communication is supported only for Public Safety ProSe-enabled UE. The service authorisation is either:
1) pre-configured in the UE. The pre-configured service authorisation may be stored in the ME, or in the USIM as specified in 3GPP TS 31.102 [17], or in both the ME and the USIM. If both the ME and the USIM contain the same parameters, the values stored in the USIM shall take precedence. The UE shall not use the pre-configured service authorisation if the contents of the USIM indicate that the UE is not authorised to use them (see 3GPP TS 31.102 [17]); or
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.
[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.3.2]
Before initiating the monitor request procedure, the UE is configured with the data structure of the ProSe Application IDs it wants to monitor. This step is performed using mechanisms that are out of scope of 3GPP.
If the UE is authorised to perform ProSe direct discovery monitoring in at least one PLMN, it shall initiate a monitor request procedure:
a) when the UE is triggered by an upper layer application to perform ProSe direct discovery monitoring corresponding to a ProSe Application ID and the UE has no valid Discovery Filters corresponding to the requested ProSe Application ID for that upper layer application; or
b) when the TTL timer T4002 assigned by the ProSe Function to a Discovery Filter has expired and the request from upper layers to monitor that ProSe Application ID is still in place.
NOTE 1: To ensure service continuity if the UE needs to keep monitoring the same Discovery Filter, the UE can initiate the monitor request procedure before the TTL timer T4002 assigned by the ProSe Function for a Discovery Filter expires.
The UE initiates the monitor 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 "monitor", 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 monitoring.
NOTE 2: A UE can include one or multiple transactions in one DISCOVERY_REQUEST message for one or more ProSe Application IDs, and receive corresponding <response-monitor> element or <response-reject> element in the DISCOVERY_RESPONSE message for each respective transaction. In the following description of the monitor request procedure, only one transaction is included.
Figure 6.2.3.2.1 illustrates the interaction between the UE and the ProSe Function in the monitor request procedure.
Figure 6.2.3.2.1: Monitor request procedure
[TS 24.334, clause 6.2.3.4]
Upon receipt of the DISCOVERY_RESPONSE message, if the transaction ID contained in the <response-monitor> element matches the value sent by the UE in a DISCOVERY_REQUEST message with the command set to "monitor", the UE shall, for each Discovery Filter assigned by the ProSe Function, stop TTL timer T4002 if running and start TTL timer T4002 with the received value. Otherwise the UE shall discard the DISCOVERY_RESPONSE message and shall not perform the procedures below.
The UE may perform monitor for discovery messages received over the PC5 interface as described below.
For a ProSe Application ID requested by the monitoring UE, the ProSe Function may have assigned one or more Discovery Filters. The UE should apply all assigned Discovery Filters to its monitoring operation. Using these Discovery Filters may result in a match event. In case of a match event, the UE shall consider that the ProSe Application ID it seeks to monitor has been discovered. A match event is defined as follows:
There is a match event when, for any of the ProSe Application Masks in a Discovery Filter, the output of a bitwise AND operation between the ProSe Application Code contained in the received PC5_DISCOVERY message and the ProSe Application Mask, matches the output of a bitwise AND operation between the ProSe Application Mask and the ProSe Application Code contained in the same Discovery Filter.
NOTE: A ProSe Application Mask with all bits set to "1" is assigned by the ProSe Function for full matching.
The UE may instruct the lower layers to start monitoring if all of the following conditions are met:
– the UE is currently authorized to perform monitoring in at least one PLMN;
– the UE has obtained at least one Discovery Filter and their respective TTL timer T4002(s) have not expired; and
– a request from upper layers to monitor for the ProSe Application ID associated with an authorised Application Identity is still in place.
If the UE is in EMM-CONNECTED mode, the monitoring UE shall also trigger the corresponding procedure in lower layers as specified in 3GPP TS 36.331 [12].
During the monitoring operation, the UE receives all PC5_DISCOVERY messages and associated UTC times from the lower layers.
During the monitoring operation, if one of the above conditions is no longer met, the UE may instruct the lower layers to stop monitoring. When the UE stops monitoring, if 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 24.334, clause 6.2.4.2]
The UE shall meet the following pre-conditions before initiating this procedure:
– a request from upper layers to monitor for the ProSe Application ID, which resulted in the matched ProSe Application Code, is still in place;
– the lower layers have provided a "Monitored PLMN ID" value, and UTC time information, along with the discovery message containing a ProSe Application Code; and
– the TTL timer T4002 associated with the Discovery Filter, which resulted in a match event of the ProSe Application Code, has not expired.
If the UE is authorised to perform ProSe direct discovery monitoring in the monitored PLMN, it should initiate a match report procedure:
a) when there is a match event of one of the ProSe Application Codes received from the lower layers, and the UE does not have a corresponding ProSe Application ID already locally stored;
b) when the UE has a locally stored mapping for the ProSe Application Code that resulted in a match event, but the validity timer T4004 of the ProSe Application Code has expired; or
c) when the UE has a locally stored mapping for the ProSe Application Code that resulted in a match event, but the match report refresh timer T4006 of the ProSe Application Code has expired.
The UE initiates the match report procedure by sending a MATCH_REPORT message with a new transaction ID and shall set the message contents as follows:
– the UE shall set the ProSe Application Code to the ProSe Application Code for which there was a match event;
– the UE shall set the UE identity to the UE’s IMSI;
– the UE shall set the UTC-based counter as follows:
– the 28 most significant bits of the UTC-based counter shall be set to the 28 most significant bits of the UTC time provided by the lower layers for the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event encoded as specified in subclause 12.2.2.18; and
– the 4 least significant bits of the UTC-based counter shall be set to the 4 least significant bits of the UTC-based counter contained in the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event, as specified in 3GPP TS 33.303 [6];
– the UE shall set the MIC to the MIC of the PC5_DISCOVERY message that contained the ProSe Application Code for which there was a match event;
– the UE shall set the Monitored PLMN ID to the PLMN ID of the PLMN where the PC5_DISCOVERY message was received, as provided by the lower layers;
– if the UE was roaming when the match event occurred, the UE shall set the VPLMN ID to the PLMN ID of the PLMN in which the UE was registered when the match event occurred; and
– the UE shall set the Metadata Flag to indicate whether or not it wishes to receive metadata information associated with the ProSe Application ID in the MATCH_REPORT_ACK message from the ProSe Function.
NOTE 1: A UE can include one or multiple transactions in one MATCH_REPORT message for different ProSe Application Codes, and receive corresponding <match-ack> element or <match-reject> element in the MATCH_REPORT_ACK message for each respective transaction. In the following description of match report procedure, only one transaction is included.
NOTE 2: The value of the Metadata Flag is determined through an indication from upper layers in the original request to monitor for a ProSe Application ID.
Figure 6.2.4.2.1 illustrates the interaction between the UE and the ProSe Function in the match report procedure.
Figure 6.2.4.2.1: Match report procedure
[TS 24.334, clause 6.2.4.4]
Upon receipt of the MATCH_REPORT_ACK message, if the transaction ID contained in the <match-ack> element matches the value sent by the UE in a MATCH_REPORT message, the UE shall store the mapping between the ProSe Application Code and ProSe Application ID locally, start timers T4004 and T4006, and may inform the upper layers of this match of the ProSe Application ID. Otherwise the UE shall discard the MATCH_REPORT_ACK message.
Upon receipt of the MATCH_REPORT_ACK message, if the transaction ID contained in the <match-reject> element matches the value sent by the UE in a MATCH_REPORT message and if the received PC3 Control Protocol cause value is #5 "Invalid MIC", as specified in subclause 6.2.4.5, the UE shall stop timer T4004 if it is running.
NOTE 1: It is an implementation specific choice whether the UE informs the upper layers every time a ProSe Application ID triggers a match event, or only the first time this match occurs.
NOTE 2: The UE can also inform the upper layers if a ProSe Application ID is no longer matched, because the validity timer T4004 of the corresponding ProSe Application Code expires.
NOTE 3: The UE can also inform the upper layers if a ProSe Application ID is no longer matched, because the validity timer T4004 of the corresponding ProSe Application Code is stopped upon receiving MATCH_REPORT_ACK message with a <match-reject> element with PC3 Control Protocol cause value #5 "Invalid MIC".
[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;
2> for each of the one or more frequencies included in discInterFreqList, if included in SystemInformationBlockType19 and for which the UE is configured by upper layers to receive sidelink discovery announcements on:
3> if schedulingInfoList indicates that SystemInformationBlockType19 is present and the UE does not have stored a valid version of this system information block:
4> acquire SystemInformationBlockType19;
[TS 36.331, clause 5.2.2.26]
Upon receiving SystemInformationBlockType19, the UE shall:
1> if SystemInformationBlockType19 message includes the discConfig:
2> from the next discovery period, as defined by discPeriod, use the resources indicated by discRxPool for sidelink discovery monitoring, as specified in 5.10.5;
[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.
…
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 configured by upper layers to receive sidelink discovery announcements on a serving frequency or on one or more frequencies included in discInterFreqList, if included in SystemInformationBlockType19:
3> if the UE did not transmit a SidelinkUEInformation message since last 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 discRxInterest:
4> initiate transmission of the SidelinkUEInformation message to indicate it is interested in sidelink discovery reception in accordance with 5.10.2.3;
2> else:
3> if the last transmission of the SidelinkUEInformation message included discRxInterest:
4> initiate transmission of the SidelinkUEInformation message to indicate it is no longer interested in sidelink discovery reception 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 configured by upper layers to receive sidelink discovery announcements on a serving frequency or one or more frequencies included in discInterFreqList, if included in SystemInformationBlockType19:
3> include discRxInterest;
…
The UE shall submit the SidelinkUEInformation message to lower layers for transmission.
[TS 36.331, clause 5.10.5]
A UE capable of sidelink discovery that is configured by upper layers to monitor sidelink discovery announcements shall:
1> for each frequency the UE is configured to monitor sidelink discovery announcements on, prioritising the frequencies included in discInterFreqList, if included in SystemInformationBlockType19:
2> configure lower layers to monitor sidelink discovery announcements using the pool of resources indicated by discRxPool in SystemInformationBlockType19 without affecting normal operation i.e. receive during idle periods or by using a spare receiver;
NOTE 1: The requirement not to affect normal UE operation also applies for the acquisition of sidelink discovery related system and synchronisation information from inter-frequency cells.
NOTE 2: The UE is not required to monitor all pools simultaneously.
NOTE 3: It is up to UE implementation to decide whether a cell is sufficiently good to be used to monitor sidelink discovery announcements.
19.2.1.3 Test description
19.2.1.3.1 Pre-test conditions
System Simulator:
SS-NW
– 4 cells with parameters defined in Table 19.2.1.3.1-1.
NOTE: The test only requires 2 cells to be active at any one instant.
Table 19.2.1.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_MON 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 cells when SystemInformationBlockType19 is transmitted. In all other cases System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 shall be used.
– SystemInformationBlockType19 is transmitted on all cells when they are active unless otherwise stated; the sidelink related resources in each instance are specified in the specific message content.
SS-UE
– SS-UE 1.
– As defined in TS 36.508 [18], configured and operating for/as ProSe Direct Discovery Announcing on the resources provided by different cells (as specified in the relevant procedure steps in Table 19.2.1.3.2-1)
UE:
– ProSe related configuration
The UE is equipped with a USIM containing values shown in Table 19.2.1.3.1-2, and, relevant to each of the supported services values as specified in TS 36.508 [18], section 4.9.3.1 (e.g. 2 PLMNs are authorised for ProSe Direct Discovery Monitoring).
Table 19.2.1.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°4 (ProSe Direct Discovery monitoring 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 Monitoring (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 Monitoring (e.g. via MMI). The values specified for EFPROSE_MON 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. 7 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).
– The UE is configured with the data structure of the ProSe Application ID (px_ProSeMonApplicationIdentity1) it wants to monitor (This step is performed using UE implementation dependent mechanisms, e.g. MMI command, or, may be pre-loaded in the UE).
– A number of arbitrarily chosen ProSe Application IDs are provided during the test. The UE shall have no knowledge of them before the test is started.
– The UE has no valid Discovery Filters corresponding to the configured ProSe Application ID (px_ProSeMonApplicationIdentity1) nor to any other possibly pre-loaded ProSe Application IDs (this is to ensure that the provided during the test ProSe Application Codes are not known to the UE).
Preamble:
– The UE is in state Switched OFF (state 1) according to TS 36.508 [18].
19.2.1.3.2 Test procedure sequence
Table 19.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS configures: SS-NW – Cell 1 as the "Serving cell". – Cell 2 as the "Non-suitable “Off” cell". – Cell 4 as the "Non-suitable “Off” cell". – Cell 11 as the "Non-suitable “Off” cell". Cell 1 does not transmit SystemInformationBlockType19. |
– |
– |
– |
– |
|
2 |
The UE is switched on. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
3 |
Check: Does the UE announce that it is ProSe capable during registration? The Generic test procedure for ‘UE Registration (State 2)’ defined in TS 36.508 [18] clause 4.5.2 takes place. |
– |
– |
1 |
P |
|
4 |
Force the UE upper layer application corresponding to ProSe Application ID px_ProSeMonApplicationIdentity1 to initiate continuous ProSe direct discovery monitoring. |
– |
– |
– |
– |
|
5 |
Check: Does the 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 Monitor request procedure) in the next 5 sec? |
– |
– |
2 |
F |
|
6 |
From the beginning of the next modification period the SS-NW starts broadcast of SystemInformationBlockType19 (according to System information combination 24 as defined in TS 36.508[18] clause 4.4.3.1) on Cell 1. |
– |
– |
– |
– |
|
7 |
Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType19. |
– |
– |
– |
– |
|
8 |
Force the UE upper layer application corresponding to ProSe Application ID px_ProSeMonApplicationIdentity1 to initiate continuous ProSe direct discovery monitoring. |
– |
– |
– |
– |
|
9 |
Check: Does the 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 Monitor request procedure)? |
– |
– |
3 |
P |
|
10 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
– |
EXCEPTION: The events described in steps 10A – 10B are sent in the same transmission period. |
– |
– |
– |
– |
|
10A |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message which will produce match, and for which the UE does not have a corresponding ProSe Application ID already locally stored. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[2] broadcasted on the serving cell. Note that SIB19 includes a corresponding Tx resource for transmission in RRC_IDLE SystemInformationBlockType19/discTxPoolCommon-r12/SL-DiscResourcePool-r12[2], i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_IDLE. |
<– |
PC5_DISCOVERY |
– |
– |
|
10B |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message and which will not produce match. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[2] broadcasted on the serving cell. Note that SIB19 includes a corresponding Tx resource for transmission in RRC_IDLE SystemInformationBlockType19/discTxPoolCommon-r12/SL-DiscResourcePool-r12[2], i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_IDLE. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 11 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
11 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Match report procedure including the ProSe-Application-Code transmitted in step 10A and receiving a new ProSe-Application-ID)? NOTE: MATCH_REPORT_ACK message assigning T4006=[1] min, T4004=[4] min relevant to the newly provided ProSe-Application-ID. |
– |
– |
4, 5 |
P |
|
12 |
SS starts timer T4006. |
– |
– |
– |
– |
|
13 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
14 |
Void. |
– |
– |
– |
– |
|
15 |
SS waits for T4006 (match-report-refresh-timer) to expire. |
– |
– |
– |
– |
|
15A |
SS-UE1 transmits he same PC5_DISCOVERY message and utilising the same resources as the message transmitted in step 10A. |
<– |
PC5_DISCOVERY |
– |
– |
|
15B |
SS-UE1 transmits the same PC5_DISCOVERY message and utilising the same resources as the message transmitted in step 10B. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 16 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
16 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Match report procedure)? NOTE: MATCH_REPORT_ACK message assigning T4006=[4] min, T4004=[1] min |
– |
– |
6 |
P |
|
17 |
SS starts timer T4004. |
– |
– |
– |
– |
|
18 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
19 |
Void. |
– |
– |
– |
– |
|
20 |
SS waits for T4004 (validity-timer) to expire. |
– |
– |
– |
– |
|
20A |
SS-UE1 transmits he same PC5_DISCOVERY message and utilising the same resources as the message transmitted in step 15A. |
<– |
PC5_DISCOVERY |
– |
– |
|
20B |
SS-UE1 transmits he same PC5_DISCOVERY message and utilising the same resources as the message transmitted in step 15B. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 21 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
21 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Match report procedure)? |
– |
– |
7 |
P |
|
22 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
23 |
The SS configures: SS-NW – Cell 1 as the "Non-suitable “Off” cell". – Cell 2 as the "Serving cell". Cell 2 broadcasts SystemInformationBlockType19 which provides 2 reception pools, one of them is different to the resources broadcasted on the previous cell on which the UE monitored ProSe direct announcements (SL-DiscResourcePool-r12[1]). |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2. |
– |
– |
– |
– |
|
– |
EXCEPTION: The events described in steps 23A – 23B are sent in the same transmission period. |
– |
– |
– |
– |
|
23A |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message which will produce match, and for which the UE does not have a corresponding ProSe Application ID already locally stored. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
23B |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message and which will not produce match. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 24 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
24 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Match report procedure including the ProSe-Application-ID transmitted in step 21)? |
– |
– |
8 |
P |
|
25 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
26 |
The SS configures: SS-NW – Cell 2 as the "Non-suitable “Off” cell". – Cell 4 as the "Serving cell". – Cell 1 as "Suitable neighbour intra-frequency cell". Cell 4 broadcasts SystemInformationBlockType19 which provides 2 reception pools, one of them is different to the resources broadcasted on the previous cell on which the UE monitored ProSe direct announcements (SL-DiscResourcePool-r12[1]). |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4. |
– |
– |
– |
– |
|
27 |
Check: Does the UE announce its ProSe direct discovery capabilities? The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place. |
– |
– |
1 |
P |
|
28 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Monitor request procedure)? |
– |
– |
9 |
P |
|
29 |
SS-NW starts a timer=T4002. (the value of T4002 is provided in the DISCOVERY_RESPONSE message, step 28) |
– |
– |
– |
– |
|
30 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
– |
EXCEPTION: The events described in steps 30A – 30B are sent in the same transmission period. |
– |
– |
– |
– |
|
30A |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message which will produce match, and for which the UE does not have a corresponding ProSe Application ID already locally stored. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
30B |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message and which will not produce match. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 31 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
31 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Match report procedure including the ProSe-Application-ID transmitted in step 28)? |
– |
– |
9 |
P |
|
32 |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
33 |
SS-NW waits until the timer = T4002 set in step 29 expires. |
– |
– |
– |
– |
|
34 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place? (UE performs Monitor request procedure) |
– |
– |
10 |
P |
|
34A |
The SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
35-48 |
Void |
– |
– |
– |
– |
|
49 |
The SS configures: SS-NW – Cell 11 as the "Serving cell". – Cell 4 as the "Non-suitable “Off” cell". – Cell 1 as "Non-suitable “Off” cell". Cell 11 broadcasts SystemInformationBlockType19 which provides the same 2 reception pools as the previous cell on which the UE monitored ProSe direct announcements. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11. |
– |
– |
– |
– |
|
50 |
Check: Does the UE announce that it is ProSe capable during ‘Tracking area updating procedure? The Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 takes place. |
– |
– |
1 |
P |
|
51 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A takes place (UE performs Monitor request procedure) within the next 5s? |
– |
– |
13 |
F |
|
52 |
Force the UE upper layer application corresponding to ProSe Application ID px_ProSeMonApplicationIdentity1 to initiate ProSe direct discovery monitoring. |
– |
– |
– |
– |
|
53 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition ANNOUNCE/MONITOR REQUEST defined in TS 36.508 [18] subclause 4.5A.22A take place (UE performs Monitor request procedure) within the next 5? |
– |
– |
13 |
F |
|
– |
EXCEPTION: The events described in steps 53A – 53B are sent in the same transmission period. |
– |
– |
– |
– |
|
53A |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message which will produce match, and for which the UE does not have a corresponding ProSe Application ID already locally stored. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
53B |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message and which will not produce match. For the transmission the SS-UE1 shall use the resources indicated in SystemInformationBlockType19/discRxPool-r12/SL-DiscResourcePool-r12[1] broadcasted on the serving cell. Note that SIB19 does not include a corresponding Tx resource for transmission in RRC_IDLE, i.e. the SS-UE1 is behaving as an UE transmitting announcements in RRC_CONNECTED. |
<– |
PC5_DISCOVERY |
– |
– |
|
– |
EXCEPTION: In parallel to the events described in step 54 the events described in Table 19.2.1.3.2-3 take place (the same PC5_DISCOVERY messages are transmitted 2 more times). |
– |
– |
– |
– |
|
54 |
Check: Does the generic test procedure for ‘Communication with the ProSe Function’ with the condition MATCH REPORT defined in TS 36.508 [18] subclause 4.5A.22A take place within the next 5 sec? |
– |
– |
13 |
F |
Table 19.2.1.3.2-2: Void
Table 19.2.1.3.2-3: Parallel behaviour – PC5_DISCOVERY transmission
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
EXCEPTION: The events described in steps 1 – 2 are repeated 2 times. They shall be sent in the same transmission period. |
– |
– |
– |
– |
|
1 |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message which will produce match, and for which the UE does not have a corresponding ProSe Application ID already locally stored. For the transmission the SS-UE1 shall use the resources used for the first transmission of the same PC5_DISCOVERY message indicated in the relevant step in the main behaviour preceding the execution of the parallel behaviour. |
<– |
PC5_DISCOVERY |
– |
– |
|
2 |
SS-UE1 transmits a PC5_DISCOVERY message containing a ProSe Application Code different to the one provided in the last received DISCOVERY_RESPONSE message and which will not produce match. For the transmission the SS-UE1 shall use the resources used for the first transmission of the same PC5_DISCOVERY message indicated in the relevant step in the main behaviour preceding the execution of the parallel behaviour. |
<– |
PC5_DISCOVERY |
– |
– |
19.2.1.3.3 Specific message contents
Table 19.2.1.3.3-1: SystemInformationBlockType19 (Transmitted on Cell 1 in Table 19.2.1.3.2-1)
|
Derivation Path: 36.508 [18] Table 4.4.3.3-17 |
Table 19.2.1.3.3-2: SystemInformationBlockType19 (Transmitted on Cell 4 and Cell 11 in Table 19.2.1.3.2-1)
|
Derivation Path: 36.508 [18] Table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType19 ::= SEQUENCE { |
|||
|
discConfig-r12 ::= SEQUENCE { |
|||
|
discRxPool-r12 ::= SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[1] ::= SEQUENCE { |
RxPool 1 |
||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000000 00000011 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000000 00000011 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[1] |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note 1: The resources provided on RxPool 1 are different to the Rx resource(s) provided on cell 2 where the UE operates prior to moving to Cell 4. |
|||
Table 19.2.1.3.3-3: SystemInformationBlockType19 (Transmitted on Cell 2 in Table 19.2.1.3.2-1)
|
Derivation Path: 36.508 [18] Table 4.4.3.3-17 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType19 ::= SEQUENCE { |
|||
|
discConfig-r12 ::= SEQUENCE { |
|||
|
discRxPool-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[1] SEQUENCE { |
RxPool 1 |
||
|
tf-ResourceConfig-r12 SEQUENCE { |
|||
|
subframeBitmap-r12 |
00000000 11000000 00000000 00000000 00000000 |
bs40-r12 |
FDD |
|
00000000 11000000 |
bs16-r12 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
discTxPoolCommon-r12 SEQUENCE SIZE (1..maxSL-TxPool-r12) OF SL-DiscResourcePool-r12 { |
|||
|
SL-DiscResourcePool-r12[1] |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note 1: The resources provided on RxPool 1 are different to the Rx resource(s) provided on cell 1 where the UE operates prior to moving to Cell 2. |
|||
Table 19.2.1.3.3-4: ATTACH REQUEST (step 3, Table 19.2.1.3.2-1; step 4, TS 36.508 [18] Table 4.5.2.3-1)
|
Derivation path: 36.508 [18] table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
UE network capability |
|||
|
ProSe (octet 7, bit 7) |
‘1’ |
ProSe Supported |
|
|
..ProSe direct discovery (ProSe-dd) (octet 7, bit 8) |
‘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.1.3.3-5: TRACKING AREA UPDATE REQUEST (steps 27, 50, Table 19.2.1.3.2-1; step 4, TS 36.508 [18] Table 4.5A.2.1-1)
|
Derivation path: 36.508 [18] table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
UE network capability |
|||
|
EPS update type |
|||
|
"Active" flag |
‘1’B |
||
|
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.1.3.3-5 A : RRCConnectionRequest (steps 9, 28, 34, Table 19.2.1.3.2-1)
|
Derivation Path: 36.508, Table 4.6.1-16. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
mo-Data |
||
|
Delay tolerant |
|||
|
High priority access AC 11 – 15 |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 19.2.1.3.3-6: DISCOVERY_REQUEST (steps 9, 28, 34, Table 19.2.1.3.2-1; step 10a1, TS 36.508 [18] Table 4.5A.22.3-2)
|
Derivation path: 36.508 [18] , Table 4.7F.1-1. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
discovery-request1 { |
|||
|
command |
2 |
monitor |
|
|
} |
|||
Table 19.2.1.3.3-7: DISCOVERY_RESPONSE (step 9, Table 19.2.1.3.2-1; step 10a2, TS 36.508 [18] Table 4.5A.22.3-2)
|
Derivation path: 36.508 [18] , Table 4.7F.1-2. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Current-time |
Current UTC time |
||
|
response-announce[1] |
Not Present |
||
Table 19.2.1.3.3-8: SidelinkUEInformation (steps 9, 28, 34, 47, Table 19.2.1.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 |
||
|
commTxResourceReq-r12 |
Not Present |
||
|
discRxInterest-r12 |
true |
||
|
discTxResourceReq-r12 |
Not Present |
||
|
} |
|||
Table 19.2.1.3.3-9: Void
Table 19.2.1.3.3-10: PC5_DISCOVERY (steps 10B, 15B, 20B, 23B, 30B, 53B, Table 19.2.1.3.2-1 and step 2, Table 19.2.1.3.2-3 when step 2 happens in sequence with step 10B, 15B, 20B, 23B, 30B or 53B)
|
Derivation path: 36.508 [18] , Table 4.7F.1-5. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ProSe Application Code { |
|||
|
TemporaryID |
0000000011111111 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 |
Different to the one set by SS-NW in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure which will NOT provide a match with any of ProSe Application Masks included in the DISCOVERY_RESPONSE. |
|
|
} |
|||
Table 19.2.1.3.3-11: PC5_DISCOVERY (steps 10A, 15A, 20A, Table 19.2.1.3.2-1 and step 1, Table 19.2.1.3.2-3 when step 1 happens in sequence with step 10A, 15A, 20A)
|
Derivation path: 36.508 [18] , Table 4.7F.1-5. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ProSe Application Code { |
|||
|
TemporaryID |
1111111100000000 0000000000000000 1111111100000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 |
Different to the one set by SS-NW in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure which will provide a match. Will provide match when ProSe Application Mask[1] included in the DISCOVERY_RESPONSE is applied. |
|
|
} |
|||
Table 19.2.1.3.3-12: MATCH_REPORT (steps 11, 16, 21, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18] , Table 4.7F.1-3. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
transaction-ID |
a new transaction ID |
||
|
ProSe-Application-Code |
The code transmitted by PC5_DISCOVERY which was sent immediately before the MATCH REPORT and for which there was a match event (Table 19.2.1.3.3-11) |
||
|
Monitored-PLMN-id |
PLMN1 |
||
Table 19.2.1.3.3-12A: MATCH_REPORT_ACK (steps 11, 16, 21, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18], Table 4.7F.1-4. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Current-Time |
Current UTC time |
||
|
match-ack { |
|||
|
transaction-ID |
the transaction ID received in the MATCH_REPORT Table 19.2.1.3.3-12 |
||
|
ProSe-Application-ID |
mcc001.mnc001.ProSeApp.Food.Restaurants.Bulgarian999 |
a ProSe Application ID which the UE does not have The MCC/MNC values in mcc001.mnc001 shall be equal to the PLMN1. The ProSe Application ID Name part (ProSeApp.Food.Restaurants.Bulgarian999) is an arbitrary chosen (see TS 23.003 [2]) |
|
|
validity-timer-T4004 |
4 |
4 min |
|
|
match-report-refresh-timer-T4006 |
1 |
1 min |
|
|
} |
|||
Table 19.2.1.3.3-12B: PC5_DISCOVERY (step 23A, Table 19.2.1.3.2-1 and step 1, Table 19.2.1.3.2-3 when step 1 happens in sequence with step 23A)
|
Derivation path: 36.508 [18] clause 4.7F.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ProSe Application Code { |
|||
|
TemporaryID |
1111000000000000 0000000000000000 1111111100000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000011111111 |
Different to the one set by SS-NW in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure which will provide a match. Will provide match when ProSe Application Mask[2] included in the DISCOVERY_RESPONSE is applied. |
|
|
} |
|||
Table 19.2.1.3.3-13: MATCH_REPORT (step 24, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18] , Table 4.7F.1-3. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
transaction-ID |
a new transaction ID |
||
|
ProSe-Application-Code |
The code transmitted by PC5_DISCOVERY which was sent immediately before the MATCH REPORT and for which there was a match event (Table 19.2.1.3.3-12B) |
||
|
Monitored-PLMN-id |
PLMN1 |
||
Table 19.2.1.3.3-14: MATCH_REPORT_ACK (step 24, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18] , Table 4.7F.1-4. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Current-Time |
Current UTC time |
||
|
match-ack { |
|||
|
transaction-ID |
the transaction ID received in the MATCH_REPORT Table 19.2.1.3.3-13 |
||
|
ProSe-Application-ID |
mcc001.mnc001.ProSeApp.Food.Restaurants.Bulgarian888 |
a ProSe Application ID which the UE does not have The MCC/MNC values in mcc001.mnc001 shall be equal to the PLMN1. The ProSe Application ID Name part (ProSeApp.Food.Restaurants.Bulgarian888) is an arbitrary chosen (see TS 23.003 [2]) |
|
|
} |
|||
Table 19.2.1.3.3-14A: DISCOVERY_RESPONSE (steps 28, 34, Table 19.2.1.3.2-1; step 10a2, TS 36.508 [18] Table 4.5A.22.3-2)
|
Derivation path: 36.508 [18], Table 4.7F.1-1. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
response-monitor1 { |
|||
|
transaction-ID |
Same as that included by UE in the relevant DISCOVERY_REQUEST message and the relevant discovery-request |
||
|
discovery-filter[1] { |
|||
|
ProSe Application Code1 { |
|||
|
TemporaryID |
1111111100000000 1111111100000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 |
||
|
} |
|||
|
ProSe Application Mask[1] |
0000111111111100 00000000 1111111111111111 1111111111111111 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 |
Full matching for the MCC part is required, as well as for the first 32 bits of the Temporary ID in order a received ProSe Application Code to result in a match |
|
|
ProSe Application Mask[2] |
Not Present |
||
|
TTLTimer T4002 |
2 |
||
|
} |
|||
|
} |
|||
Table 19.2.1.3.3-14B: PC5_DISCOVERY (steps 30A, 53A Table 19.2.1.3.2-1 and step 1, Table 19.2.1.3.2-3 when step 1 happens in sequence with steps 30A or 53A)
|
Derivation path: 36.508 [18], Table 4.7F.1-5. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
ProSe Application Code { |
|||
|
TemporaryID |
1111111100000000 1111111100000000 1111111111111111 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 |
Different to the one set by SS-NW in the DISCOVERY_RESPONSE message sent during the latest Monitor request procedure which will provide a match. Will provide match when ProSe Application Mask[1] included in the DISCOVERY_RESPONSE is applied. |
|
|
} |
|||
Table 19.2.1.3.3-14C: MATCH_REPORT (step 31, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18], Table 4.7F.1-3. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
transaction-ID |
a new transaction ID |
||
|
ProSe-Application-Code |
The code transmitted by PC5_DISCOVERY which was sent immediately before the MATCH REPORT and for which there was a match event (Table 19.2.1.3.3-14B) |
||
|
Monitored-PLMN-id |
PLMN2 |
||
Table 19.2.1.3.3-15: MATCH_REPORT_ACK (step 31, Table 19.2.1.3.2-1)
|
Derivation path: 36.508 [18] , Table 4.7F.1-4. |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
match-ack { |
|||
|
transaction-ID |
the transaction ID received in the MATCH_REPORT Table 19.2.1.3.3-14C |
||
|
ProSe-Application-ID |
mcc001.mnc001.ProSeApp.Food.Restaurants.Bulgarian777 |
a ProSe Application ID which the UE does not have The MCC/MNC values in mcc001.mnc001 shall be equal to the PLMN1. The ProSe Application ID Name part (ProSeApp.Food.Restaurants.Bulgarian777) is an arbitrary chosen (see TS 23.003 [2]) |
|
|
validity-timer-T4004 |
1 |
4 min |
|
|
match-report-refresh-timer-T4006 |
4 |
4 min |
|
|
} |
|||