Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code: DatasetGenerationError
Exception: ArrowInvalid
Message: Failed to parse string: 'Response ended prematurely' as a scalar of type double
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1848, in _prepare_split_single
writer.write_table(table)
~~~~~~~~~~~~~~~~~~^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 765, in write_table
self._write_table(pa_table, writer_batch_size=writer_batch_size)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 773, in _write_table
pa_table = table_cast(pa_table, self._schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2312, in cast_table_to_schema
cast_array_to_feature(
~~~~~~~~~~~~~~~~~~~~~^
table[name] if name in table_column_names else pa.array([None] * len(table), type=schema.field(name).type),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
feature,
^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 1861, in wrapper
return pa.chunked_array([func(chunk, *args, **kwargs) for chunk in array.chunks])
~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2152, in cast_array_to_feature
return array_cast(
array,
...<2 lines>...
allow_decimal_to_str=allow_decimal_to_str,
)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 1863, in wrapper
return func(array, *args, **kwargs)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2015, in array_cast
return array.cast(pa_type)
~~~~~~~~~~^^^^^^^^^
File "pyarrow/array.pxi", line 1161, in pyarrow.lib.Array.cast
File "/usr/local/lib/python3.14/site-packages/pyarrow/compute.py", line 414, in cast
return call_function("cast", [arr], options, memory_pool)
File "pyarrow/_compute.pyx", line 604, in pyarrow._compute.call_function
File "pyarrow/_compute.pyx", line 399, in pyarrow._compute.Function.call
result = GetResultValue(
File "pyarrow/error.pxi", line 155, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
raise convert_status(status)
pyarrow.lib.ArrowInvalid: Failed to parse string: 'Response ended prematurely' as a scalar of type double
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1880, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
question string | answer_type string | answer string | accuracy float64 | mc_tf_outcome string | faithfulness float64 | answer_relevancy float64 | context_recall float64 | answer_correctness float64 | latency float64 | prompt_tokens int64 | completion_tokens int64 | total_tokens int64 | token_source string | cost null | error null |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
How many faders are used in the system simulator setup described for the Target E-UTRAN and Target ≠ E-UTRAN configurations? (Rel-19, V19.1.0) | mc | Question: How many faders are used in the system simulator setup described for the Target E-UTRAN and Target ≠ E-UTRAN configurations? (Rel-19, V19.1.0)
Options:
A. Two faders (Fader 1 and Fader 2)
B. Three faders (Fader 1, Fader 2, and Fader 3)
C. Four faders (Fader 1, Fader 2, Fader 3, and Fader 4)
Verdict: abstain... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.080777 | 241 | 184 | 425 | api | null | null |
Which UE configuration parameters can be updated in an SNPN according to this specification release? (Rel-19, V19.2.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. The specification release mentioned (Rel-19, V19.2.0) may have updated some parameters, but it is not clear which ones were updated. Therefore, guessing would not be appropriate in this case... | 0 | abstained | -1 | -1 | -1 | -1 | 0.432673 | 211 | 70 | 281 | api | null | null |
What does the SENSR KPI measure in IMS according to the specification? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. The specification mentioned is not specified, and the KPIs mentioned in the options are not unique to the given specification. Therefore, it is not possible to determine the correct answer ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.41754 | 210 | 68 | 278 | api | null | null |
What action is taken when the reportType is set to reportCGI and the UE detects that the requested NR cell is not transmitting SIB1? (Rel-19, V19.2.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct answer. The question refers to a specific scenario where the UE detects that the requested NR cell is not transmitting SIB1, and the reportType is set to reportCGI. However, the context doe... | 0 | abstained | -1 | -1 | -1 | -1 | 0.670549 | 224 | 111 | 335 | api | null | null |
In UM mode, when specific conditions are met including uplink transmission and RLC SDU beginning at the start of RLC PDU, what Length Indicator value should be used for 7-bit Length Indicators? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The provided context does not contain enough information to determine the answer. The specific conditions mentioned are not clear, and the options do not match any of the mentioned conditions. Therefore, it is not possible to determine the correct option based on the giv... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.391199 | 213 | 64 | 277 | api | null | null |
When must a GPRS MS in operation mode A use the normal GPRS attach procedure instead of the combined GPRS attach procedure? (Rel-19, V19.2.0) | mc | Question: When must a GPRS MS in operation mode A use the normal GPRS attach procedure instead of the combined GPRS attach procedure? (Rel-19, V19.2.0)
Options:
A. When emergency bearer services are required
B. When a circuit-switched transaction is ongoing
C. When the network operates in network operation mode II
Ve... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.851764 | 204 | 144 | 348 | api | null | null |
What happens when the HSS sends InsertSubscriberData messages despite a "skip subscriber data" indication being present? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. It is unclear what "skip subscriber data" indication is referring to, and what the consequences of sending InsertSubscriberData messages despite it would be. Therefore, it is not possible t... | 0 | abstained | -1 | -1 | -1 | -1 | 0.415275 | 224 | 68 | 292 | api | null | null |
In the SlicePpData schema, what serves as the key in the sliceUsgCtrlData map? (Rel-19, V19.2.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. The SlicePpData schema is not specified, and the sliceUsgCtrlData map is not defined. Therefore, it is impossible to identify the key in the sliceUsgCtrlData map based on the given options. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.432612 | 219 | 71 | 290 | api | null | null |
In the ServiceNameDescription schema, what is the requirement for the "language" field and the service content fields? (Rel-19, V19.1.0) | mc | Context: The ServiceNameDescription schema is a data format used to describe services in a standardized way. The "language" field is used to specify the language of the service content, while the "servName" field is used to specify the name of the service and the "servDescrip" field is used to specify a description of ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.788492 | 229 | 133 | 362 | api | null | null |
According to the call flow diagram, what happens after the "ICA Default Call Handling" decision is made and processed? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The provided context does not contain enough information to determine the correct option. The "ICA Default Call Handling" decision is not specified in the given call flow diagram, and the flow after that decision is not explicitly mentioned. Therefore, it is impossible to... | 0 | abstained | -1 | -1 | -1 | -1 | 0.463901 | 218 | 73 | 291 | api | null | null |
What must occur before a UE can transmit using Type 1 channel access procedure? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: While the options provided are related to the Type 1 channel access procedure, they do not provide enough information to determine the correct answer. The Type 1 channel access procedure is used for uplink transmission in 3GPP systems and involves several steps. The corre... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.611714 | 234 | 100 | 334 | api | null | null |
When determining the BWP switching delay T_BWPswitchDelay for multiple CCs where the BWP switch results in SCS change on any involved CC, which SCS should be used as the basis? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. The question refers to multiple CCs and SCS change, but it does not specify the number of CCs or the specific SCS values involved. Therefore, it is impossible to determine which SCS should b... | 0 | abstained | -1 | -1 | -1 | -1 | 0.509213 | 245 | 81 | 326 | api | null | null |
When a UP function sends additional PFCP Session Report Request messages following a PFCP Session Modification Response, how should the AURI flag be set? (Rel-19, V19.1.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct answer. It only states that the UP function sends additional PFCP Session Report Request messages following a PFCP Session Modification Response, but it does not specify the exact conditions... | 0 | abstained | -1 | -1 | -1 | -1 | 0.556703 | 267 | 90 | 357 | api | null | null |
When the IP-SM-GW receives an MO_FORWARD_SHORT_MESSAGE_ACK with SMS-SUBMIT-REPORT and specific conditions are met, what action shall it take? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The question requires knowledge of specific conditions that are not provided in the context. Therefore, it is not possible to determine the correct answer based on the given information. | 0 | abstained | -1 | -1 | -1 | -1 | 0.291305 | 233 | 46 | 279 | api | null | null |
When a subscriber registers on a VLR, what information about the Call Deflection service must the HLR send to the VLR? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct option. It is necessary to refer to the 3GPP technical specifications to determine the correct answer. | 0 | abstained | -1 | -1 | -1 | -1 | 0.295138 | 259 | 47 | 306 | api | null | null |
According to the MacAddr48Rm specification, how are features numbered and represented in the hexadecimal string? (Rel-19, V19.2.0) | mc | Verdict: abstained
Justification: The context provided does not contain enough information to determine the answer. The MacAddr48Rm specification is not mentioned, and the numbering and representation of features in a hexadecimal string is not specified. Therefore, it is not possible to determine the correct option ba... | 0 | abstained | -1 | -1 | -1 | -1 | 0.397332 | 270 | 66 | 336 | api | null | null |
What happens when a target PSA UPF does not support ECN marking for L4S during PSA UPF relocation? (Rel-19, V19.7.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. It is unclear what the specific requirements are for the SMF and the PSA UPF during the relocation procedure. Additionally, it is not specified whether the target PSA UPF can be upgraded to ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.533786 | 255 | 91 | 346 | api | null | null |
According to the MnS (Management Service) specification, what happens when a MnS Consumer sends a request with only "attrA" and "attrB" values, but the MnS Producer has no valid value for "attrC" and no default value is defined for "attrC"? (Rel-19, V19.1.0) | mc | Question: According to the MnS (Management Service) specification, what happens when a MnS Consumer sends a request with only "attrA" and "attrB" values, but the MnS Producer has no valid value for "attrC" and no default value is defined for "attrC"? (Rel-19, V19.1.0)
Options:
A. The response includes all three attrib... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.539191 | 291 | 274 | 565 | api | null | null |
In the Home Link Detection procedure, what should a UE do if there is a match between the Home Network Prefix and one of the local prefixes, but the UE currently has a valid DSMIPv6 Binding Update list entry? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct option. The subclauses mentioned in the options are not specified in the given context. Therefore, it is not possible to make an informed decision on the correct option. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.361335 | 267 | 60 | 327 | api | null | null |
When a UE is configured with "CS Voice preferred, IMS PS Voice as secondary" and the combined EPS/IMSI attach procedure succeeds with an "SMS-only" indication, what does the UE do next for voice calls? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The provided context does not contain enough information to determine the answer. The question mentions that the UE is configured with "CS Voice preferred, IMS PS Voice as secondary" and that the combined EPS/IMSI attach procedure succeeds with an "SMS-only" indication. H... | 0 | abstained | -1 | -1 | -1 | -1 | 0.692089 | 246 | 118 | 364 | api | null | null |
In the SCC AS multimedia session scenario, what happens to the media paths after the SIP signaling exchange is completed? (Rel-19, V19.0.0) | mc | Question: In the SCC AS multimedia session scenario, what happens to the media paths after the SIP signaling exchange is completed? (Rel-19, V19.0.0)
Options:
A. All media paths are terminated and re-established through different interworking entities
B. The CS bearer is converted to a realtime media path while mainta... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.013688 | 246 | 180 | 426 | api | null | null |
According to the measurement reporting procedure described, which events are evaluated by comparing reported RSRP values between different cells? (Rel-19, V19.1.0) | mc | Verdict: abstained
Option: null
Justification: The question seems to be based on the measurement reporting procedure described in 3GPP TS 36.214, but it does not provide enough context to determine the correct answer. The events mentioned in the question are not explicitly defined in the standard, and it is unclear w... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.544244 | 284 | 92 | 376 | api | null | null |
What happens when an MCData client attempts to make an imminent peril group communication while the group is already in an in-progress emergency group state? (Rel-19, V19.2.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. It is unclear what the specific requirements and conditions are for making an MCData client attempt to make an imminent peril group communication while the group is already in an in-progres... | 0 | abstained | -1 | -1 | -1 | -1 | 0.476368 | 249 | 82 | 331 | api | null | null |
What is the key difference between the sliding window technique and the fixed window technique in TFH carrier list management? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct answer. The question asks for the key difference between the sliding window technique and the fixed window technique in TFH carrier list management, but it does not provide any specific det... | 0 | abstained | -1 | -1 | -1 | -1 | 0.491371 | 267 | 84 | 351 | api | null | null |
In the IMS service data change information flow, what is the sequence of operations performed by HSS-FE with the UDR after receiving the Sh-Update from the Application Server? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The question requires knowledge of the specific sequence of operations performed by HSS-FE with the UDR in the context of the IMS service data change information flow. While the options provided are related to the process, they do not provide enough information to determ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.518133 | 290 | 90 | 380 | api | null | null |
What is the status of protocol control information compression support for Multimedia Broadcast/Multicast Service (MBMS)? (Rel-19, V19.0.0) | mc | Question: What is the status of protocol control information compression support for Multimedia Broadcast/Multicast Service (MBMS)? (Rel-19, V19.0.0)
Options:
A. ROHC decompression is optional but recommended for optimal MBMS performance
B. ROHC compression is optional and negotiated via SNDPCP XID parameters
C. ROHC ... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.162873 | 249 | 210 | 459 | api | null | null |
According to the 5G Media Streaming (5GMSd) service flow diagram, in which phase does the "5GMSd Service Access Information acquisition" occur? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. The 5GMSd service flow diagram is not specified, and the version (Rel-19, V19.0.0) is not sufficient to identify the exact phase where "5GMSd Service Access Information acquisition" occurs. ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.52457 | 230 | 93 | 323 | api | null | null |
In the Multi-RTT positioning procedure, what does the LMF do after receiving both DL-PRS measurements from the target device and UE SRS measurements from the gNBs? (Rel-19, V19.1.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct option. The Multi-RTT positioning procedure involves several steps and the LMF's actions depend on the specific scenario and configuration. Therefore, it is not possible to identify the corr... | 0 | abstained | -1 | -1 | -1 | -1 | 0.399799 | 267 | 69 | 336 | api | null | null |
According to the SMS functional requirements, what must a Service Centre (SC) do when two or more messages to the same MS arrive within one second? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct answer. The SMS functional requirements mentioned in the question are not specified, and the version of the 3GPP technical specification (Rel-19, V19.0.0) is not provided. Therefore, it is ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.474934 | 258 | 82 | 340 | api | null | null |
When a UE is configured with highPriorityMeasRelax and meets the lowMobilityEvaluation criterion, how frequently must it search for inter-frequency layers of higher priority? (Rel-19, V19.0.0) | mc | Question: When a UE is configured with highPriorityMeasRelax and meets the lowMobilityEvaluation criterion, how frequently must it search for inter-frequency layers of higher priority? (Rel-19, V19.0.0)
Options:
A. At least every T_higher_priority_search
B. At least every T_detect,NR_Inter_Relax
C. At least every 30 *... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.97266 | 246 | 174 | 420 | api | null | null |
In a RANflex configuration where the originating MSC is the group call serving MSC, what should be included in the generic number parameter when passing the call request to the anchor MSC? (Rel-19, V19.0.0) | mc | The answer to this question is option D. The address of the group call serving MSC with number qualifier indicator set to "calling party number" should be included in the generic number parameter when passing the call request to the anchor MSC in a RANflex configuration where the originating MSC is the group call servi... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.677886 | 285 | 121 | 406 | api | null | null |
When an intermediate node processes a Single Codec information element for an AMR codec with OM set to "Optimization of the ACS supported", what must it do if the last codec mode is deleted from the offered SCS? (Rel-19, V19.0.0) | mc | Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the correct answer. The question refers to specific technical details related to the AMR codec and its parameters, which are not mentioned in the given context. Therefore, it is not possible to provide ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.409365 | 259 | 71 | 330 | api | null | null |
When a UE indicates 'no-gap' via NeedForGapsInfoNR and no-gap-no-interruption via NeedForInterruptionInfoNR for inter-frequency measurement, what condition applies to the SMTC occasions? (Rel-19, V19.0.0) | mc | Question: When a UE indicates 'no-gap' via NeedForGapsInfoNR and no-gap-no-interruption via NeedForInterruptionInfoNR for inter-frequency measurement, what condition applies to the SMTC occasions? (Rel-19, V19.0.0)
Options:
A. Part of the SMTC occasions are overlapped by measurement gaps or the union of concurrent mea... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.859911 | 281 | 339 | 620 | api | null | null |
When the current serving cell is among the candidate cells and rangeToBestCell is configured, what is the minimum ranking difference required for cell reselection in FR2? (Rel-19, V19.0.0) | mc | Verdict: abstained
Justification: The context provided does not contain enough information to determine the answer. The question refers to a specific configuration (rangeToBestCell) and a particular frequency range (FR2), which may not be applicable to all scenarios. Additionally, the minimum ranking difference requir... | 0 | abstained | -1 | -1 | -1 | -1 | 0.509184 | 223 | 92 | 315 | api | null | null |
When a UE is in a visited country and the DNS response for the Visited Country Emergency SNPN FQDN query contains no records, what should the UE do next? (Rel-19, V19.2.0) | mc | Question: When a UE is in a visited country and the DNS response for the Visited Country Emergency SNPN FQDN query contains no records, what should the UE do next? (Rel-19, V19.2.0)
Options:
A. The UE may proceed to bullet a) 1), a) 2) or a) 3)
B. The UE shall select any available SNPN from its stored configuration
C.... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.196144 | 268 | 222 | 490 | api | null | null |
Which HTTP reference points shall be used by the SEAL-X1 reference point for transport and routing of security related information? (Rel-19, V19.5.0) | mc | Verdict: abstained
Option: null
Justification: The provided context does not contain enough information to determine the correct option. The question asks about the HTTP reference points to be used by the SEAL-X1 reference point for transport and routing of security related information, but it does not specify which ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.503727 | 230 | 91 | 321 | api | null | null |
What are the two possible string values that can be set in the <acknowledgement> element within <DAA-server-event-info-ack>? (Rel-19, V19.2.0) | mc | Verdict: abstained
Option: null
Justification: While the question provides a specific context related to the 3GPP technical specifications, it does not contain enough information to determine the correct answer. The <acknowledgement> element within <DAA-server-event-info-ack> is not explicitly mentioned in the provide... | 0 | abstained | -1 | -1 | -1 | -1 | 0.496944 | 212 | 89 | 301 | api | null | null |
According to the NF discovery procedure shown, what does the c-SEPP do when the URI scheme in the response is https? (Rel-19, V19.2.0) | mc | Question: According to the NF discovery procedure shown, what does the c-SEPP do when the URI scheme in the response is https? (Rel-19, V19.2.0)
Options:
A. c-SEPP rewrites the FQDN part of the API root to Telescopic FQDN
B. c-SEPP forwards the response without any modifications to maintain end-to-end security
C. c-SE... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.160594 | 281 | 213 | 494 | api | null | null |
What is the size of the LWIPEP Header when both the Key and Sequence Number fields are included? (Rel-19, V19.0.0) | mc | Question: What is the size of the LWIPEP Header when both the Key and Sequence Number fields are included? (Rel-19, V19.0.0)
Options:
A. Twelve bytes
B. Eight bytes
C. Sixteen bytes
Verdict: abstained
Option: null
Justification: The context provided does not contain enough information to determine the answer. It is ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.767494 | 184 | 143 | 327 | api | null | null |
According to the FR2 cell power level configuration at time instance T0, what is the relationship between the R values of the three NR cells? (Rel-19, V19.0.0) | mc | Question: According to the FR2 cell power level configuration at time instance T0, what is the relationship between the R values of the three NR cells? (Rel-19, V19.0.0)
Options:
A. R_NRCell 11 < R_NRCell 1 < R_NRCell 12
B. R_NRCell 1 > R_NRCell 12 > R_NRCell 11
C. R_NRCell 1 < R_NRCell 12 < R_NRCell 11
Respond with ... | 0 | incorrect | -1 | -1 | -1 | -1 | 1.470855 | 235 | 273 | 508 | api | null | null |
The RSC values from "000001" to "00000F" in hexadecimal representation are reserved for future use and may be implemented in later specification releases. (Rel-19, V19.1.0) | tf | Question: The RSC values from "000001" to "00000F" in hexadecimal representation are reserved for future use and may be implemented in later specification releases. (Rel-19, V19.1.0)
Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the state... | 0 | abstained | -1 | -1 | -1 | -1 | 0.592937 | 179 | 111 | 290 | api | null | null |
When the originating UE does not support the precondition mechanism, the AS must always send an UPDATE request regardless of whether the media types in the CAT SDP differ from the initial INVITE request. (Rel-19, V19.0.0) | tf | The statement is true. According to the 3GPP technical specification 24.229 (Rel-19, V19.0.0), when the originating UE does not support the precondition mechanism, the AS must always send an UPDATE request regardless of whether the media types in the CAT SDP differ from the initial INVITE request. This is because the p... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.625892 | 185 | 117 | 302 | api | null | null |
When access is barred because of access class control and ACDC is applicable to the request from upper layers, the MS shall not start the GPRS attach procedure even if it supports ACDC. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is not clear what "ACDC" stands for or what "GPRS attach procedure" entails. Additionally, it is not specified what "access class control" refers to or how it... | 0 | abstained | -1 | -1 | -1 | -1 | 0.525309 | 185 | 98 | 283 | api | null | null |
When the SMF decides to re-activate an existing PDU session with SSC mode 1 or SSC mode 2, it sends the replaced S-NSSAI to the UE during the PDU session modification procedure. (Rel-19, V19.2.0) | tf | The statement is true. According to the 3GPP TS 23.501 V19.2.0, when the SMF decides to re-activate an existing PDU session with SSC mode 1 or SSC mode 2, it sends the replaced S-NSSAI to the UE during the PDU session modification procedure. This is a technical requirement specified in the standard, and it is clear fro... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.566228 | 191 | 105 | 296 | api | null | null |
The 5GS in an SNPN supports updating both routing indicator and default configured NSSAI parameters on the USIM. (Rel-19, V19.2.0) | tf | Context: The 5GS in an SNPN supports updating both routing indicator and default configured NSSAI parameters on the USIM. (Rel-19, V19.2.0)
Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It only states that ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.750197 | 171 | 136 | 307 | api | null | null |
When PS handover procedure is terminated, the source BSS resumes all TBFs and for normal PS Handover it indicates the failure to the SGSN, while for optimized PS Handover it indicates the failure to the target BSS. (Rel-19, V19.0.0) | tf | The statement is true. The context provided indicates that the source BSS resumes all TBFs and for normal PS Handover it indicates the failure to the SGSN, while for optimized PS Handover it indicates the failure to the target BSS. This information is sufficient to determine that the statement is accurate. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.353314 | 196 | 64 | 260 | api | null | null |
When a data link layer entity receives a supervisory response with the F bit set to "1", it shall reset timer T200 and may transmit new I frames if the response is an RNR response. (Rel-19, V19.0.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. The statement is a fragment of a larger protocol specification, and it is not clear what the surrounding context is. Therefore, it is not possible to determine w... | 0 | abstained | -1 | -1 | -1 | -1 | 0.420632 | 188 | 75 | 263 | api | null | null |
The gNB forwards application layer measurement reports to MCE together with the QoE reference after mapping the measurement configuration application layer ID to the QoE reference. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context is too technical and specific to be easily understood by a chatbot. It requires a deep understanding of 3GPP standards and technical specifications, which is beyond the scope of this chatbot. Therefore, it is not possible to determine whether the sta... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.435027 | 180 | 77 | 257 | api | null | null |
For the DM-RS of PDCCH, when a UE is configured with dl-OrJointTCI-StateList, the indicated TCI-State can use 'typeA' with a CSI-RS resource configured with higher layer parameter repetition. (Rel-19, V19.3.0) | tf | The provided context is not sufficient to determine whether the statement is true or false. Therefore, the verdict is "abstained" and the boolean value is null. The justification is that the context does not provide enough information to make a determination. | 0 | abstained | -1 | -1 | -1 | -1 | 0.281649 | 196 | 50 | 246 | api | null | null |
For DRX configurations greater than 320 ms, the evaluation period formula includes a factor of 1.5 times M_out. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. The evaluation period formula is not specified, and M_out is not defined. Therefore, it is impossible to determine the validity of the statement based on the giv... | 0 | abstained | -1 | -1 | -1 | -1 | 0.372041 | 173 | 65 | 238 | api | null | null |
When the DL LBT Failure Information Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use it for temporary capability restriction if supported. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. The statement is based on the inclusion of the DL LBT Failure Information Request IE in the UE CONTEXT MODIFICATION REQUEST message, which is a specific scenario... | 0 | abstained | -1 | -1 | -1 | -1 | 0.563624 | 182 | 101 | 283 | api | null | null |
When SR_COUNTER reaches sr-TransMax, the MAC entity notifies RRC to release PUCCH and SRS for all Serving Cells. (Rel-19, V19.2.0) | tf | The statement is true. The context provided indicates that when the SR_COUNTER reaches sr-TransMax, the MAC entity notifies RRC to release PUCCH and SRS for all Serving Cells. This is a clear indication that the statement is true. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.299072 | 175 | 51 | 226 | api | null | null |
Configuration Constraints require that a field can only be signalled if another field is present in the same message. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. The statement mentions "Configuration Constraints" and "a field can only be signalled if another field is present in the same message," but it does not specify w... | 0 | abstained | -1 | -1 | -1 | -1 | 0.535585 | 168 | 96 | 264 | api | null | null |
The crossCarrierSchedulingProcessing-DiffSCS-r16 capability applies to both triggering and triggered serving cells, and when reported values differ between bands, the value from the scheduled cell is applied. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. The statement mentions the crossCarrierSchedulingProcessing-DiffSCS-r16 capability, triggering and triggered serving cells, and reporting values from different b... | 0 | abstained | -1 | -1 | -1 | -1 | 0.568158 | 186 | 101 | 287 | api | null | null |
For clause 4.2B.2.11.5, the UE must be configured with lowMobilityEvaluation criterion and have fulfilled it, plus be configured with both stationaryMobilityEvaluation and cellEdgeEvaluationWhileStationary criteria and have fulfilled both of them. (Rel-19, V19.0.0) | tf | The statement is true. The context provided indicates that the UE must be configured with lowMobilityEvaluation criterion and have fulfilled it, plus be configured with both stationaryMobilityEvaluation and cellEdgeEvaluationWhileStationary criteria and have fulfilled both of them. This means that the UE has met all th... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.397385 | 201 | 70 | 271 | api | null | null |
The event triggered measurement reporting delay shall be less than T_measurement_NR_FDD when the timing to that cell has changed more than ±3200 Tc. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. The specific values of T_measurement_NR_FDD and Tc are not given, so it is impossible to determine whether the event triggered measurement reporting delay will b... | 0 | abstained | -1 | -1 | -1 | -1 | 0.544416 | 178 | 97 | 275 | api | null | null |
When the S4-SGSN decides not to activate reporting UE presence in one or more Presence Reporting Areas, it must exclude those inactive areas from the Update Bearer Request message. (Rel-19, V19.0.0) | tf | The statement is true. According to the 3GPP TS 29.274 specification, when the S4-SGSN decides not to activate reporting UE presence in one or more Presence Reporting Areas, it must exclude those inactive areas from the Update Bearer Request message. This is because the S4-SGSN needs to ensure that the MME is aware of ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.780139 | 183 | 140 | 323 | api | null | null |
The CP function and the UP function shall support the Sx association setup initiated by the UP function. (Rel-19, V19.0.0) | tf | Context: "The CP function and the UP function shall support the Sx association setup initiated by the UP function. (Rel-19, V19.0.0)"
Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. It only states that the CP a... | 0 | abstained | -1 | -1 | -1 | -1 | 0.686624 | 167 | 124 | 291 | api | null | null |
The flowchart shows that when ICA Default Call Handling is set to "Release Call", the process transitions directly to the DP_Collected_Info state without going through the Int_Initiate Call Attempt ack step. (Rel-19, V19.0.0) | tf | The statement is true. The flowchart shows that when ICA Default Call Handling is set to "Release Call", the process transitions directly to the DP_Collected_Info state without going through the Int_Initiate Call Attempt ack step. This means that the call is released without any further action, and the system moves on ... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.424848 | 189 | 77 | 266 | api | null | null |
When the UE wishes to connect to an additional PDN, it sends a Registration Request (RRQ) message that must include the Home Agent address field. (Rel-19, V19.0.0) | tf | Context: The UE wants to connect to an additional PDN, and it sends a Registration Request (RRQ) message that includes the Home Agent address field. The RRQ message is sent to the SGSN, which then forwards it to the GGSN. The GGSN checks the RRQ message and determines whether the UE is authorized to connect to the addi... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.915135 | 178 | 167 | 345 | api | null | null |
In the IMS service data change information flow, the HSS-FE sends a Sh-Update-Rsp message to the Application Server after receiving confirmation that the service data has been updated in the UDR. (Rel-19, V19.0.0) | tf | Context: The HSS-FE sends a Sh-Update-Rsp message to the Application Server after receiving confirmation that the service data has been updated in the UDR. This is a standard procedure in the IMS service data change information flow. Therefore, it is true that the HSS-FE sends a Sh-Update-Rsp message to the Application... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.490739 | 188 | 87 | 275 | api | null | null |
The NSCE_NSOptimization API includes a Resource called "Individual Network Slice Optimization Subscription" that supports GET, PUT, PATCH, and DELETE standard methods. (Rel-19, V19.1.0) | tf | True. The context provided includes enough information to determine that the NSCE_NSOptimization API includes a Resource called "Individual Network Slice Optimization Subscription" that supports GET, PUT, PATCH, and DELETE standard methods. This is because the question explicitly states that the API includes this Resou... | 1 | correct | -1 | -1 | -1 | -1 | 0.390935 | 179 | 70 | 249 | api | null | null |
The discovery of NFs in the 5G System is supported by the NRF, with DNS procedures defined for AMF discovery by 5G-AN and AMF discovery by MME for EPS interworking. (Rel-19, V19.1.0) | tf | Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. It only mentions that the discovery of NFs in the 5G System is supported by the NRF, with DNS procedures defined for AMF discovery by 5G-AN and AMF discovery by ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.64547 | 190 | 117 | 307 | api | null | null |
The AN_INFO policy control request trigger requires the "lastReqRuleData" attribute to contain both the "reqData" attribute and the "refPccRuleIds" attribute when processing PCC rules. (Rel-19, V19.2.0) | tf | The statement is true. The "lastReqRuleData" attribute is required to contain both the "reqData" attribute and the "refPccRuleIds" attribute when processing PCC rules according to the AN_INFO policy control request trigger in Rel-19, V19.2.0. This is because the "reqData" attribute provides the policy control request d... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.628226 | 188 | 114 | 302 | api | null | null |
When subscription data includes the DL-Buffering-Suggested-Packet-Count AVP, the MME or SGSN must invoke extended buffering of downlink packets at the SGW for High Latency Communication. (Rel-19, V19.1.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It only mentions that subscription data includes the DL-Buffering-Suggested-Packet-Count AVP, but it does not provide any details about the specific conditions o... | 0 | abstained | -1 | -1 | -1 | -1 | 0.569678 | 190 | 105 | 295 | api | null | null |
When the HSS sends InsertSubscriberData messages despite a "skip subscriber data" indication being present, the IWF must store the received data. (Rel-19, V19.0.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is unclear what the "skip subscriber data" indication refers to, and whether it is applicable in the given scenario. Therefore, it is not possible to make a d... | 0 | abstained | -1 | -1 | -1 | -1 | 0.393795 | 176 | 72 | 248 | api | null | null |
The GmCapable enumeration includes three values: GTP for gPTP grandmaster support, PTP for PTP grandmaster support, and ETH for Ethernet support. (Rel-19, V19.2.0) | tf | The provided context does not contain enough information to determine whether the statement is true or false. Therefore, the verdict is "abstained" and the boolean is null. The justification is that the statement requires knowledge of the specific capabilities of the GmCapable enumeration, which is not provided in the ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.356056 | 182 | 63 | 245 | api | null | null |
When indirect data forwarding applies, the DL forwarding tunnel information shall contain the E-UTRAN tunnel info for data forwarding per EPS bearer received from the MME. (Rel-19, V19.2.0) | tf | Context: The context provided is a statement about the DL forwarding tunnel information containing E-UTRAN tunnel info for data forwarding per EPS bearer received from the MME. This statement is based on the 3GPP technical specification Rel-19, version 19.2.0.
Verdict: abstained
Boolean: null
Justification: The conte... | 0 | abstained | -1 | -1 | -1 | -1 | 0.760323 | 180 | 142 | 322 | api | null | null |
For UE category 0 RSRQ intra frequency absolute accuracy, the normal condition accuracy requirement is ±4.5 dB for all E-UTRA operating band groups when Ês/Iot is ≥-3 dB. (Rel-19, V19.1.0) | tf | The statement is true. The context provided specifies that for UE category 0 RSRQ intra frequency absolute accuracy, the normal condition accuracy requirement is ±4.5 dB for all E-UTRA operating band groups when Ês/Iot is ≥-3 dB. This means that when the signal strength is at least -3 dB, the accuracy requirement for R... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.515831 | 192 | 92 | 284 | api | null | null |
The additionalSpectrumEmission-r13 parameter can have values of 1 (NS_01) or 4 (NS_04), where NS_01 indicates that A-MPR doesn't apply by default. (Rel-19, V19.2.0) | tf | The statement is true. The additionalSpectrumEmission-r13 parameter has two possible values, NS_01 and NS_04. NS_01 indicates that A-MPR doesn't apply by default. Therefore, if the value of additionalSpectrumEmission-r13 is NS_01, then A-MPR doesn't apply by default. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.400829 | 190 | 70 | 260 | api | null | null |
The GMLCFunction has a one-to-many relationship with EP_NL9, which connects to the NWDAFFunction. (Rel-19, V19.3.0) | tf | The statement is true. The GMLCFunction has a one-to-many relationship with EP_NL9, which connects to the NWDAFFunction. This is based on the Rel-19, V19.3.0 context provided. The GMLCFunction is a Gateway Mobile Location Centre that provides location information to emergency services. EP_NL9 is an External Provider of... | 0 | incorrect | -1 | -1 | -1 | -1 | 0.763884 | 173 | 145 | 318 | api | null | null |
CR 0252 with revision 1 was approved at meeting RP-83 to add new applicability for user initiated USSI, updating the specification from version 14.5.0 to 14.6.0. (Rel-19, V19.0.0) | tf | The statement is true. CR 0252 with revision 1 was approved at meeting RP-83 to add new applicability for user initiated USSI, updating the specification from version 14.5.0 to 14.6.0. This information is provided in the context of the question, so it is possible to determine that the statement is true. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.409791 | 192 | 74 | 266 | api | null | null |
For scheduled recording, the SCF creates a timer for the request and when the start time comes, it directs the PSS Adapter to set up the delivery channel. (Rel-19, V19.0.0) | tf | The statement is true. The context provided indicates that the SCF creates a timer for the request and when the start time comes, it directs the PSS Adapter to set up the delivery channel. This suggests that the scheduled recording is successfully set up and will be executed as planned. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.32312 | 180 | 57 | 237 | api | null | null |
Service announcement senders must increment the version by exactly one for each subsequent transported version of a metadata fragment, and UEs will reject any versions with increments greater than one. (Rel-19, V19.0.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is unclear what "Service announcement senders" and "UEs" refer to, and what "transported version of a metadata fragment" means. Additionally, the context does... | 0 | abstained | -1 | -1 | -1 | -1 | 0.57369 | 181 | 108 | 289 | api | null | null |
The EF_STK file has a structure of linear fixed with records that can hold up to 40 test data records, each with a default value of 'FF FF .. FF FF'. (Rel-19, V19.1.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is unclear what the EF_STK file is or what its purpose is. Additionally, it is not specified how the records are used or what the default values are for. Ther... | 0 | abstained | -1 | -1 | -1 | -1 | 0.462904 | 184 | 87 | 271 | api | null | null |
The time T_measure per 480 ms period is calculated as the sum of all idle intervals minus the time used for beacon timeslots of the serving cell. (Rel-19, V19.0.0) | tf | The statement is true. The context provides enough information to determine that the time T_measure per 480 ms period is calculated as the sum of all idle intervals minus the time used for beacon timeslots of the serving cell. Therefore, the statement is true. | 0 | incorrect | -1 | -1 | -1 | -1 | 0.28912 | 178 | 52 | 230 | api | null | null |
If the RADIO LINK SETUP REQUEST message includes the Allowed Queuing Time IE, the DRNS must queue the request for the specified time period before execution. (Rel-19, V19.0.0) | tf | Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether the statement is true or false. It only mentions the presence of the Allowed Queuing Time IE in the RADIO LINK SETUP REQUEST message and the requirement to queue the request for the specified ti... | 0 | abstained | -1 | -1 | -1 | -1 | 0.545372 | 177 | 106 | 283 | api | null | null |
The Charging Data Request[Stop] is sent when the ProSe Function receives a Received Direct Communication Usage Report event and there is an open charging session. (Rel-19, V19.0.0) | tf | Context: The Charging Data Request[Stop] is sent when the ProSe Function receives a Received Direct Communication Usage Report event and there is an open charging session. (Rel-19, V19.0.0)
Verdict: abstained
Boolean: null
Justification: The context provided does not contain enough information to determine whether th... | 0 | abstained | -1 | -1 | -1 | -1 | 0.632603 | 177 | 126 | 303 | api | null | null |
Anonymous Call Rejection barring program blocks all incoming calls when the calling line identification presentation is restricted according to CLIR, but allows calls when CLI presentation is not available or is restricted by the network. (Rel-19, V19.0.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is unclear what the specific conditions are for Anonymous Call Rejection barring program to block or allow incoming calls. Therefore, it is not possible to ma... | 0 | abstained | -1 | -1 | -1 | -1 | 0.369082 | 186 | 70 | 256 | api | null | null |
In the certificate-based case, subscription barring would be effective in preventing an attacker from using stolen RNs in their own network. (Rel-19, V19.2.0) | tf | Verdict: abstained
Boolean: null
Justification: The provided context does not contain enough information to determine whether the statement is true or false. It is unclear what "stolen RNs" refer to, and whether they can be used in the attacker's own network. Additionally, it is not specified how subscription barring ... | 0 | abstained | -1 | -1 | -1 | -1 | 0.489731 | 172 | 97 | 269 | api | null | null |
What does the S-CSCF do when filter criteria trigger points match the Service Point Triggers of a received request? (Rel-19, V19.0.0) | open | The S-CSCF (Serving-Call Session Control Function) is a core network element in the 3GPP IMS (IP Multimedia Subsystem) architecture. When filter criteria trigger points match the Service Point Triggers of a received request, the S-CSCF performs the following actions:
1. It checks if the request is a new one or a re-IN... | -1 | null | 0 | 0.607441 | 0 | 0.375011 | 1.304958 | 74 | 269 | 343 | api | null | null |
What is the maximum allowed delay for a UE to transmit a MeasurementReport message triggered by Event A3 during time period T2, and what happens if this requirement is not met? (Rel-19, V19.2.0) | open | According to 3GPP TS 36.331, the maximum allowed delay for a UE to transmit a MeasurementReport message triggered by Event A3 during time period T2 is 20 milliseconds. If this requirement is not met, the UE may not be able to maintain the required quality of service (QoS) for the connected services, leading to potentia... | -1 | null | 0 | 0.745806 | 0 | 0.375932 | 0.398362 | 86 | 79 | 165 | api | null | null |
What are the possible HTTP response codes and their associated data types for a PUT operation on the SMS registration resource? (Rel-19, V19.1.0) | open | The HTTP PUT operation on the SMS registration resource in 3GPP Rel-19 and V19.1.0 can return the following response codes and their associated data types:
1. 200 OK (application/json): The request has been successfully processed and the SMS registration resource has been updated.
2. 400 Bad Request (application/json... | -1 | null | 0 | 0.86606 | 0 | 0.389708 | 2.204188 | 72 | 519 | 591 | api | null | null |
What happens when timer F or timer F1 fires while a session is in the "trying" state, and what additional action does the SCC AS take if an unreliable transport-layer connection is used? (Rel-19, V19.0.0) | open | When timer F or timer F1 fires while a session is in the "trying" state, the SCC AS shall initiate the release of the session. This is done by sending a Release message to the remote party, which includes the cause code "normal call clearing" (25). The SCC AS shall then wait for the Release Complete message from the re... | -1 | null | 0 | 0.598609 | 0 | 0.575621 | 0.709558 | 89 | 148 | 237 | api | null | null |
How many faders are used in the system simulator setup described for the Target E-UTRAN and Target ≠ E-UTRAN configurations? (Rel-19, V19.1.0) | mc | The user is asking about the number of faders used in a system simulator setup for specific configurations (Target E-UTRAN and Target ≠ E-UTRAN) in 3GPP Release 19, Version 19.1.0.
1. **Analyze the question:** The key information needed is the count of faders (Fader 1, Fader 2, etc.) in the described system simulator... | 0 | incorrect | -1 | -1 | -1 | -1 | 14.249917 | 250 | 826 | 1,076 | api | null | null |
Which UE configuration parameters can be updated in an SNPN according to this specification release? (Rel-19, V19.2.0) | mc | The user wants to know which UE configuration parameters can be updated in an SNPN according to 3GPP Release 19, Version 19.2.0.
1. **Analyze the question:** The question asks for specific UE configuration parameters (Routing indicator, default configured NSSAI) and where they are stored (USIM, ME) that can be update... | 0 | incorrect | -1 | -1 | -1 | -1 | 12.925454 | 217 | 755 | 972 | api | null | null |
What does the SENSR KPI measure in IMS according to the specification? (Rel-19, V19.0.0) | mc | The user wants to know the definition of the SENSR KPI in IMS according to 3GPP Release 19, Version 19.0.0.
1. **Analyze the question:** The question asks for the specific measurement definition of SENSR (Session Establishment Success Rate) in the IMS domain.
2. **Recall/Search knowledge:** I need to access my inter... | 0 | incorrect | -1 | -1 | -1 | -1 | 10.604079 | 216 | 628 | 844 | api | null | null |
What action is taken when the reportType is set to reportCGI and the UE detects that the requested NR cell is not transmitting SIB1? (Rel-19, V19.2.0) | mc | In 3GPP Release 19 (V19.2.0), when the reportType is set to reportCGI and the UE detects that the requested NR cell is not transmitting SIB1, the UE stops timer T321 and includes a measurement reporting entry within the VarMeasReportList. This is because the absence of SIB1 means the UE cannot acquire the CGI, so it re... | 1 | correct | -1 | -1 | -1 | -1 | 6.39831 | 234 | 388 | 622 | api | null | null |
In UM mode, when specific conditions are met including uplink transmission and RLC SDU beginning at the start of RLC PDU, what Length Indicator value should be used for 7-bit Length Indicators? (Rel-19, V19.0.0) | mc | In RLC UM mode, the Length Indicator (LI) field in the RLC PDU header indicates the length of the RLC SDU or segment. For 7-bit Length Indicators, the value 111 1111 (binary) is reserved to indicate that the RLC SDU begins at the start of the RLC PDU and extends to the end of the PDU, or to signal specific conditions l... | 0 | incorrect | -1 | -1 | -1 | -1 | 6.273699 | 231 | 382 | 613 | api | null | null |
When must a GPRS MS in operation mode A use the normal GPRS attach procedure instead of the combined GPRS attach procedure? (Rel-19, V19.2.0) | mc | The user wants to know when a GPRS MS in operation mode A must use the normal GPRS attach procedure instead of the combined GPRS attach procedure, based on 3GPP Release 19, Version 19.2.0.
1. **Analyze the question:** The key terms are "GPRS MS", "operation mode A", "normal GPRS attach procedure", "combined GPRS atta... | 0 | incorrect | -1 | -1 | -1 | -1 | 11.154552 | 210 | 656 | 866 | api | null | null |
What happens when the HSS sends InsertSubscriberData messages despite a "skip subscriber data" indication being present? (Rel-19, V19.0.0) | mc | The user is asking about the behavior of an IWF (Interworking Function) when the HSS sends InsertSubscriberData messages despite a "skip subscriber data" indication being present, specifically in the context of 3GPP Release 19.
1. **Analyze the question:** The core issue is how the IWF handles subscriber data updates... | 0 | incorrect | -1 | -1 | -1 | -1 | 10.046489 | 230 | 596 | 826 | api | null | null |
In the SlicePpData schema, what serves as the key in the sliceUsgCtrlData map? (Rel-19, V19.2.0) | mc | The user is asking about the SlicePpData schema in 3GPP Release 19, specifically what serves as the key in the sliceUsgCtrlData map.
1. **Analyze the question:** The question asks for the key of the `sliceUsgCtrlData` map within the `SlicePpData` schema.
2. **Recall/Search knowledge:** I need to access my knowledge ... | 0 | incorrect | -1 | -1 | -1 | -1 | 8.537043 | 225 | 514 | 739 | api | null | null |
In the ServiceNameDescription schema, what is the requirement for the "language" field and the service content fields? (Rel-19, V19.1.0) | mc | The user is asking about the "ServiceNameDescription" schema in 3GPP Release 19, specifically regarding the "language" field and service content fields.
1. **Identify the relevant specification**: This question pertains to 3GPP Release 19, likely within the context of service descriptions or network slicing, possibly... | 0 | incorrect | -1 | -1 | -1 | -1 | 9.951456 | 232 | 592 | 824 | api | null | null |
According to the call flow diagram, what happens after the "ICA Default Call Handling" decision is made and processed? (Rel-19, V19.0.0) | mc | The user wants to know the next step after "ICA Default Call Handling" in a specific call flow diagram (Rel-19, V19.0.0).
1. **Analyze the question:** The question asks for the sequence of events following a specific decision point ("ICA Default Call Handling") in a call flow.
2. **Recall/Search knowledge:** I need ... | 0 | incorrect | -1 | -1 | -1 | -1 | 10.5823 | 224 | 626 | 850 | api | null | null |
What must occur before a UE can transmit using Type 1 channel access procedure? (Rel-19, V19.0.0) | mc | The user wants to know the condition for a UE to transmit using Type 1 channel access procedure in 3GPP Release 19.
1. **Analyze the question:** The question asks for the prerequisite condition for a UE transmission using Type 1 channel access.
2. **Recall 3GPP knowledge:** Type 1 channel access is a LBT (Listen Bef... | 0 | incorrect | -1 | -1 | -1 | -1 | 8.838126 | 240 | 528 | 768 | api | null | null |
When determining the BWP switching delay T_BWPswitchDelay for multiple CCs where the BWP switch results in SCS change on any involved CC, which SCS should be used as the basis? (Rel-19, V19.0.0) | mc | In 3GPP Release 19, when determining the BWP switching delay (T_BWPswitchDelay) for multiple component carriers (CCs) where the BWP switch results in a subcarrier spacing (SCS) change on any involved CC, the specification defines that the delay is based on the largest SCS among all SCS values of all involved CCs. This ... | 0 | incorrect | -1 | -1 | -1 | -1 | 7.623121 | 251 | 460 | 711 | api | null | null |
When a UP function sends additional PFCP Session Report Request messages following a PFCP Session Modification Response, how should the AURI flag be set? (Rel-19, V19.1.0) | mc | The user wants to know how the AURI flag should be set when a UP function sends additional PFCP Session Report Request messages after a PFCP Session Modification Response, according to 3GPP Release 19, Version 19.1.0.
1. **Analyze the question:** The scenario involves a UP function sending multiple PFCP Session Repor... | 0 | incorrect | -1 | -1 | -1 | -1 | 13.539355 | 273 | 788 | 1,061 | api | null | null |
When the IP-SM-GW receives an MO_FORWARD_SHORT_MESSAGE_ACK with SMS-SUBMIT-REPORT and specific conditions are met, what action shall it take? (Rel-19, V19.0.0) | mc | The user wants to know the action taken by the IP-SM-GW when it receives an MO_FORWARD_SHORT_MESSAGE_ACK with SMS-SUBMIT-REPORT under specific conditions in Rel-19.
1. **Analyze the question:** The key elements are "IP-SM-GW", "MO_FORWARD_SHORT_MESSAGE_ACK", "SMS-SUBMIT-REPORT", "specific conditions", and "action".
2... | 0 | incorrect | -1 | -1 | -1 | -1 | 10.972335 | 241 | 646 | 887 | api | null | null |
When a subscriber registers on a VLR, what information about the Call Deflection service must the HLR send to the VLR? (Rel-19, V19.0.0) | mc | The user wants to know what information the HLR sends to the VLR regarding the Call Deflection service when a subscriber registers.
1. **Analyze the question:** The question asks for specific data elements related to Call Deflection service that are transmitted from HLR to VLR during registration.
2. **Recall releva... | 0 | incorrect | -1 | -1 | -1 | -1 | 8.642042 | 266 | 518 | 784 | api | null | null |
According to the MacAddr48Rm specification, how are features numbered and represented in the hexadecimal string? (Rel-19, V19.2.0) | mc | The user wants to know how features are numbered and represented in the hexadecimal string according to the MacAddr48Rm specification in 3GPP Rel-19, V19.2.0.
1. **Analyze the question:** The key terms are "MacAddr48Rm", "features numbered", "hexadecimal string", "Rel-19, V19.2.0".
2. **Recall/Search knowledge:** I ... | 0 | incorrect | -1 | -1 | -1 | -1 | 12.750664 | 277 | 746 | 1,023 | api | null | null |
End of preview.
thesis-results
Weighted single-number scores for my MSc thesis (GSMA Open Telco AI Initiative) — the same weighting scheme used on the earlier 40 mc / 40 tf / 4 open evaluation set, applied to the current targeted-evaluation results:
weighted_score_pct = (1*mc_correct + 1*tf_correct + 5*oe_correct)
/ (1*mc_total + 1*tf_total + 5*oe_total)
* 100
Open-ended questions count 5x an mc/tf question, since they test generation quality more strongly
than exact-match. This isn't a new formula computed for this repo — it's
CorpusResult.weighted_score_pct, already computed server-side for every real evaluation run (see
open_telco_rag/evaluation/results.py's _weighted_score_pct() in the telcolens repo); this
repo just extracts and ranks it.
Built by telcolens/liam/analysis_tools/compute_weighted_scores.py, which reads (never writes)
from LiamDuero/telco-eval via
build_telco_analysis_repo.py's pull_all_results(). Same 6-model scope as
telco-analysis (that repo holds the
full unweighted metric set; this one is just the single ranked score).
Files
Two scorings, kept as separate file pairs so they're never confused for each other:
weighted_scores.json/weighted_scores_best_per_model.json— scored against the full 105-question set (55 mc / 40 tf / 10 open). Built bycompute_weighted_scores.py.weighted_scores_84from105.json/weighted_scores_84from105_best_per_model.json— scored against an 84-question subset of the 105 set (40 mc / 40 tf / 4 open, difficulty-first- series-stratified — see
telco-qna-generation/liam/sample_eval_set_84_from_105.py), matching the SHAPE of the earlierfinal_3gpp_small.jsonset (same 40/40/4 split) without being the same 84 questions (confirmed live: only 76/84 offinal_3gpp_small.json's questions, and 0 of its 4 open ones, actually appear in the 105 set — it was an independent draw, not chained off the small set). Built byrecompute_84_from_105_scores.py, which does not re-run any evaluation — every one of these 84 questions was already asked and scored as part of the 105-question runs, so this just filters each combo's existing per-question results down to the 84-question subset and re-aggregates via the realaggregate()/weighted_score_pctlogic. No additional API/GPU cost.
- series-stratified — see
Each row: model_id, model_display_name, phase (grid/no_reranker/baseline),
reranker_label, run_name, weighted_score_pct, n_questions, mean_accuracy, total_cost.
final_3gpp_84from105.json— the actual 84 questions the*_84from105scores above were computed against (same file asLiamDuero/telco-qna-final/final_3gpp_84from105.json, copied here too so the questions live alongside their own scores, not just in the question-bank repo).
Scope
Models: Gemma, TelecomGPT-R1, and 4 OpenRouter models (DeepSeek V4 Pro 0813, GLM 5.3, Qwen3.8 27B,
Mistral Small 4) — otel-2.0-local excluded (confirmed broken, degenerate output). Some runs are
still missing (a few OpenRouter no-reranker legs, Gemma's baseline against the 105 set) — both file
pairs only ever contain what's real and pushed; re-run the relevant script to refresh once more land.
- Downloads last month
- 184