LOGGING SYSTEM INFORMATION REQUEST PROCEDURE RELATED INFORMATION AND MEASUREMENTS Related Applications This application claims the benefit of provisional patent application serial number 63/143,249, filed January 29, 2021, the disclosure of which is hereby incorporated herein by reference in its entirety. Technical Field The present disclosure relates to system information requests in a cellular communications system and, more specifically, logging of information and/or measurements related to system information requests. Background Third Generation Partnership Project (3GPP) Technical Specification (TS) 32.422 V16.3.0, Section 4.8 describes Radio Resource Control (RRC) Connection Establishment Failure (RCEF) reporting to the Trace Collection Entity (TCE). An excerpt from a relevant subsection of Section 4.8 of 3GPP TS 32.422 is provided below. ********** Start Excerpt from 3GPP TS 32.422 V16.3.0 ********** 4.8.1 Trace session activation for RCEF reporting in E-UTRAN RCEF reporting is activated to the eNB as a special Trace Session where the job type indicates RCEF reporting only. The detailed procedure is shown in figure 4.8.1.1 where a UE experiences an RCEF event and the RRC establishment is successful to the same eNB. [REPRODUCED HEREIN AS FIGURE 1] Figure 4.8.1.1 Example scenario for RCEF reporting when UE RRC establishment is successful to the same eNB. When the eNB receives the Trace Session activation indicating RCEF reporting only, the eNB shall start a Trace Session. This Trace Session shall collect only RCEF reports received from the UE. The Trace Session activation message received from the EMS shall contain the following information: - Trace Reference - Job type=RCEF reporting only - IP address of the TCE Figure 4.8.1.2 shows another example where the UE RRC Establishment is failed to one eNB, but successful to another eNB. [REPRODUCED HEREIN AS FIGURE 2] Figure 4.8.1.2 Example scenario for RCEF reporting when the UE RRC establishment is successful to a different eNB If the UE establishes the RRC connection successfully the RCEF reports are fetched by the eNB. The procedures to be used at eNB to forward the RCEF reports towards the management system are the same regardless of whether RCEF occurred at this eNB or a different eNB. If a UE detects a RRC Connection Establishment Failure event, it collects certain information as described in TS 37.320[30]. Once the eNB retrieved the RCEF report from the UE, as defined in TS 37.320[30], it shall save it to the Trace Record. The Trace Record containing the RCEF reports can be transferred to the TCE in the same mechanism as for normal subscriber and equipment trace or for MDT. ********** End Excerpt from 3GPP TS 32.422 V16.3.0 ********** In regard to connection establishment failure reporting in the RRC specification, upon failure in RRC establishment or RRC resume procedure, a UE starts logging the connection establishment failure report. The procedural text concerning the connection establishment failure is shown in the following excerpt from 3GPP TS 38.331 V16.3.0. ********** Start Excerpt from 3GPP TS 38.331 V16.3.0 ********** 5.3.3.7 T300 expiry The UE shall: 1> if timer T300 expires: 2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established; 2> if the UE supports RRC Connection Establishment failure with temporary offset and the T300 has expired a consecutive connEstFailCount times on the same cell for which connEstFailureControl is included in SIB1: 3> for a period as indicated by connEstFailOffsetValidity: 4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell selection and reselection according to TS 38.304 [20] and TS 36.304 [27]; NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during connEstFailOffsetValidity for the concerned cell. 2> if the UE has connection establishment failure informaton or connection resume failure information available in VarConnEstFailReport and if the RPLMN is not equal to plmn-identity stored in VarConnEstFailReport; or 2> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport: 3> reset the numberOfConnFail to 0; 2> clear the content included in VarConnEstFailReport except for the numberOfConnFail, if any; 2> store the following connection establishment failure information in the VarConnEstFailReport by setting its fields as follows: 3> set the plmn-Identity to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1; 3> set the measResultFailedCell to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection establishment failure; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re- selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: 4> for each neighbour cell included, include the optional fields that are available; NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. 3> if available, set the locationInfo as follows: 4> if available, set the commonLocationInfo to include the detailed location information; 4> if available, set the bt-LocationInfo to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons; 4> if available, set the wlan-LocationInfo to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs; 4> if available, set the sensor-LocationInfo to include the sensor measurement results as follows; 5> if available, include the sensor-MeasurementInformation; 5> if available, include the sensor-MotionInformation; 3> set perRAInfoList to indicate random access failure information as specified in 5.7.10.5; 3> if the numberOfConnFail is smaller than 8: 4> increment the numberOfConnFail by 1; 2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends; The UE may discard the connection establishment failure or connection resume failure information, i.e. release the UE variable VarConnEstFailReport, 48 hours after the last connection establishment failure is detected. ********** End Excerpt from 3GPP TS 38.331 V16.3.0 ********** The content of the connection failure establishment report is specified in section 6.2.2. in 3GPP TS 38.331. On demand system acquisition is specified as part of the 3GPP TS 38.331. System Information Blocks (SIBs) can be broadcasted or not broadcasted. In case they are broadcasted, si-BroadcastStatus will be set to broadcasting, and the periodicity of the broadcasted SIB is provided as part of si-BroadcastStatus. If the system information is not broadcasted, there are two methods for the UE to request the system information of interest during random access. These two methods are: MSG1 based system information request, and MSG3 based system information request. For the MSG1 based system information request, the si-BroadcastStatus for a SIB type that is not broadcasted will be set to notbroadcasting. If the UE is interested to read at least one SIB of this SIB type, the UE follows the si-RequestConfig to determine what Random Access Channel (RACH) resources should be used to request that the network broadcast the desired SIB. The use of these RACH resources for MSG1 transmission serves as an on-demand request for the desired system information. However, the si-RequestConfig is an optional field and exists if the RACH resources are configured for the on-demand system information request from the UE. If the si- RequestConfig does not exist or if RACH resources are not configured for the on- demand SI request, then the UE initiates the RRCSystemInfoRequest (MSG3 based approach) to request the system information of interest from the network. The aforementioned two approaches (MSG1 and MSG3 based on-demand SI request) are shown in the following excerpts from 3GPP TS 38.331. ********** Start Excerpts from 3GPP TS 38.331 V16.3.0 ********** SI-SchedulingInfo ::= SEQUENCE { schedulingInfoList SEQUENCE (SIZE (1..maxSI- Message)) OF SchedulingInfo, si-WindowLength ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280}, si-RequestConfig SI-RequestConfig OPTIONAL, -- Cond MSG-1 si-RequestConfigSUL SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 systemInformationAreaID BIT STRING (SIZE (24)) OPTIONAL, -- Need R ... } SchedulingInfo ::= SEQUENCE { si-BroadcastStatus ENUMERATED {broadcasting, notBroadcasting}, si-Periodicity ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, sib-MappingInfo SIB-Mapping } SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-TypeInfo ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare3, spare2, spare1,... }, valueTag INTEGER (0..31) OPTIONAL, -- Cond SIB-TYPE areaScope ENUMERATED {true} OPTIONAL -- Need S } SI-RequestConfig information element -- ASN1START -- TAG–SI-REQUESTCONFIG-START SI-RequestConfig::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need R si-RequestResources SEQUENCE (SIZE (1..maxSI- Message)) OF SI-RequestResources } SI-RequestResources ::= SEQUENCE { ra-PreambleStartIndex INTEGER (0..63), ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, -- Need R ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL -- Need R } 5.2.2.3.3 Request for on demand system information The UE shall: 1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the random access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> initiate transmission of the RRCSystemInfoRequest message in accordance with 5.2.2.3.4; 2> if acknowledgement for RRCSystemInfoRequest message is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: 2> reset MAC; 2> if SI request is based on RRCSystemInfoRequest message: 3> release RLC entity for SRB0. NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. ********** End Excerpts from 3GPP TS 38.331 V16.3.0 ********** In both methods for requesting on-demand system information, a RACH procedure is initiated (either based on the configuration provided in the MSG1 based solution or a contention-based method for the MSG3 based solution). If the random access procedure is successful, an ra-Report will be logged by the UE which indicates the random access procedure performance. The content of the ra-Report is shown in the following excerpt of the 3GPP TS 38.331. However, if the UE fails in the random access procedure for requesting the system information, there is no action on the UE to log the failed random access related information. ********** Start Excerpt from 3GPP TS 38.331 V16.3.0 ********** RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA- Report-r16 RA-Report-r16 ::= SEQUENCE { cellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging- r16, pci-arfcn-r16 SEQUENCE { physCellId-r16 PhysCellId, carrierFreq-r16 ARFCN-ValueNR } }, ra-InformationCommon-r16 RA-InformationCommon- r16, raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } RA-InformationCommon-r16 ::= SEQUENCE { absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16 } ********** End Excerpt from 3GPP TS 38.331 V16.3.0 ********** Summary Systems and methods related to logging system information request procedure related information and/or measurements are disclosed. In one embodiment, a method performed by a wireless communication device comprises sending a request for system information to a network node and, regardless of whether the request for system information succeeds or fails, logging information and/or measurements related to the request for system information. The method further comprises reporting the logged information and/or measurements to a network node. In this manner, information and/or measurements related to system information requests is reported by the network and can be used by the network, e.g., for Random Access Channel (RACH) optimization and/or coverage optimization. In one embodiment, sending the request for system information comprises sending the request for system information via a message sent during a random access procedure. In one embodiment, the message is MSG1 or MSG3. In one embodiment, the logged information and/or measurements comprises a list of system information types that are requested by the wireless communication device. In one embodiment, the logged information and/or measurements comprises a list of system information types that are wanted by the wireless communication device. In one embodiment, the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device, (b) a list of system information types that are wanted by the wireless communication device, (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information about random access resources configured for the random access procedure in which the request for system information was sent, (e) information that indicates whether the request for system information was sent via MSG1 or MSG3 in the random access procedure, (f) information that indicates that a purpose of the random access procedure was to make the request for system information, or (g) any combination of two or more of (a)-(f). In one embodiment, the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device, (b) a list of system information types that are wanted by the wireless communication device, (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information comprised in a system information request configuration, (e) preamble group index or identity that is used to perform the random access procedure in which the request for system information was sent, (f) frequency related information about random access resources used for the random access procedure in which the request for system information was sent, (g) a cell identity of a cell in which the random access procedure was performed, (h) information related to random access attempts performed per each selected beam, or (i) any combination of two or more of (a)-(h). In one embodiment, the logged information and/or measurements comprises the information comprised in the system information request configuration, and the information comprised in the system information request configuration comprises: (i) ssb-perRACH-Occasion; (ii) si-RequestPeriod; (iii) si-RequestResources; (iv) SI- RequestResources including (a) ra-PreambleStartIndex, (b) ra-AssociationPeriodIndex, and/or (c) ra-ssb-OccasionMaskIndex; or (v) a combination of any two or more of (i) to (iv). In one embodiment, the request for system information succeeds. In one embodiment, reporting the logged information and/or measurements to the network node comprises reporting the logged information and/or measurements to the network node via a random access report. In one embodiment, the request for system information fails. In one embodiment, reporting the logged information and/or measurements to the network node comprises reporting the logged information and/or measurements to the network node via a connection establishment failure report. In one embodiment, reporting the logged information and/or measurements to the network node comprises reporting the logged information and/or measurements to the network node via a dedicated report. Corresponding embodiments of a wireless communication device are also disclosed. In one embodiment, a wireless communication device is adapted to send a request for system information to a network node and, regardless of whether the request for system information succeeds or fails, log information and/or measurements related to the request for system information. The wireless communication device is further adapted to report the logged information and/or measurements to a network node. In one embodiment, a wireless communication device comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers. The processing circuitry is configured to cause the wireless communication device to send a request for system information to a network node and, regardless of whether the request for system information succeeds or fails, log information and/or measurements related to the request for system information. The processing circuitry is further configured to cause the wireless communication device to report the logged information and/or measurements to a network node. Embodiments of a method performed by a base station are also disclosed. In one embodiment, a method performed by a base station comprises receiving a report comprising logged information and/or measurements from a wireless communication device, the logged information and/or measurements comprising information and/or measurements related to a request for system information sent by the wireless communication device regardless of whether the request for system information succeed or failed. The method further comprises using the logged information and/or measurements. In one embodiment, the logged information and/or measurements comprises a list of system information types that are requested by the wireless communication device. In one embodiment, the logged information and/or measurements comprises a list of system information types that are wanted by the wireless communication device. In one embodiment, the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device, (b) a list of system information types that are wanted by the wireless communication device, (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information about random access resources configured for the random access procedure in which the request for system information was sent, (e) information that indicates whether the request for system information was sent via MSG1 or MSG3 in the random access procedure, (f) information that indicates that a purpose of the random access procedure was to make the request for system information, or (g) any combination of two or more of (a)-(f). In one embodiment, the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device, (b) a list of system information types that are wanted by the wireless communication device, (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information comprised in a system information request configuration, (e) preamble group index or identity that is used to perform the random access procedure in which the request for system information was sent, (f) frequency related information about random access resources used for the random access procedure in which the request for system information was sent, (g) a cell identity of a cell in which the random access procedure was performed, (h) information related to random access attempts performed per each selected beam, or (i) any combination of two or more of (a)-(h). In one embodiment, the logged information and/or measurements comprises the information comprised in the system information request configuration, and the information comprised in the system information request configuration comprises: (i) ssb-perRACH-Occasion; (ii) si-RequestPeriod; (iii) si-RequestResources; (iv) SI- RequestResources including (a) ra-PreambleStartIndex, (b) ra-AssociationPeriodIndex, and/or (c) ra-ssb-OccasionMaskIndex; or (v) a combination of any two or more of (i) to (iv). In one embodiment, the request for system information succeeds. In one embodiment, the received report is a random access report. In one embodiment, the request for system information fails. In one embodiment, the received report is a connection establishment failure report. In one embodiment, the received report is a dedicated report. Corresponding embodiments of a base station are also disclosed. In one embodiment, a base station is adapted to receive a report comprising logged information and/or measurements from a wireless communication device, the logged information and/or measurements comprising information and/or measurements related to a request for system information sent by the wireless communication device regardless of whether the request for system information succeed or failed. The base station is further adapted to use the logged information and/or measurements. In one embodiment, a base station comprises processing circuitry configured to cause the base station to receive a report comprising logged information and/or measurements from a wireless communication device, the logged information and/or measurements comprising information and/or measurements related to a request for system information sent by the wireless communication device regardless of whether the request for system information succeed or failed. The processing circuitry is further configured to cause the base station to use the logged information and/or measurements. Brief Description of the Drawings The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. Figure 1 is a reproduction of Figure 4.8.1.1 of Third Generation Partnership Project (3GPP) Technical Specification (TS) 32.422 V16.3.0; Figure 2 is a reproduction of Figure 4.8.1.2 of 3GPP TS 32.422 V16.3.0; Figure 3 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented; Figure 4 illustrates the operation of a User Equipment (UE) to log and report information related to a UE requested system information procedure and measurements in accordance with an embodiment of the present disclosure; Figures 5, 6, and 7 are schematic block diagrams of a radio access node (e.g., a base station or a network node that implements part of the functionality of a base station) in accordance with embodiments of the present disclosure; Figures 8 and 9 are schematic block diagrams of a wireless communication device (e.g., a UE) in accordance with embodiment of the present disclosure; Figure 10 illustrates an example embodiment of a communication system in which embodiments of the present disclosure may be implemented; Figure 11 illustrates example embodiments of the host computer, base station, and UE of Figure 10; Figures 12, 13, 14, and 15 are flow charts that illustrate example embodiments of methods implemented in a communication system such as that of Figure 10. Detailed Description The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description. Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device. Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node. Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like. Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle- mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection. Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection. Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system. In the following description, the terms “request for on demand system information” and “request for system information” and “SI request” are used interchangeably. Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams. There currently exist certain challenge(s). According to the current version of 3GPP Technical Specification (TS) 38.331, the UE that triggers the request for the on- demand system information is not able to log the information and measurements pertained to the performed procedure if the request for system information procedure fails. In addition, no matter whether the request for system information procedure fails or is successful, currently it is not possible for the network to detect what type of system information is requested and or wanted by the UE from the logged random- access related report pertaining to the random-access procedure triggered by the request for system information procedure. In addition, the network cannot determine from the current random access report whether the random access procedure was trigged with configured random access resources (i.e., the request for system information procedure was based on MSG1) or not (i.e., the request for system information procedure was based on MSG3). Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Embodiments of the systems and methods disclosed herein provide a solution in which the UE logs and reports the measurement and information related to a UE request for system information (SI request). In one embodiment, a method for UE logging and reporting of measurements and information related to a UE request for system information comprises at least one of the following actions upon failure of a request for system information (SI request): 1. Logging a list of system information type(s) that is(are) requested by the UE a. In one embodiment, this information can be mapped to at least one of the system information types included in SIB-TypeInfo Information Element (IE) or requested-SI-List IE as defined in 3GPP TS 38.311. 2. Logging a list of system information type(s) that are wanted by the UE a. In one embodiment, this information can be mapped to at least one of the system information types included in SIB-TypeInfo IE or requested-SI- List IE as defined in 3GPP TS 38.331; however, the values (indicated system information types by UE) may be more compared to the requested one in this attempt. 3. Logging the preamble indexes as well as random access resources configured for the random access procedure triggered for requesting system information. 4. Logging if the random-access procedure triggered for requesting system information was based on the MSG1 procedure (i.e., whether the MSG1 resources were already configured) or based on the MSG3 procedure (i.e., whether request is initiated by RRCSystemInfoRequest according to the 3GPP TS 38.331. 5. Logging the purpose of the random-access procedure for the random- access procedure triggered for the request for system information. a. In one embodiment, in 3GPP TS 38.331, this information can be mapped to ra-purpose IE. i. In this method, the purpose of the random-access procedure will be the request for other SI. 6. Logging the performed random access related information and measurements, for the random-access procedure triggered for the request for system information. a. In one embodiment, this information comprises at least the information included in the connection establishment failure report (e.g., connEstFailReport-16) as defined in 3GPP TS 38.331. In one embodiment, the method also comprises at least one of the following actions upon successful request for system information request (SI request): 1. Logging a list of system information type(s) that is(are) requested by the UE. a. In one embodiment, this information can be mapped to at least one of the system information types included in SIB-TypeInfo IE or requested-SI- List IE as defined in 3GPP TS 38.331. 2. Logging a list of system information types that are wanted by the UE a. In one embodiment, this information can be mapped to at least one of the system information types included in SIB-TypeInfo IE as defined in 3GPP TS 38.331; however, the values (indicated system information types by UE) may be more compared to the requested one in this attempt. 3. Logging the preamble indexes as well as random access resources configured for the random access procedure triggered for requesting system information. 4. Logging if the random-access procedure triggered for request for system information was based on the MSG1 procedure (i.e., whether the MSG1 resources were already configured) or based on the MSG3 procedure (i.e., whether request is initiated by RRCSystemInfoRequest according to the 3GPP TS 38.331. 5. Logging the purpose of the random-access procedure triggered for the request for system information. a. In one embodiment, this information can be mapped to ra-purpose IE as defined in 3GPP TS 38.331. i. In this method, the purpose of the random-access procedure will be the request for other SI 6. Logging the performed random access related information and measurements, for the random-access procedure triggered for the request for system information. a. In one embodiment, this information comprises at least the information included in the random-access report (e.g., ra-Report-16) as defined in 3GPP TS 38.331. Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solution disclosed herein may allow the UE to log and report the measurement and information related to the request for system information and its pertained random access procedure (if the random access procedure is failed). Currently the information related to the request for system information procedure, including the random access related information (when it fails), the requested system information type and whether the request was based on MSG1 or MSG3 are not logged and reported by the UE. The logged information disclosed herein can be used by the network nodes (or operation and management system) for Random Access Channel (RACH) optimization as well as coverage optimization. In addition, logging the system information type that is requested by the UE can be used by the network to optimize broadcasting the system information based on the frequency of the reports. In addition, UE can log the system information that is wanted beside the system information that is requested. Note that UE may require multiple random access procedures to acquire all the wanted SIBs. Namely, it may not be possible to acquire all the wanted system information via one random access procedure. Including the system information types that are wanted by UE (i.e., not only the system information that are requested but also those that are wanted but not yet requested) could help the RAN nodes and operation and management system to optimize the allocation of the preambles and RACH resources to different system information types. Figure 3 illustrates one example of a cellular communications system 300 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 300 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC) or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC); however, the embodiments disclosed herein are not limited thereto. In this example, the RAN includes base stations 302-1 and 302-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC) and in the EPS include eNBs, controlling corresponding (macro) cells 304-1 and 304-2. The base stations 302-1 and 302-2 are generally referred to herein collectively as base stations 302 and individually as base station 302. Likewise, the (macro) cells 304-1 and 304-2 are generally referred to herein collectively as (macro) cells 304 and individually as (macro) cell 304. The RAN may also include a number of low power nodes 306-1 through 306-4 controlling corresponding small cells 308-1 through 308-4. The low power nodes 306-1 through 306-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 308-1 through 308-4 may alternatively be provided by the base stations 302. The low power nodes 306-1 through 306-4 are generally referred to herein collectively as low power nodes 306 and individually as low power node 306. Likewise, the small cells 308- 1 through 308-4 are generally referred to herein collectively as small cells 308 and individually as small cell 308. The cellular communications system 300 also includes a core network 310, which in the 5G System (5GS) is referred to as the 5GC. The base stations 302 (and optionally the low power nodes 306) are connected to the core network 310. The base stations 302 and the low power nodes 306 provide service to wireless communication devices 312-1 through 312-5 in the corresponding cells 304 and 308. The wireless communication devices 312-1 through 312-5 are generally referred to herein collectively as wireless communication devices 312 and individually as wireless communication device 312. In the following description, the wireless communication devices 312 are oftentimes UEs and as such oftentimes referred to as UEs 312, but the present disclosure is not limited thereto. Embodiments of the present disclosure provide logging measurements and information for a UE request for system information and transmitting this logged information to the network. The logged information comprises, in one embodiment, the requested or wanted system information type(s), information about whether the UE request for system information was based on a MSG1 or MSG3, as well as the failed random-access procedure information and measurements for the random-access procedure triggered for the UE request for system information as part of the logged information in an existing or a dedicated report. The logged information comprises one or more of the following: • A list of requested system information types that are requested by the UE 312. In other words, the logged information includes information that indicates one or more system information types that are requested by the UE 312. In one embodiment, the one or more system information types requested by the UE 312 are one or more of the following system information types (according to the 3GPP TS 38.331): SIB-TypeInfo ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare3, spare2, spare1,... }, o In an example variant, the UE 312 logs the requested-SI-List according to the 3GPP TS 38.331. • A list of wanted system information types. In other words, the logged information includes information that indicates the system information types that the UE 312 requested and those wanted, but not requested, in this attempt. In one embodiment, the information types requested and the information types wanted, but not requested, are from among the following system information types (according to the 3GPP TS 38.331): SIB-TypeInfo ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare3, spare2, spare1,... }, o In an example variant, the UE 312 logs the requested-SI-List according to the 3GPP TS 38.331. • Preamble index that is configured and used as part of random-access procedure triggered to send the request for system information. o In one embodiment, if the preamble index is not already configured for the purpose of requesting system information, the selected preambles as part of the random-access procedure are logged. • Information included in SI request configuration (e.g., si-RequestConfig in 3GPP TS 38.331) for normal uplink or a supplementary uplink. The information may include at least one of the following items: o ssb-perRACH-Occasion o si-RequestPeriod o si-RequestResources o SI-RequestResources including: ■ ra-PreambleStartIndex ■ ra-AssociationPeriodIndex ■ ra-ssb-OccasionMaskIndex • Preamble group index (or ID) that is used to perform random access procedure for the request for system information. • Frequency related information of the random access resources used for performing the request for system information from the UE 312 o Some frequency related information logged by the UE 312 includes at least one of the following: ■ absoluteFrequencyPointA-r16 ■ locationAndBandwidth-r16 ■ subcarrierSpacing-r16 ■ msg1-FrequencyStart-r16 ■ msg1-FrequencyStartCFRA-r16 ■ msg1-SubcarrierSpacing-r16 ■ msg1-SubcarrierSpacingCFRA-r16 ■ msg1-FDM-r16 ■ msg1-FDMCFRA-r16 • Cell identity of the cell in which the random access procedure is performed. Cell ID may include at least one of the following: o global cell identity, o cell physical identity o carrier frequency, o any combination of the above information • Information related to the random-access attempts performed per each selected beam. This information may include at least one of the following: o beam index; beam can be an SSB beam or a CSI-RS beam o number of random-access attempts per beam o link quality measurements, in terms of RSRP, RSRQ, SINR, etc. or an indication if the link quality is above or below a certain threshold. o A flag indicating if any random-access contention is detected or not The above-mentioned information is logged by the UE 312 upon a successful or a failed UE request for system information. In other words, no matter if the UE 312 request for system information was failed or successful, the above-mentioned information will be logged. • In one embodiment, if the UE request for system information is successful, the UE 312 logs the above-mentioned information as part of a RACH report (e.g., as part of the so-called ra-Report in 3GPP TS 38.331). o In a sub-embodiment, if UE request for system information is successful, the UE 312 logs the above-mentioned information as part of a dedicated report for logging the request for system information. The report can be different from ra-Report or a ConEstFailureReport. • In another embodiment, if the UE request for system information is failed, the UE 312 logs the above-mentioned information as part of a connection establishment failure report (e.g., as part of the so-called ConEstFailureReport in 3GPP TS 38.331). o In a sub-embodiment, if the request for system information is failed, the UE 312 logs the above-mentioned information as part of a dedicated report for logging the information for the UE request for on system information. The report can be different from ra-Report or a ConEstFailureReport. Figure 4 illustrates the operation of a UE 312 to log and report information related to a UE requested system information procedure and measurements in accordance with an embodiment of the present disclosure. As illustrated, the UE 312 sends a request for system information (i.e., a SI request) (step 400). As described above, the request for system information is sent via a message (i.e., either MSG1 or MSG3) in a random access procedure. Regardless of whether the request for system information is successful or fails, the UE 312 logs information and/or measurements related to the request for system information as described above (step 402). The various types of information and/or measurements that can be logged in step 402 are described above. For example, the logged information and/or measurements include one or more of the following: (a) a list of system information types that are requested by the UE 312, (b) a list of system information types that are wanted by the UE 312, (c) the random access preamble index(es) configured for the random access procedure in which the request for system information was sent, (d) information about (e.g., information that indicates) random access resources configured for the random access procedure in which the request for system information was sent, (e) information that indicates whether the request for system information was sent via MSG1 or MSG3, (f) information that indicates that the purpose of the random access procedure was to make the request for system information, or (g) any combination of two or more of (a)- (f). The UE 312 reports the logged information and/or measurements to a network node, which in this example is the base station 302 (step 404). Note that the base station 302 may be the base station 302 that serves the cell on which the request for system information was sent in step 400 or a base station 302 that serves a different cell to which the UE 312 subsequently connects (via a successful random access), e.g., after a failed request for system information in step 400. As described above, if the request for system information in step 400 is successful, the logged information and/or measurements may be reported in a random access report (e.g., ra-Report-16) or a dedicated report. If the request for system information in step 402 failed, the logged information and/or measurements may be reported in a connection establishment failure report (e.g., connEstFailReport-16) or a dedicated report. In one embodiment, the report of the logged information is sent via a UE Information Request/Response procedure, where after the UE 312 performs a successful random access, the base station 302 sends a UE Information Request to the UE 312, and the UE 312 responds with a UE Information Response that includes a report including the logged information and/or measurements. The base station 302 or other network node may then utilize the logged information to perform one or more operational tasks, as described above (step 406). Example Implementation #1 In this section, a non-limiting example implementation is described that shows how the measurement and information related to a failed UE request for system information (including the system information type, random access purpose, and random access configuration) are logged as part of a connection establishment failure report. Note that here ConnEstFailureReport is used as an example and any dedicated report can be designed and used for reporting this information and measurement to the network. This example implantation is shown as a number of changes to 3GPP TS 38.331 V16.3.0. Corresponding text is shown in bold underlined text. ********** First Change to 3GPP TS 38.331 V16.3.0 ********** ConnEstFailReport-r16 ::= SEQUENCE { measResultFailedCell-r16 MeasResultFailedCell- r16, locationInfo-r16 LocationInfo-r16 OPTIONAL, measResultNeighCells-r16 SEQUENCE { measResultNeighCellListNR MeasResultList2NR- r16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL }, numberOfConnFail-r16 INTEGER (1..8), perRAInfoList-r16 PerRAInfoList- r16, timeSinceFailure-r16 TimeSinceFailure-r16, sIB-Mapping-r17 SIB-Mapping requested-SI-List-17 BIT STRING (SIZE (maxSI- Message)), raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} sI-RequestConfig-17 SI-RequestConfig SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-TypeInfo-17 ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14- v1610, spare3, spare2, spare1,... }, SI-RequestConfig::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, si-RequestResources SEQUENCE (SIZE (1..maxSI- Message)) OF SI-RequestResources } ********** Next Change to 3GPP TS 38.331 V16.3.0 ********** 5.3.3.7 T300 expiry The UE shall: 1> if timer T300 expires or if the random access procedure for UE request for system information failed: 2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established; 2> if the UE supports RRC Connection Establishment failure with temporary offset and the T300 has expired a consecutive connEstFailCount times on the same cell for which connEstFailureControl is included in SIB1: 3> for a period as indicated by connEstFailOffsetValidity: 4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell selection and reselection according to TS 38.304 [20] and TS 36.304 [27]; NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during connEstFailOffsetValidity for the concerned cell. 2> if the UE has connection establishment failure informaton or connection resume failure information available in VarConnEstFailReport and if the RPLMN is not equal to plmn- identity stored in VarConnEstFailReport; or 2> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport: 3> reset the numberOfConnFail to 0; 2> clear the content included in VarConnEstFailReport except for the numberOfConnFail, if any; 2> if the random access procedure for the request for system information procedure failed 3> set the requested-SI-List to indicate the system information (SI) message(s) that the UE requested to receive via request for on demand system information procedure; 3> store the system information type that UE requested as part of request for system information procedure in SIB-Mapping 3> store the preamble indexes of the preambles configured or used as part of random access procedure for the request for system information procedure 3> store the RACH resource configurations configured for the random access procedure for request for system information as part of SI-RequestConfig 3> set the ra-purpose to the requestForOtherSI 2> store the following connection establishment failure information in the VarConnEstFailReport by setting its fields as follows: 3> set the plmn-Identity to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1; 3> set the measResultFailedCell to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection establishment failure; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: 4> for each neighbour cell included, include the optional fields that are available; NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. 3> if available, set the locationInfo as follows: 4> if available, set the commonLocationInfo to include the detailed location information; 4> if available, set the bt-LocationInfo to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons; 4> if available, set the wlan-LocationInfo to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs; 4> if available, set the sensor-LocationInfo to include the sensor measurement results as follows; 5> if available, include the sensor-MeasurementInformation; 5> if available, include the sensor-MotionInformation; 3> set perRAInfoList to indicate random access failure information as specified in 5.7.10.5; 3> if the numberOfConnFail is smaller than 8: 4> increment the numberOfConnFail by 1; 2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends; The UE may discard the connection establishment failure or connection resume failure information, i.e. release the UE variable VarConnEstFailReport, 48 hours after the last connection establishment failure is detected. ********** Next Change to 3GPP TS 38.331 V16.3.0 ********** 5.2.2.3.3 Request for on demand system information The UE shall: 1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the random access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> initiate transmission of the RRCSystemInfoRequest message in accordance with 5.2.2.3.4; 2> if acknowledgement for RRCSystemInfoRequest message is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: 2> reset MAC; 2> if SI request is based on RRCSystemInfoRequest message: 3> release RLC entity for SRB0. 1> If the random access procedure triggered for request for on demand SI failed 2> Performs actions specified in 5.3.3.7 1> If the random access procedure trigged for the request for on demand SI is successful 2> Perform actions specified in 5.7.10.4 NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. ********** End Changes to 3GPP TS 38.331 V16.3.0 ********** Example Implementation #2 In a second non-limiting example implementation, the logging of the information related to UE request for system information (SI request) is implemented as part of a ra-Report as part of 3GPP TS 38.331. This example covers the cases when the random access procedure triggered for the UE request for system information was successful. This example implementation of an embodiment of the solution described herein is described below as changes to 3GPP TS 38.331 and includes the information related to the SI request procedure (e.g., the requested system information type) as part of the ra-Report. Corresponding text is shown as bold underlined text. ********** First Change to 3GPP TS 38.331 V16.3.0 ********** RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA- Report-r16 RA-Report-r16 ::= SEQUENCE { cellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging- r16, pci-arfcn-r16 SEQUENCE { physCellId-r16 PhysCellId, carrierFreq-r16 ARFCN-ValueNR } }, ra-InformationCommon-r16 RA-InformationCommon- r16, } RA-InformationCommon-r16 ::= SEQUENCE { absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16 } sIB-Mapping-r17 SIB-Mapping requested-SI-List-17 BIT STRING (SIZE (maxSI- Message)), raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} sI-RequestConfig-17 SI-RequestConfig SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-TypeInfo-17 ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14- v1610, spare3, spare2, spare1,... }, SI-RequestConfig::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, si-RequestResources SEQUENCE (SIZE (1..maxSI- Message)) OF SI-RequestResources } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfo-r16 ::= CHOICE { perRASSBInfoList-r16 PerRASSBInfo-r16, perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 } PerRASSBInfo-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 } PerRACSI-RSInfo-r16 ::= SEQUENCE { csi-RS-Index-r16 CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) } PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::= SEQUENCE { contentionDetected-r16 BOOLEAN OPTIONAL, dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, ... } ********** Next Change to 3GPP TS 38.331 V16.3.0 ********** 5.7.10.4 Actions upon successful completion of random-access procedure Upon successfully performing 4 step random access procedure, the UE shall: 1> if the number of RA-Report entries stored in the ra-ReportList in VarRA-Report is less than maxRAReport: 2> if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is less than maxPLMN; or 2> if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is equal to maxPLMN and the list of EPLMNs is subset of or equal to the plmn-IdentityList stored in VarRA-Report: 3> append the following contents associated to the successfully completed random- access procedure as a new entry in the VarRA-Report: 4> if the list of EPLMNs has been stored by the UE: 5> if the RPLMN is included in plmn-IdentityList stored in VarRA-Report: 6> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN) without exceeding the limit of maxPLMN; 5> else: 6> clear the information included in VarRA-Report; 6> set the plmn-IdentityList to the list of EPLMNs stored by the UE (i.e. includes the RPLMN); 4> else: 5> set the plmn-Identity, in plmn-IdentityList, to the PLMN selected by upper layers from the PLMN(s) included in the plmn-IdentityList in SIB1; 4> set the cellId to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; 4> if the successful random-access procedure is triggered for the request for system information procedure 5> set the requested-SI-List to indicate the system information (SI) message(s) that the UE requested to receive via request for on demand system information procedure; 5> store the system information type that UE requested as part of request for system information procedure in SIB-Mapping 5> store the preamble indexes of the preambles configured or used as part of random access procedure for the request for system information procedure 5> store the RACH resource configurations configured for the random access procedure for request for system information as part of SI-RequestConfig 4> set the raPurpose to include the purpose of triggering the random-access procedure; 4> set the ra-InformationCommon-r16 as specified in subclause 5.7.10.5. ********** End Changes to 3GPP TS 38.331 V16.3.0 ********** Example Implementation #3 In a third non-limiting example implementation, the logging of the information related to UE request for system information (SI request) in accordance with an embodiment of the present disclosure is implemented as part of a dedicated report as part of 3GPP TS 38.331. This method includes the information related to the SI request procedure (e.g., the requested system information type) as part of the ra-Report. Corresponding text is shown as bold underlined text in the following changes to 3GPP TS 38.331. ********** First Change to 3GPP TS 38.331 V16.3.0 ********** SI-Request-ReportList-r16 ::= SEQUENCE (SIZE (1..maxSIReport- r16)) OF SI-Request-Report-r16 SI-Request-Report-r16 ::= SEQUENCE { cellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging- r16, pci-arfcn-r16 SEQUENCE { physCellId-r16 PhysCellId, carrierFreq-r16 ARFCN-ValueNR } }, ra-InformationCommon-r16 RA-InformationCommon- r16, } RA-InformationCommon-r16 ::= SEQUENCE { absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16 } sIB-Mapping-r17 SIB-Mapping requested-SI-List-17 BIT STRING (SIZE (maxSI- Message)), raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} sI-RequestConfig-17 SI-RequestConfig SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-TypeInfo-17 ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14- v1610, spare3, spare2, spare1,... }, SI-RequestConfig::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, si-RequestResources SEQUENCE (SIZE (1..maxSI- Message)) OF SI-RequestResources } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfo-r16 ::= CHOICE { perRASSBInfoList-r16 PerRASSBInfo-r16, perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 } PerRASSBInfo-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 } PerRACSI-RSInfo-r16 ::= SEQUENCE { csi-RS-Index-r16 CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) } PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::= SEQUENCE { contentionDetected-r16 BOOLEAN OPTIONAL, dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, ... } ********** Next Change to 3GPP TS 38.331 V16.3.0 ********** 5.7.10.x Actions upon completion of UE request for on demand system information 1> if the number of SI-Request-Report entries stored in the SI-Request-ReportList in VarSI- Report is less than maxSIReport: 2> if the number of PLMN entries in plmn-IdentityList stored in VarSI-Report is less than maxPLMN; or 2> if the number of PLMN entries in plmn-IdentityList stored in VarSI-Report is equal to maxPLMN and the list of EPLMNs is subset of or equal to the plmn-IdentityList stored in VarSI-Report: 3> append the following contents associated to the successfully completed SI request procedure as a new entry in the VarSI-Report: 4> if the list of EPLMNs has been stored by the UE: 5> if the RPLMN is included in plmn-IdentityList stored in VarRA-Report: 6> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN) without exceeding the limit of maxPLMN; 5> else: 6> clear the information included in VarRA-Report; 6> set the plmn-IdentityList to the list of EPLMNs stored by the UE (i.e. includes the RPLMN); 4> else: 5> set the plmn-Identity, in plmn-IdentityList, to the PLMN selected by upper layers from the PLMN(s) included in the plmn-IdentityList in SIB1; 4> set the cellId to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; 4> set the requested-SI-List to indicate the system information (SI) message(s) that the UE requested to receive via request for on demand system information procedure; 4> store the system information type that UE requested as part of request for system information procedure in SIB-Mapping 4> store the preamble indexes of the preambles configured or used as part of random access procedure for the request for system information procedure 4> store the RACH resource configurations configured for the random access procedure for request for system information as part of SI-RequestConfig 4> set the raPurpose to include the purpose of triggering the random-access procedure; 4> set the ra-InformationCommon-r16 as specified in subclause 5.7.10.5. ********** Next Change to 3GPP TS 38.331 V16.3.0 ********** 5.2.2.3.3 Request for on demand system information The UE shall: 1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[13], clause 5.1.1 is met: 2> trigger the lower layer to initiate the random access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> initiate transmission of the RRCSystemInfoRequest message in accordance with 5.2.2.3.4; 2> if acknowledgement for RRCSystemInfoRequest message is received from lower layers: 3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately; 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: 2> reset MAC; 2> if SI request is based on RRCSystemInfoRequest message: 3> release RLC entity for SRB0. 1> Perform actions specified in 5.7.10.x NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. ********** End Changes to 3GPP TS 38.331 V16.3.0 ********** Figure 5 is a schematic block diagram of a radio access node 500 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 500 may be, for example, a base station 302 or 306 or a network node that implements all or part of the functionality of the base station 302 or gNB described herein. As illustrated, the radio access node 500 includes a control system 502 that includes one or more processors 504 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 506, and a network interface 508. The one or more processors 504 are also referred to herein as processing circuitry. In addition, the radio access node 500 may include one or more radio units 510 that each includes one or more transmitters 512 and one or more receivers 514 coupled to one or more antennas 516. The radio units 510 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 510 is external to the control system 502 and connected to the control system 502 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 510 and potentially the antenna(s) 516 are integrated together with the control system 502. The one or more processors 504 operate to provide one or more functions of a radio access node 500 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 506 and executed by the one or more processors 504. Figure 6 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 500 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes. As used herein, a “virtualized” radio access node is an implementation of the radio access node 500 in which at least a portion of the functionality of the radio access node 500 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 500 may include the control system 502 and/or the one or more radio units 510, as described above. The control system 502 may be connected to the radio unit(s) 510 via, for example, an optical cable or the like. The radio access node 500 includes one or more processing nodes 600 coupled to or included as part of a network(s) 602. If present, the control system 502 or the radio unit(s) are connected to the processing node(s) 600 via the network 602. Each processing node 600 includes one or more processors 604 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 606, and a network interface 608. In this example, functions 610 of the radio access node 500 described herein are implemented at the one or more processing nodes 600 or distributed across the one or more processing nodes 600 and the control system 502 and/or the radio unit(s) 510 in any desired manner. In some particular embodiments, some or all of the functions 610 of the radio access node 500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 600. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 600 and the control system 502 is used in order to carry out at least some of the desired functions 610. Notably, in some embodiments, the control system 502 may not be included, in which case the radio unit(s) 510 communicate directly with the processing node(s) 600 via an appropriate network interface(s). In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 500 or a node (e.g., a processing node 600) implementing one or more of the functions 610 of the radio access node 500 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). Figure 7 is a schematic block diagram of the radio access node 500 according to some other embodiments of the present disclosure. The radio access node 500 includes one or more modules 700, each of which is implemented in software. The module(s) 700 provide the functionality of the radio access node 500 described herein. This discussion is equally applicable to the processing node 600 of Figure 6 where the modules 700 may be implemented at one of the processing nodes 600 or distributed across multiple processing nodes 600 and/or distributed across the processing node(s) 600 and the control system 502. Figure 8 is a schematic block diagram of a wireless communication device 800 according to some embodiments of the present disclosure. As illustrated, the wireless communication device 800 includes one or more processors 802 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 804, and one or more transceivers 806 each including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver(s) 806 includes radio-front end circuitry connected to the antenna(s) 812 that is configured to condition signals communicated between the antenna(s) 812 and the processor(s) 802, as will be appreciated by on of ordinary skill in the art. The processors 802 are also referred to herein as processing circuitry. The transceivers 806 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 800 described above may be fully or partially implemented in software that is, e.g., stored in the memory 804 and executed by the processor(s) 802. Note that the wireless communication device 800 may include additional components not illustrated in Figure 8 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 800 and/or allowing output of information from the wireless communication device 800), a power supply (e.g., a battery and associated power circuitry), etc. In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 800 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). Figure 9 is a schematic block diagram of the wireless communication device 800 according to some other embodiments of the present disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software. The module(s) 900 provide the functionality of the wireless communication device 800 described herein. With reference to Figure 10, in accordance with an embodiment, a communication system includes a telecommunication network 1000, such as a 3GPP- type cellular network, which comprises an access network 1002, such as a RAN, and a core network 1004. The access network 1002 comprises a plurality of base stations 1006A, 1006B, 1006C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1008A, 1008B, 1008C. Each base station 1006A, 1006B, 1006C is connectable to the core network 1004 over a wired or wireless connection 1010. A first UE 1012 located in coverage area 1008C is configured to wirelessly connect to, or be paged by, the corresponding base station 1006C. A second UE 1014 in coverage area 1008A is wirelessly connectable to the corresponding base station 1006A. While a plurality of UEs 1012, 1014 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1006. The telecommunication network 1000 is itself connected to a host computer 1016, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 1016 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1018 and 1020 between the telecommunication network 1000 and the host computer 1016 may extend directly from the core network 1004 to the host computer 1016 or may go via an optional intermediate network 1022. The intermediate network 1022 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1022, if any, may be a backbone network or the Internet; in particular, the intermediate network 1022 may comprise two or more sub-networks (not shown). The communication system of Figure 10 as a whole enables connectivity between the connected UEs 1012, 1014 and the host computer 1016. The connectivity may be described as an Over-the-Top (OTT) connection 1024. The host computer 1016 and the connected UEs 1012, 1014 are configured to communicate data and/or signaling via the OTT connection 1024, using the access network 1002, the core network 1004, any intermediate network 1022, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1024 may be transparent in the sense that the participating communication devices through which the OTT connection 1024 passes are unaware of routing of uplink and downlink communications. For example, the base station 1006 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1016 to be forwarded (e.g., handed over) to a connected UE 1012. Similarly, the base station 1006 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1012 towards the host computer 1016. Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to Figure 11. In a communication system 1100, a host computer 1102 comprises hardware 1104 including a communication interface 1106 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1100. The host computer 1102 further comprises processing circuitry 1108, which may have storage and/or processing capabilities. In particular, the processing circuitry 1108 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 1102 further comprises software 1110, which is stored in or accessible by the host computer 1102 and executable by the processing circuitry 1108. The software 1110 includes a host application 1112. The host application 1112 may be operable to provide a service to a remote user, such as a UE 1114 connecting via an OTT connection 1116 terminating at the UE 1114 and the host computer 1102. In providing the service to the remote user, the host application 1112 may provide user data which is transmitted using the OTT connection 1116. The communication system 1100 further includes a base station 1118 provided in a telecommunication system and comprising hardware 1120 enabling it to communicate with the host computer 1102 and with the UE 1114. The hardware 1120 may include a communication interface 1122 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1100, as well as a radio interface 1124 for setting up and maintaining at least a wireless connection 1126 with the UE 1114 located in a coverage area (not shown in Figure 11) served by the base station 1118. The communication interface 1122 may be configured to facilitate a connection 1128 to the host computer 1102. The connection 1128 may be direct or it may pass through a core network (not shown in Figure 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 1120 of the base station 1118 further includes processing circuitry 1130, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 1118 further has software 1132 stored internally or accessible via an external connection. The communication system 1100 further includes the UE 1114 already referred to. The UE’s 1114 hardware 1134 may include a radio interface 1136 configured to set up and maintain a wireless connection 1126 with a base station serving a coverage area in which the UE 1114 is currently located. The hardware 1134 of the UE 1114 further includes processing circuitry 1138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 1114 further comprises software 1140, which is stored in or accessible by the UE 1114 and executable by the processing circuitry 1138. The software 1140 includes a client application 1142. The client application 1142 may be operable to provide a service to a human or non-human user via the UE 1114, with the support of the host computer 1102. In the host computer 1102, the executing host application 1112 may communicate with the executing client application 1142 via the OTT connection 1116 terminating at the UE 1114 and the host computer 1102. In providing the service to the user, the client application 1142 may receive request data from the host application 1112 and provide user data in response to the request data. The OTT connection 1116 may transfer both the request data and the user data. The client application 1142 may interact with the user to generate the user data that it provides. It is noted that the host computer 1102, the base station 1118, and the UE 1114 illustrated in Figure 11 may be similar or identical to the host computer 1016, one of the base stations 1006A, 1006B, 1006C, and one of the UEs 1012, 1014 of Figure 10, respectively. This is to say, the inner workings of these entities may be as shown in Figure 11 and independently, the surrounding network topology may be that of Figure 10. In Figure 11, the OTT connection 1116 has been drawn abstractly to illustrate the communication between the host computer 1102 and the UE 1114 via the base station 1118 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 1114 or from the service provider operating the host computer 1102, or both. While the OTT connection 1116 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 1126 between the UE 1114 and the base station 1118 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1114 using the OTT connection 1116, in which the wireless connection 1126 forms the last segment. A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1116 between the host computer 1102 and the UE 1114, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1116 may be implemented in the software 1110 and the hardware 1104 of the host computer 1102 or in the software 1140 and the hardware 1134 of the UE 1114, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1116 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1110, 1140 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1116 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1118, and it may be unknown or imperceptible to the base station 1118. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 1102’s measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 1110 and 1140 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1116 while it monitors propagation times, errors, etc. Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In step 1200, the host computer provides user data. In sub-step 1202 (which may be optional) of step 1200, the host computer provides the user data by executing a host application. In step 1204, the host computer initiates a transmission carrying the user data to the UE. In step 1206 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1208 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step 1300 of the method, the host computer provides user data. In an optional sub-step (not shown) the host computer provides the user data by executing a host application. In step 1302, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1304 (which may be optional), the UE receives the user data carried in the transmission. Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1400 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1402, the UE provides user data. In sub-step 1404 (which may be optional) of step 1400, the UE provides the user data by executing a client application. In sub-step 1406 (which may be optional) of step 1402, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 1408 (which may be optional), transmission of the user data to the host computer. In step 1410 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1500 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1502 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1504 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station. Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.). Some example embodiments of the present disclosure are as follows: Group A Embodiments Embodiment 1: A method performed by a wireless communication device (312), the method comprising: sending (402) a request for system information to a network node; regardless of whether the request for system information succeeds or fails, logging (404) information and/or measurements related to the request for system information; and reporting (406) the logged information and/or measurements to a network node. Embodiment 2: The method of embodiment 1 wherein sending (402) the request for system information comprises sending (402) the request for system information via a message sent during a random access procedure. Embodiment 3: The method of embodiment 2 wherein the message is MSG1 or MSG3. Embodiment 4: The method of any of embodiments 1 to 3 wherein the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device (312), (b) a list of system information types that are wanted by the wireless communication device (312), (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information about random access resources configured for the random access procedure in which the request for system information was sent, (e) information that indicates whether the request for system information was sent via MSG1 or MSG3 in the random access procedure, (f) information that indicates that a purpose of the random access procedure was to make the request for system information, or (g) any combination of two or more of (a)-(f). Embodiment 5: The method of any of embodiments 1 to 3 wherein the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device (312), (b) a list of system information types that are wanted by the wireless communication device (312), (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information comprised in a system information request configuration, (e) preamble group index (or ID) that is used to perform the random access procedure in which the request for system information was sent, (f) frequency related information about random access resources used for the random access procedure in which the request for system information was sent, (g) a cell identity of a cell in which the random access procedure was performed, (h) information related to random access attempts performed per each selected beam, or (i) any combination of two or more of (a)-(h). Embodiment 6: The method of embodiment 5 wherein the information comprised in the system information request configuration comprises: i) ssb-perRACH-Occasion, ii) si-RequestPeriod, iii) si-RequestResources, iv) SI-RequestResources including: a. ra-PreambleStartIndex, b. ra-AssociationPeriodIndex, and/or c. ra-ssb-OccasionMaskIndex, or v) a combination of any two or more of (i) to (iv). Embodiment 7: The method of any of embodiments 1 to 6 wherein the request for system information succeeds. Embodiment 8: The method of embodiment 7 wherein reporting (406) the logged information and/or measurements to a network node comprises reporting (406) the logged information and/or measurements to a network node via a random access report. Embodiment 9: The method of any of embodiments 1 to 6 wherein the request for system information fails. Embodiment 10: The method of embodiment 9 wherein reporting (406) the logged information and/or measurements to a network node comprises reporting (406) the logged information and/or measurements to a network node via a connection establishment failure report. Embodiment 11: The method of any of embodiments 1 to 6 wherein reporting (406) the logged information and/or measurements to a network node comprises reporting (406) the logged information and/or measurements to a network node via a dedicated report. Embodiment 12: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments Embodiment 13: A method performed by a base station (302), the method comprising: receiving (404) a report comprising logged information and/or measurements from a wireless communication device (312), the logged information and/or measurements comprising information and/or measurements related to a request for system information sent by the wireless communication device (312) regardless of whether the request for system information succeed or failed; and using (406) the logged information and/or measurements. Embodiment 14: The method of embodiment 13 wherein the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device (312), (b) a list of system information types that are wanted by the wireless communication device (312), (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information about random access resources configured for the random access procedure in which the request for system information was sent, (e) information that indicates whether the request for system information was sent via MSG1 or MSG3 in the random access procedure, (f) information that indicates that a purpose of the random access procedure was to make the request for system information, or (g) any combination of two or more of (a)-(f). Embodiment 15: The method of any of embodiments 13 wherein the logged information and/or measurements comprises: (a) a list of system information types that are requested by the wireless communication device (312), (b) a list of system information types that are wanted by the wireless communication device (312), (c) the random access preamble index(es) configured for a random access procedure in which the request for system information was sent, (d) information comprised in a system information request configuration, (e) preamble group index (or ID) that is used to perform the random access procedure in which the request for system information was sent, (f) frequency related information about random access resources used for the random access procedure in which the request for system information was sent, (g) a cell identity of a cell in which the random access procedure was performed, (h) information related to random access attempts performed per each selected beam, or (i) any combination of two or more of (a)-(h). Embodiment 16: The method of embodiment 15 wherein the information comprised in the system information request configuration comprises: i) ssb-perRACH-Occasion, ii) si-RequestPeriod, iii) si-RequestResources, iv) SI-RequestResources including: a. ra-PreambleStartIndex, b. ra-AssociationPeriodIndex, and/or c. ra-ssb-OccasionMaskIndex, or v) a combination of any two or more of (i) to (iv). Embodiment 17: The method of any of embodiments 13 to 16 wherein the request for system information succeeds. Embodiment 18: The method of embodiment 17 wherein the received report is a random access report. Embodiment 19: The method of any of embodiments 13 to 16 wherein the request for system information fails. Embodiment 20: The method of embodiment 19 wherein the received report is a connection establishment failure report. Embodiment 21: The method of any of embodiments 13 to 16 wherein the received report is a dedicated report. Embodiment 22: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless communication device. Group C Embodiments Embodiment 23: A wireless communication device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless communication device. Embodiment 24: A base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station. Embodiment 25: A User Equipment, UE, comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. Embodiment 26: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. Embodiment 27: The communication system of the previous embodiment further including the base station. Embodiment 28: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. Embodiment 29: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application. Embodiment 30: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. Embodiment 31: The method of the previous embodiment, further comprising, at the base station, transmitting the user data. Embodiment 32: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. Embodiment 33: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments. Embodiment 34: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. Embodiment 35: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. Embodiment 36: The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application. Embodiment 37: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. Embodiment 38: The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. Embodiment 39: A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. Embodiment 40: The communication system of the previous embodiment, further including the UE. Embodiment 41: The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. Embodiment 42: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. Embodiment 43: The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. Embodiment 44: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. Embodiment 45: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. Embodiment 46: The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application. Embodiment 47: The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data. Embodiment 48: A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. Embodiment 49: The communication system of the previous embodiment further including the base station. Embodiment 50: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. Embodiment 51: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. Embodiment 52: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. Embodiment 53: The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. Embodiment 54: The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer. Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.