Small data transmission reporting

Abstract

According to an aspect, there is provided a method performed by a user equipment, UE, in a communication network. The method comprises: obtaining (301) values of one or more metrics relating to a Small Data Transmission, SDT, procedure used for transmitting data to, and / or receiving data from, a first Radio Access Network, RAN, node in the communication network; and sending (303), to the first RAN node, a measurement report comprising the obtained values.

Description

[0001] SMALL DATA TRANSMISSION REPORTING Technical Field This disclosure relates to Small Data Transmission (SDT) procedures that are used by a user equipment (UE) for transmitting data to, and / or receiving data from, radio access network (RAN) nodes in a communication network, and in particular to measurement reports relating to SDT procedures. Background Self-Organising Networks (SON) in 3GPP – A Self-Organising Network (SON) is an automation technology designed to make the planning, configuration, management, optimisation and healing (repair) of mobile radio access networks simpler and faster. SON functionality and behaviour has been defined and specified in generally accepted mobile industry recommendations produced by organisations such as the 3rdGeneration Partnership Project (3GPP) and Next Generation Mobile Networks (NGMN). In 3GPP, the processes within the SON area are classified into self-configuration process and self-optimisation process. Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation. Self-configuration is a process that works in a pre-operational state. A pre-operational state is understood as the state from when the eNB is powered up and has backbone connectivity until the radio frequency (RF) transmitter is switched on. Self-optimisation is a process where User Equipment (UE) and access node measurements and performance measurements are used to auto-tune the network. Self-optimisation is a process that works in an operational state. The operational state is understood as the state where the RF interface is additionally switched on. Fig. 1 is a block diagram illustrating operations and functions performed in the pre- operational state and operational state. Fig.1 is a copy of Figure 22.1-1 from 3GPP Technical Standard (TS) 36.300 v17.4.0. As illustrated in Fig.1, functions handled in the Self-configuration process / pre-operational state include Basic Setup and Initial Radio Configuration. Also as illustrated in Fig.1, functions handled in the operational state include Optimisation / Adaptation. In Long Term Evolution (LTE), support for Self-Configuration and Self-Optimisation is specified in section 22.2 of 3GPP TS 36.300, and includes features such as Dynamic configuration, Automatic Neighbour Relation (ANR), mobility load balancing, Mobility Robustness Optimisation (MRO), Random Access Channel (RACH) optimisation, and support for energy saving. In New Radio (NR), support for Self-Configuration and Self-Optimisation is specified as well, starting with Self-Configuration features such as Dynamic configuration, Automatic Neighbour Relation (ANR) in Release 15 (Rel-15), as described in section 15 of 3GPP TS 38.300 v15.15.0. In NR Release 16 (Rel-16), more SON features are being specified, including Self-Optimisation features such as Mobility Robustness Optimisation (MRO). Minimisation of Drive Tests (MDT) – MDT was standardised for NR in Rel-16 to reduce the amount of drive tests performed manually. It is a UE-assisted framework where network measurements are collected by both IDLE / INACTIVE and Radio Resource Control (RRC) Connected UE(s) in order to aid the network in gathering valuable information. It has been specified for both LTE and NR in 3GPP TS 37.320 v17.4.0. In general, there are two types of MDT measurement logging, Logged MDT and Immediate MDT. Logged MDT Type based on RRC states – A UE in RRC_IDLE / RRC_INACTIVE state is configured to perform periodical and event-triggered MDT logging after receiving the MDT configurations from the network. The UE shall report the downlink (DL) pilot strength measurements (Reference Signal Received Power (RSRP) / Reference Signal Received Quality (RSRQ)) together with time information, detailed location information if available, and Wireless Local Area Network (WLAN), Bluetooth to the network using the UE information framework when it is in RRC_CONNECTED state. The DL pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purposes, without requiring the UE to perform additional measurements. MDT mode RRC states Measurement quantities Logged MDT RRC_IDLE / RRC RSRP and RSRQ of the serving cell and available UE _INACTIVE measurements for intra-frequency / inter-frequency / inter- RAT, time stamp and detailed location information if available Table 1 – Measurement logging for Logged MDT For periodical Logged MDT, the UE receives the MDT configurations including logginginterval and loggingduration in the RRC message, i.e. LoggedMeasurementConfiguration, from the network. A timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (which is 10 minutes – 120 minutes). The UE shall perform periodical MDT logging with the interval set to logginginterval (1.28 seconds – 61.44 seconds) when the UE is in RRC_IDLE. An example of the Logged MDT procedure is illustrated in Fig.2. For event-triggered Logged MDT, the UE receives eventType and logginginterval from the network. The UE logs the measurement reports at every logginginterval if the event configured in eventType is satisfied. A Rel-16 UE that supports NR logged MDT configuration can be configured with one amongst two different events. One of them is associated to logging of measurements when the UE enters any cell selection state, and the other is when the UE’s serving cell quality is below a threshold. Small Data Transmission (SDT) – In Rel-15, 3GPP introduced a new radio-access technology known as NR (New Radio). The technology was further enhanced in Release 16, and will continue to evolve in Release 17 (Rel.17), and later. In NR, the device can be in RRC idle state, in RRC connected state, or in RRC inactive state. Until Release 16, data transmission was possible only in RRC connected. Therefore, the UE must transition to a connected state from idle or inactive states every time there is data to transfer between the UE and gNB. The transition from RRC_Idle or RRC_Inactive state to RRC_Connected leads to significant signalling overhead and power consumption, particularly for UEs that infrequently transmit small data packets. In RRC_Inactive state, the UE has established RRC context and core network connection. Therefore, the transition from Inactive to Connected state is relatively fast and requires less signalling compared to the transition from Idle to Connected state. In order to enable efficient transmission of small infrequent data packets, 3GPP has approved a new study item on NR small data transmissions in RRC_Inactive state. In Rel-17, this specified Mobile Originated Small Data Transmission (MO-SDT) to allow small packet transmission for uplink (UL)-oriented packets. The new Release 18 (Rel.18) expects Mobile Terminated (MT) SDT, that is DL-triggered small data, to allow similar benefits, i.e. 1) reducing signalling overhead and UE power consumption by not transitioning to RRC_CONNECTED, and reducing latency by allowing fast transmission of (small and infrequent) packets, e.g. for positioning. The scope of this work item majorly addresses two main objectives. ^ MT-SDT triggering mechanism for UEs in RRC_INACTIVE, supporting Random Access (RA)-SDT (RA-SDT) and Configured Grant (CG)-SDT (CG-SDT) as the UL response. ^ MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmissions in RRC_INACTIVE. MT-SDT addresses application use cases by typically reducing the overall signalling overhead with an aim to minimise the UE power consumption. In short, the MO-SDT procedure is triggered by the UE receiving UL data in its buffer. If the UL data is mapped to a Data Radio Bearer (DRB) configured for SDT it further checks that the data volume is below a Data Volume Threshold (DVT) and that the RSRP is above a configured threshold. If these conditions are satisfied it initiates the SDT procedure. It may then use either CG-SDT or RA-SDT based access. CG-SDT uses configured grants and requires the UE to remain in the cell where it was released to inactive and that its RSRP does not change more than a threshold from the RSRP it had when it was released to inactive. There is also a specific timing advance timer (TAT), CG- SDT-TAT, which must be running. When 2-step Random Access (RA) is applied for SDT, the Message a (MsgA) will contain the RRCResumeRequest message and User Plane (UP) data. The gNB will, as in the legacy case, respond with the Contention Resolution (CR) Identity (ID) (CR-ID) to resolve contention. It will also send a Cell-Radio Network Temporary Identifier (C-RNTI) and the UE will monitor Physical Downlink Control Channel (PDCCH) for Downlink Control Information (DCI) scrambled by C-RNTI to obtain new UL grants or assignments for DL data, in case subsequent transmissions are needed. As for the 4-step RA procedure, the SDT procedure ends when the gNB sends a RRCRelease with suspend config message, and thereby keeps the UE in Inactive state. Alternatively, the gNB may instead send a RRCResume and move the UE to connected state. When the 4-step RA is applied for SDT, the Message 3 (Msg3) will contain the RRCResumeRequest message and UP data. The gNB will, as in the legacy case, respond with the contention resolution ID (CR-ID) to resolve contention and at this point the Temporary C-RNTI (TC-RNTI) will be used by the UE as C-RNTI, i.e. the UE will monitor PDCCH for DCI scrambled by C-RNTI to obtain new UL grants or assignments for DL data, in case subsequent transmissions are needed. The SDT procedure ends when the gNB sends a RRCRelease with suspend config message and thereby keeps the UE in Inactive state. Alternatively, the gNB may instead send a RRCResume and move the UE to connected state. As described above, there are three options to perform MO-SDT: CG-SDT, 2-step RA-SDT and 4-step RA-SDT. The selection of procedure is specified as followed in clause 5.29 of 3GPP TS 38.321 v17.3.0: ******************************************************** “The MAC entity shall, if initiated by the upper layers for SDT procedure: 1> if the data volume of the pending UL data across all RBs configured for SDT is less than or equal to sdt- DataVolumeThreshold; and NOTE: For SDT procedure, the MAC entity also considers the suspended RBs configured with SDT for data volume calculation. It is up to the UE's implementation how the UE calculates the data volume for the suspended RBs. Size of the CCCH message is not considered for data volume calculation 1> if the RSRP of the downlink pathloss reference is higher than sdt-RSRP-Threshold; or 1> if sdt-RSRP-Threshold is not configured: 2> if the Serving Cell for SDT is configured with supplementary uplink as specified in TS 38.331 [5]; and 2> if the RSRP of the downlink pathloss reference is less than rsrp-ThresholdSSB-SUL: 3> select the SUL carrier. 2> else: 3> select the NUL carrier. 2> if CG-SDT is configured on the selected UL carrier, and TA of the configured grant Type 1 resource is valid in the first available CG occasion according to clause 5.27.2; and 2> if, for each RB having data available for transmission, configuredGrantType1Allowed, if configured, is configured with value true for the corresponding logical channel; and 2> if at least one SSB configured for CG-SDT with SS-RSRP above cg-SDT-RSRP-ThresholdSSB is available: 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled; 3> perform CG-SDT procedure on the selected UL carrier according to clause 5.8.2. 2> else if a set of Random Access resources for performing RA-SDT are selected according to clause 5.1.1b on the selected UL carrier: 3> if cg-SDT-TimeAlignmentTimer is running, consider cg-SDT-TimeAlignmentTimer as expired and perform the corresponding actions in clause 5.2; 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled. 2> else: 3> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled. 1> else: 2> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled. If RA-SDT is selected above and after the Random Access procedure is successfully completed (see clause 5.1.6), the UE monitors PDCCH addressed to C-RNTI until the RA-SDT procedure is terminated. If CG-SDT is selected above and after the initial transmission for CG-SDT is performed, the UE monitors PDCCH addressed to C-RNTI and CS-RNTI until the CG-SDT procedure is terminated. ******************************************************** Specification of MT-SDT is currently ongoing in 3GPP Rel-18. It will be initiated by the gNB paging the UE for MT-SDT. The UE will then follow the procedure of MO-SDT, except that it will not transmit any data in the first UL transmission and may receive data in DL already in Message 4 (Msg4) or Message B (MsgB). Summary There currently exist certain challenge(s). As noted above, small data transmission (SDT) has been standardised since 3GPP Rel-17. Mobile Originated SDT (MO-SDT) is introduced in 3GPP Rel-17. Mobile Terminated SDT (MT-SDT) is being studied and will be introduced in 3GPP Rel-18. Currently, the SDT configurations used by the network may impair the UE’s Quality of Service (QoS) satisfaction and / or may not be fully suitable for the needs of the UE, meaning that configured SDT resources in the cell can be insufficient or under-utilised due to the network having insufficient SDT measurements reported / collected by the UE. There is therefore a need to enable improved SDT performance, in particular with respect to SON / MDT purposes. This disclosure notes that it is beneficial for the UE to report metrics relating to SDT transmission and / or reception performance to the network for SON and MDT purposes. The network may consider the UE reported measurement results of SDT, and update the SDT configurations to maximise the UE’s QoS satisfaction and avoid the configured SDT resources in the cell being insufficient or under-utilised. The current content of the measurements for SON / MDT do not cover important measurements or metrics that are significant for SDT performance, and so this disclosure also proposes mechanisms / procedures in which the UE can log values of metrics relevant for SDT performance after performing a SDT procedure, and the UE can report these metric values to the network (for example in response to a request from the network). This disclosure indicates a number of metrics that can be relevant for SDT. For example, any one or more of data volume can be logged, a number of transmissions, radio conditions, and / or a type of SDT procedure used. In addition, the MDT configuration provided by the network doesn’t cover SDT-related triggers, meaning that the UE cannot perform SDT-related measurement effectively. According to a first aspect, there is provided a method performed by a UE in a communication network. The method comprises: obtaining values of one or more metrics relating to a SDT procedure used for transmitting data to, and / or receiving data from, a first Radio Access Network, RAN, node in the communication network; and sending, to the first RAN node, a measurement report comprising the obtained values. According to a second aspect, there is provided a method performed by a first RAN node in a communication network. The method comprises receiving, from a UE in the communication network, a measurement report comprising obtained values of one or more metrics relating to a SDT procedure used for transmitting data to, and / or receiving data from, the first RAN node. According to a third aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect or any embodiments thereof. According to a fourth aspect, there is provided a UE configured to perform the method according to the first aspect or any embodiment thereof. According to a fifth aspect, there is provided a UE comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method according to the first aspect or any embodiment thereof. According to a sixth aspect, there is provided a first RAN node, configured to perform the method according to the second aspect or any embodiment thereof. According to a seventh aspect, there is provided a first RAN node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first RAN node is operative to perform the method according to the second aspect or any embodiment thereof. Certain embodiments may provide one or more of the following technical advantage(s). In particular, it is beneficial for the UE to report metrics relating to SDT transmission and / or reception performance to the network for SON and MDT purposes. The network may consider the UE reported measurement results of SDT, and update the SDT configurations to maximise the UE’s QoS satisfaction and avoid the configured SDT resources in the cell being insufficient or under- utilised. Brief Description of the Drawings Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: Fig. 1 is a block diagram illustrating operations and functions performed in the pre- operational state and operational state of a SON; Fig.2 illustrates a Logged MDT procedure; Fig.3 is a flow chart illustrating a method performed by a UE in accordance with some embodiments; Fig.4 is a flow chart illustrating a method performed by a RAN node in accordance with some embodiments; Fig. 5 shows an example of a communication system in accordance with some embodiments; Fig.6 shows a UE in accordance with some embodiments; Fig.7 shows a RAN network node in accordance with some embodiments; and Fig. 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized. Detailed Description Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. As noted above, this disclosure proposes mechanisms / procedures in which the UE can log values of metrics relevant for SDT performance after performing a SDT procedure, and the UE can report these metric values to the network (for example in response to a request from the network). In this disclosure, a SDT transmission is defined to be a transmission or reception of data on a DRB or Signalling Radio Bearer (SRB) configured for SDT. A SDT procedure is defined as a procedure which is started by the UE via an uplink initial Physical Uplink Shared Channel (PUSCH) transmission containing a Common Control Channel (CCCH) signalling (e.g. RRCResumeRequest) and small data using a RACH resource (where the procedure is referred to as RA-SDT) or a configured grant (CG) resource (where the procedure is referred to as CG- SDT), and followed by one or multiple uplink PUSCH transmissions or Physical Downlink Shared Channel (PDSCH) receptions. The UE initiates an SDT procedure when the UE is in a less active RRC state (e.g., RRC_INACTIVE). Once initiated, the SDT procedure is either: • successfully completed after the UE is directed to RRC_IDLE (via RRCRelease) or to continue in RRC_INACTIVE (via RRCRelease or RRCReject) or to RRC_CONNECTED (via RRCResume or RRCSetup); or • unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a Medium Access Control (MAC) entity reaching a configured maximum Physical Random Access Channel (PRACH) preamble transmission threshold, a Radio Link Control (RLC) entity reaching a configured maximum retransmission threshold, or expiry of SDT- specific timing alignment timer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission. The embodiments are described in the context of New Radio (NR), where the UE performs SDT transmissions and / or receptions when the UE is RRC INACTIVE. The embodiments are also applicable to a UE using LTE Radio Access Technology (RAT), where the UE performs SDT transmissions and / or receptions when the UE is in RRC IDLE. Further, the described embodiments are not limited to the UE being in RRC IDLE or RRC INACTIVE, and the techniques described herein can be applied to a UE in any dormant state, i.e. a state where the UE is in a less active state to achieve energy saving, and / or where the UE has less / fewer configurations / resources to be active for small data transfer or reception. Enhancements to the RACH report – To enable the network to improve the SDT configuration, additional information / measurements are required from the UE. Thus, in embodiments of this disclosure a UE can be configured to provide a report to the network (eNB or gNB) comprising one or multiple of the types of metrics listed below. The metrics are also referred to herein as measurements and / or information. ^ The number of successfully completed SDT procedures. o Where a SDT procedure comprises one or multiple consecutive SDT transmissions or receptions. o A SDT procedure starts with an initial transmission or reception when the UE is in RRC IDLE or RRC INACTIVE, and continues with zero or multiple consecutive SDT transmissions or receptions until the UE is released back to RRC INACTIVE, or the UE has transitioned to a different RRC state; and / or o The number of successfully completed RA-SDT and CG-SDT procedures may be counted separately. ^ The number of successfully completed MO-SDT procedures. ^ The number of successfully completed MT-SDT procedures. ^ The number of unsuccessfully completed SDT procedures. o The number of unsuccessful RA-SDT and CG-SDT procedures may be counted separately. ^ The number of unsuccessfully completed MO-SDT procedures. ^ The number of unsuccessfully completed MT-SDT procedures. ^ The number or data volume of transmitted SDT transmissions / packets. ^ The number or data volume of received SDT transmissions / packets. ^ The number or data volume of transmitted or received SDT packets when using a configured grant / semi-persistent resource. ^ The number or data volume of transmitted or received SDT packets when using a dynamic grant / assignment. ^ The duration of each SDT procedure. ^ The number of SDT packets transmitted or received during each SDT procedure. o The number of SDT packets transmitted or received during each RA-SDT and CG- SDT procedure may be counted separately. ^ The SDT data volume transmitted or received during each SDT procedure. o The SDT data volume transmitted or received during each RA-SDT and CG-SDT procedure may be counted separately. ^ The type of each SDT procedure: o i.e. MO-SDT or MT-SDT; o i.e. RA-SDT or CG-SDT. ^ The delay of each transmitted or received SDT packet. ^ Measurements of DL radio channel quality in terms of, e.g., RSRP, RSRQ, Received Signal Strength Indicator (RSSI). o The measurements can relate to the strongest DL SSBs or CSI-RSs that the UE has measured when initialising the SDT procedure or during the SDT procedure. ^ The change of SSB during CG-SDT procedure. ^ The number of transmitted Sounding Reference Signals (SRS) for UL channel quality measurement purposes. ^ The number of transmitted UL Hybrid Automatic Repeat Request (HARQ) acknowledgements. ^ The cell IDs where the UE has performed SDT transmission or reception. ^ RACH configurations which are applied by the UE during the logging period. Any of the following can apply to the performance / counting and reporting of the metric values (measurements or information) by the UE: ^ the UE may obtain the additional information / measurements and report them to the network only during a measurement time window; ^ the UE may perform / count and report the measurements per bandwidth part (BWP), or per cell; ^ the UE may perform / count and report the measurements per SDT procedure; ^ the UE may perform / count and report the measurements per RACH procedure; ^ the UE may perform / count and report the measurements per radio bearer (DRB or SRB), service or Logical Channel (LCH); ^ the UE may perform / count and report the measurements in a RACH report upon reception of a request message from the gNB; o the request message may be indicated by the gNB in a UEInformationRequest RRC signalling; o the RACH report sent by the UE may be carried by a UEInformationResponseRRC signalling sent by the UE to the gNB; o the request message and the RACH report may be transmitted during an SDT procedure without moving the UE to connected mode. In some embodiments, the UE may be triggered to perform logs / measurements according to a configuration provided by the gNB. The configuration provided by the gNB may include rules, conditions or timings for when the UE is to perform logs / measurements. The gNB may provide the configuration to the UE via any suitable signalling mechanism, such as in system information (SI); dedicated RRC signalling (for example configured in otherConfig in RRCReconfiguration); a MAC Control Element (CE); Layer 1 (L1) signalling carried on physical channels including PDCCH, PDSCH etc. In alternative embodiments, the UE may be pre-configured with rules, conditions or timings for when the UE is to perform logs / measurements. For example, the UE may be triggered to perform logs / measurements when one or more of the below conditions is met: ^ upon completion of every NthSDT transmission and / or reception, where N may be 1; ^ upon completion of every NthSDT procedure, where N may be 1; ^ upon initiation of every NthSDT procedure, where N may be 1; ^ upon triggering of every NthRACH procedure, where N may be 1. In these embodiments, the trigger may count both successfully completed transmissions or receptions, and unsuccessfully completed transmissions or receptions. A transmission or reception being unsuccessfully completed means that the transmission or reception cannot be successfully completed after a maximum number of attempts or a maximum time period, for reasons such as cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or expiry of a SDT-specific timing alignment timer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission. In these embodiments, the trigger may count both successfully completed SDT procedures, and unsuccessfully completed SDT procedures. As described above, once a SDT procedure is initiated, the procedure is either: ^ successfully completed after the UE is directed to RRC_IDLE (via RRCRelease), or directed to continue in RRC_INACTIVE (via RRCRelease or RRCReject) or directed to RRC_CONNECTED (via RRCResume or RRCSetup); or ^ unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or expiry of SDT- specific timing alignment timer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission. The following section provides implementation examples of the RACH report disclosed herein. In one implementation example, the UE is triggered to log the measurements of RACH- based SDT transmissions and receptions when each SDT procedure is initiated by a RACH- based uplink transmission. The UE completes the log for this SDT procedure after the SDT procedure has successfully completed or unsuccessfully completed. In another implementation example, the UE is triggered to log the measurements of Configured Grant-based SDT transmissions and receptions when each SDT procedure is initiated by a Configured Grant-based uplink transmission. The UE completes the log for this SDT procedure after the SDT procedure has successfully completed or unsuccessfully completed. In another implementation example, the above methods impacting the Abstract Syntax Notation One (ASN1) of the RRC specification may be represented in 3GPP TS 38.331 v17.3.0 as follows in the UEInformationResponse message conveying the RA report. The implementation below only covers part of the proposed information elements / changes, with the proposed changes being highlighted in bold and underline. ************************************************************************************************************* - UEInformationResponse The UEInformationResponse message is used by the UE to transfer information requested by the network. Signalling radio bearer: SRB1 or SRB2 (when logged measurement information is included) RLC-SAP: AM Logical channel: DCCH Direction: UE to network UEInformationResponse message -- ASN1START -- TAG-UEINFORMATIONRESPONSE-START UEInformationResponse-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationResponse-r16 UEInformationResponse-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationResponse-r16-IEs ::= SEQUENCE {

[0002] [[ spCellID-r17 CGI-Info-Logging-r16

[0003] nrofMsgA-PO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, )

[0004] [[ fallbackToFourStepRA-r17 ENUMERATED {true} OPTIONAL ]], [[ fallbackToRASDT-r18 ENUMERATED {true} OPTIONAL, sdtFourStepRA-r18 ENUMERATED {true} OPTIONAL, sdtTwoStepRA-r18 ENUMERATED {true} OPTIONAL, moSdt-r18 ENUMERATED {true} OPTIONAL, mtSdt-r18 ENUMERATED {true} OPTIONAL, nrOfPacketsSDT-Tx-r18 INTEGER (0..maxNrofPacketsSDTTxPerProcedure-1) OPTIONAL, nrOfPacketsSDT-Rx-r18 INTEGER (0.. maxNrofPacketsSDTTxPerProcedure-1) OPTIONAL, nrOfOctetsSDT-Tx-r18 INTEGER (0..maxNrofOctetsSDTTxPerProcedure-1) OPTIONAL, nrOfOctetsSDT-Rx-r18 INTEGER (0..maxNrofOctetsSDTRxPerProcedure-1) OPTIONAL ]] } SDT-CG-InformationCommon-r18 ::= SEQUENCE { nrofSDT-CG-Tx-r18 INTEGER (0..maxNrofSDTTxPerProcedure- 1) OPTIONAL, nrofSDT-CG-Rx-r18 INTEGER (0..maxNrofSDTRxPerProcedure- 1) OPTIONAL, nrofSDT-CG-Proc-r18 INTEGER (0..maxNrofSDTProcedure-1) OPTIONAL, nrofSSB-change-r18 INTEGER (0..maxNrofSSBchange-1) OPTIONAL } SDT-CG-ReportList-r18 ::= SEQUENCE (SIZE (1..maxSDTCGReport-r18)) OF SDT-CG- Report-r18 SDT-CG-Report-r18 ::= SEQUENCE { cellId-r18 CHOICE { cellGlobalId-r18 CGI-Info-Logging-r16, pci-arfcn-r18 PCI-ARFCN-NR-r16 }, sdt-CG-InformationCommon-r18 SDT-CG-InformationCommon-r18 OPTIONAL } [Irrelevant texts are omitted]

[0005] SDT-CG-Informationcommon field descriptionsnrofSDT-CG-Tx This field indicates the number of SDT transmission which is initiated via a configured grant based uplink transmission. nrofSDT-CG-Rx This field indicates the number of SDT reception followed after an initial uplink transmission using a configured grant. nrofSDT-CG-Proc This field indicates the number of SDT procedures which is initiated via a configured grant based uplink transmission. nrofSSB-change-r18 This field indicates the number of changes of SSB for CG transmissions during an SDT procedure [Irrelevant texts are omitted]

[0006] RA-Report field descriptions bestSS-SSB-RSRP-r18 This field indicates the highest SS-RSRP for RACH resource selection when SDT is initiated. cellID This field indicates the CGI of the cell in which the associated random access procedure was performed. contentionDetected This field is used to indicate that contention was detected for the transmitted preamble in the given random access attempt or not. This field is not included when the UE performs random access attempt is using contention free random-access resources or when the raPurpose is set to requestForOtherSI or when the RA attempt is a 2-step RA attempt and fallback to 4- step RA did not occur (i.e. fallbackToFourStepRA is not included). csi-RS-Index, csi-RS-Index-v1660 This field is used to indicate the CSI-RS index corresponding to the random access attempt. If the random access procedure is for beam failure recovery, the field indicates the NZP-CSI- RS-ResourceId. For CSI-RS index larger than maxNrofCSI-RS-ResourcesRRM-1, the index value is the sum of csi-RS-Index (without suffix) and csi-RS-Index-v1660. dlPathlossRSRP Measeured RSRP of the DL pathloss reference obtained at the time of RA_Type selection stage of the RA procedure as captured in TS 38.321 [3]. dlRSRPAboveThreshold In 4 step random access procedure, this field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold rsrp- ThresholdSSB in beamFailureRecoveryConfig in UL BWP configuration of UL BWP selected for random access procedure initiated for beam failure recovery; Otherwise, rsrp- ThresholdSSB in rach-ConfigCommon in UL BWP configuration of UL BWP selected for random access procedure. In 2 step random access procedure, this field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold msgA- RSRP-ThresholdSSB in rach-ConfigCommonTwoStepRA in UL BWP configuration of UL BWP selected for random access procedure. fallbackToFourStepRA This field indicates if a fallback indication in MsgB is received (according to TS 38.321 [3]) for the 2-step random access attempt. fallbackToRASDT This field indicates if a fallback to RACH based SDT is triggered in a configured grant initiated SDT procedure. intendedSIBs This field indicates the SIB(s) the UE wanted to receive as a result of the on demand SI request (when the RA procedure is a used as a SI request) initiated by the UE. That is, it indicates the one(s) of the SIB(s) in the SI message(s) requested to be broadcast that the UE was interested in. moSdt This field indicates if this SDT procedure is a MO-SDT procedure. mtSdt This field indicates if this SDT procedure is a MT-SDT procedure. msg1-SCS-From-prach-ConfigurationIndex This field is set by the UE with the corresponding SCS for CBRA as derived from the prach- ConfigurationIndex in RACH-ConfigGeneric when the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. msg1-SCS-From-prach-ConfigurationIndexCFRA This field is set by the UE with the corresponding SCS for CFRA as derived from the prach- ConfigurationIndex in RACH-ConfigGeneric when the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. msgA-PUSCH-PayloadSize This field indicates the size of the overall payload available in the UE buffer at the time of initiating the 2 step RA procedure. The value refers to the index of TS 38.321 [3], table 6.1.3.1-1, corresponding to the UE buffer size. msgA-RO-FDM This field indicates the number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance for the PRACH resources configured for 2-step CBRA.. msgA-RO-FDMCFRA This field indicates the number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance for the PRACH resources configured for 2-step CFRA. msgA-RO-FrequencyStart This field indicates the lowest resource block of the contention based random-access resources for 2-step CBRA in the random-access procedure. The indication has the form of the offset of the lowest PRACH transmissions occasion with respect to PRB 0 in the frequency domain. msgA-RO-FrequencyStartCFRA This field indicates the lowest resource block of the contention free random-access resources for the 2-step CFRA in the random-access procedure. The indication has the form of the offset of the lowest PRACH transmissions occasion with respect to PRB 0 in the frequency domain. msgA-SCS-From-prach-ConfigurationIndex This field is set by the UE with the corresponding SCS as derived from the msgA-PRACH- ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211

[0016] ) when the msgA- SubcarrierSpacing is absent and when only 2-step random-access resources are available in the UL BWP used in the random-access procedure; otherwise, this field is absent. nrOfPacketsSDT-Tx This field indicates the number of SDT packet transmitted in this SDT procedure. nrOfPacketsSDT-Rx This field indicates the number of SDT packet received in this SDT procedure. nrOfOctetsSDT-Tx This field indicates the number of SDT octets transmitted in this SDT procedure. nrOfOctetsSDT-Rx This field indicates the number of SDT octets received in this SDT procedure. nrOfTotPacketsSDT-Tx This field indicates the total number of SDT packets transmitted. nrOfToTPacketsSDT-Rx This field indicates the total number of SDT packets received. nrOfToTOctetsSDT-Tx This field indicates the total number of SDT octets transmitted. nrOfToTOctetsSDT-Rx This field indicates the total number of SDT octets received. numberOfPreamblesSentOnCSI-RS This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding CSI-RS. numberOfPreamblesSentOnSSB This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding SS / PBCH block. onDemandSISuccess This field is set to true when the RA report entry is included because of either msg1 based on demand SI request or msg3 based on demand SI request and if the on-demand SI request is successful. Otherwise, the field is absent. perRAAttemptInfoList This field provides detailed information about a random access attempt. perRACSI-RSInfoList This field provides detailed information about the successive random access attempts associated to the same CSI-RS. perRASSBInfoList This field provides detailed information about the successive random access attempts associated to the same SS / PBCH block. ra-InformationCommon This field is used to provide information on random access attempts. This field is mandatory present. raPurpose This field is used to indicate the RA scenario for which the RA report entry is triggered. The RA accesses associated to Initial access from RRC_IDLE, RRC re-establishment procedure, transition from RRC-INACTIVE. The indicator beamFailureRecovery is used in case of successful beam failure recovery related RA procedure in the SpCell [3]. The indicator reconfigurationWithSync is used if the UE executes a reconfiguration with sync. The indicator ulUnSynchronized is used if the random access procedure is initiated in a SpCell by DL or UL data arrival during RRC_CONNECTED when the timeAlignmentTimer is not running in the PTAG or if the RA procedure is initiated in a serving cell by a PDCCH order [3]. The indicator schedulingRequestFailure is used in case of SR failures [3]. The indicator noPUCCHResourceAvailable is used when the UE has no valid SR PUCCH resources configured [3]. The indicator requestForOtherSI is used for MSG1 based on demand SI request. The indicator msg3RequestForOtherSI is used in case of MSG3 based SI request. The field can also be used for the SCG-related RA-Report when the raPurpose is set to beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure and noPUCCHResourceAvailable. sdtFourStepRA This field indicates if this four-step RACH procedure is triggered for SDT purpose. sdtTwoStepRA This field indicates if this two-step RACH procedure is triggered for SDT purpose. spCellID This field is used to indicate the CGI of the SpCell of the cell group associated to the SCell in which the associated random access procedure was performed. If the UE performs RA procedure on a SCell associated to the MCG, then this field is set to the CGI of the PCell and if the UE performs RA procedure on a SCell associated to the SCG, then this field is set to the CGI of the PSCell. If the CGI of the PSCell is not available at the UE for the RA procedure performed on a SCell associated to the SCG or for the RA procedure on the PSCell, this field is set to the CGI of the PCell. Otherwise, the field is absent. ssb-Index This field is used to indicate the SS / PBCH index of the SS / PBCH block corresponding to the random access attempt. ssbsForSI-Acquisition This field indicates the SSB(s) (in the form of SSB index(es)) that the UE used to receive the requested SI message(s). The field is present if the purpose of the random access procedure was to request on-demand SI (i.e. if the raPurpose is set to requestForOtherSI or msg3RequestForOtherSI). Otherwise, the field is absent. ************************************************************************************************************* Enhancements to logged MDT Configuration – Enhancing area configuration The UE may be configured with an area configuration as part of the logged MDT configuration that indicates to the UE when the UE shall perform the logging of MDT measurements. In particular, the area configuration can indicate one of the following criteria for the UE to perform the logging of MDT measurements: - when the UE is camping in a cell supporting RACH-based SDT (including both 4-step RACH based SDT and 2-step RACH based SDT); - when the UE is camping in a cell supporting 4-step RACH based SDT; - when the UE is camping in a cell supporting 2-step RACH based SDT; - when the UE is camping in a cell supporting configured grant-based SDT; - when the UE is camping in a cell supporting configured grant-based SDT and 4-step RACH based SDT; or - when the UE is camping in a cell supporting configured grant-based SDT and 2-step RACH based SDT. In an exemplary implementation, the above methods impacting the ASN1 of the RRC specification may be represented in 3GPP TS 38.331 v17.3.0 as follows in the AreaConfiguration that conveys the configuration provided by the gNB. The implementation below only covers part of the proposed information elements / changes, with the proposed changes being highlighted in bold and underline. In this example, the gNB can configure the UE to perform logging in a cell according to whether the cell supports SDT or not in the area. In one option, the UE shall perform the logging of MDT measurements when the UE is camping in a cell supporting SDT in the area i.e. logCellType as part of the AreaConfig is set as “nonSdtCellOnly”. In another option, the UE shall perform the logging of MDT measurements when the UE is camping in a cell not supporting SDT in the area, i.e. logCellType as part of the AreaConfig is set as “nonSdtCellOnly”. In yet another option the UE logs all the cells in the area, i.e. logCellType as part of the AreaConfig is set as “both”. ************************************************************************************************************* - AreaConfiguration The AreaConfiguration indicates area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN is contained in plmn-IdentityList stored in VarLogMeasReport. AreaConfiguration information element -- ASN1START -- TAG-AREACONFIGURATION-START AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v1700 ::= SEQUENCE { areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v18xy ::= SEQUENCE { areaConfig-r18 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r18 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R logCellType-r18 ENUMERATED {sdtCellOnly,nonSdtCellOnly, both} } AreaConfig-r16 ::= CHOICE { cellGlobalIdList-r16 CellGlobalIdList-r16, trackingAreaCodeList-r16 TrackingAreaCodeList-r16, trackingAreaIdentityList-r16 TrackingAreaIdentityList-r16 } InterFreqTargetInfo-r16 ::= SEQUENCE { dl-CarrierFreq-r16 ARFCN-ValueNR, cellList-r16 SEQUENCE (SIZE (1..32)) OF PhysCellId OPTIONAL -- Need R } CellGlobalIdList-r16 ::= SEQUENCE (SIZE (1..32)) OF CGI-Info-Logging- r16 TrackingAreaCodeList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaCode TrackingAreaIdentityList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaIdentity-r16 TrackingAreaIdentity-r16 ::= SEQUENCE { plmn-Identity-r16 PLMN-Identity, trackingAreaCode-r16 TrackingAreaCode } -- TAG-AREACONFIGURATION-STOP -- ASN1STOP ************************************************************************************************************* Enhanced configuration for the target frequencies – In an exemplary implementation, the above methods impacting the ASN1 of the RRC specification may be represented in 3GPP TS 38.331 v17.3.0 as follows in the AreaConfiguration conveying the configuration provided by the gNB. The implementation has only covered part of the proposed information elements / changes, with the proposed changes being highlighted in bold and underline. In some embodiments, the UE can be configured with a neighbour frequency or neighbour cells-related configuration as part of the logged MDT configuration for which the UE shall perform the logging of MDT measurements. The configuration can include the field logCellType which indicates whether the cell to be measured supports SDT or not. Here, a neighbour frequency or neighbour cell refers to a frequency or cell that is neighbouring the frequency or cell that is used for the SDT. In an example, the field logCellType as part of the InterFreqTargetInfo can be set as “sdtCellOnly”, and the UE is configured to measure a neighbour frequency or neighbour cells if those cells support SDT. In another example, the field logCellType as part of the InterFreqTargetInfo can be set as “nonSdtCellOnly”, and the UE is configured to measure a neighbour frequency or neighbour cells if those cells don’t support SDT. In another example, the field logCellType as part of the InterFreqTargetInfo can be set as “both”, and the UE is configured to measure a neighbour frequency or neighbour cells regardless of whether they support SDT or not. ************************************************************************************************************* AreaConfiguration The AreaConfiguration indicates area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN is contained in plmn-IdentityList stored in VarLogMeasReport. AreaConfiguration information element -- ASN1START -- TAG-AREACONFIGURATION-START AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v1700 ::= SEQUENCE { areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v18xy ::= SEQUENCE { areaConfig-r18 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r18 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r18 OPTIONAL -- Need R } AreaConfig-r16 ::= CHOICE { cellGlobalIdList-r16 CellGlobalIdList-r16, trackingAreaCodeList-r16 TrackingAreaCodeList-r16, trackingAreaIdentityList-r16 TrackingAreaIdentityList-r16 } InterFreqTargetInfo-r16 ::= SEQUENCE { dl-CarrierFreq-r16 ARFCN-ValueNR, cellList-r16 SEQUENCE (SIZE (1..32)) OF PhysCellId OPTIONAL -- Need R } InterFreqTargetInfo-r18 ::= SEQUENCE { dl-CarrierFreq-r18 ARFCN-ValueNR, cellList-r18 SEQUENCE (SIZE (1..32)) OF PhysCellId OPTIONAL -- Need R logCellType-r18 ENUMERATED {sdtCellOnly,nonSdtCellOnly, both} } CellGlobalIdList-r16 ::= SEQUENCE (SIZE (1..32)) OF CGI-Info-Logging- r16 TrackingAreaCodeList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaCode TrackingAreaIdentityList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaIdentity-r16 TrackingAreaIdentity-r16 ::= SEQUENCE { plmn-Identity-r16 PLMN-Identity, trackingAreaCode-r16 TrackingAreaCode } -- TAG-AREACONFIGURATION-STOP -- ASN1STOP ************************************************************************************************************* Fig.3 is a flow chart illustrating a method according to various embodiments. The method in Fig.3 may be performed by a User Equipment (UE) or wireless device (e.g. the UE 512 or UE 600 as described later with reference to Figs. 5 and 6 respectively). The UE may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. In step 301 the UE obtains values of one or more metrics relating to a SDT procedure used for transmitting data to, and / or receiving data from, a first RAN node (e.g. a gNB) in the communication network. The SDT procedure may be a RA-SDT procedure or a CG-SDT procedure. The SDT procedure may be MO-SDT or MT-SDT. In step 303, the UE sends a measurement report comprising the obtained values to the first RAN node. During the SDT procedure the UE is in a dormant state with respect to the first RAN node. The dormant state may an idle state or an inactive state, such as a RRC idle state or a RRC inactive state. The method performed by the UE may further comprise, after step 303, receiving an updated SDT configuration from the first RAN node. The metrics may relate to successfully completed SDT procedures and / or unsuccessfully completed SDT procedures. The one or more metrics relating to the SDT procedure can comprise any one or more of: • a number of successfully completed SDT procedures; • a number of successfully completed RA-SDT procedures; • a number of successfully completed CG-SDT procedures; • a number of successfully completed MO-SDT procedures; • a number of successfully completed MT-SDT procedures; • a number of unsuccessfully completed SDT procedures; • a number of unsuccessfully completed RA-SDT procedures; • a number of unsuccessfully completed CG-SDT procedures; • a number of unsuccessfully completed MO-SDT procedures; • a number of unsuccessfully completed MT-SDT procedures; • a number or data volume of transmitted SDT transmissions / packets; • a number or data volume of received SDT transmissions / packets; • a number or data volume of transmitted or received SDT packets when using a configured grant or semi-persistent resource; • a number or data volume of transmitted or received SDT packets when using a dynamic grant or assignment; • a duration of one or more SDT procedures; • a number of SDT packets transmitted or received during one or more SDT procedures; • a number of SDT packets transmitted or received during one or more RA-SDT procedures; • a number of SDT packets transmitted or received during one or more CG-SDT procedures; • a SDT data volume transmitted or received during one or more SDT procedures; • a SDT data volume transmitted or received during one or more RA-SDT procedures; • a SDT data volume transmitted or received during one or more CG-SDT procedures; • a type of one or more SDT procedures; • a delay of transmitted or received SDT packets; • measurements of one or more downlink radio channel quality parameters. • a change of SSB during a CG-SDT procedure; • a number of transmitted SRS; • a number of transmitted uplink HARQ acknowledgements; • cell identifiers where the UE has performed transmission or reception using the SDT procedure; • RACH configurations which are applied by the UE. Step 301 can be performed during a measurement time window. Step 301 may be performed in response to a request from the first RAN node. The request may be received by the UE in RRC signalling. Step 301 may be performed according to a configuration provided by the first RAN node. In some embodiments, step 301 is performed if a trigger condition or criteria is met. The trigger condition or criteria can relate to one or more of a number of completed SDT procedures, a number of completed SDT transmissions, a number of completed SDT receptions, initiation of a NthSDT procedure, and triggering a NthRACH procedure. In some cases, the trigger condition or criteria can relate to an area in which the UE is located. For example, the trigger condition or criteria can be one of: the UE is camping in a cell supporting RA-SDT; the UE is camping in a cell supporting 4-step RA-SDT; the UE is camping in a cell supporting 2-step RA-SDT; the UE is camping in a cell supporting CG-SDT; the UE is camping in a cell supporting CG-SDT and 4-step RA-SDT; and the UE is camping in a cell supporting CG-SDT and 2-step RA-SDT. The values obtained in step 301 can be any of obtained per BWP; per cell; per SDT procedure; per RACH procedure; per radio bearer service; and / or per LCH. The values obtained in step 301 may further comprise values of the one or more metrics for a neighbour frequency or neighbouring cell to a frequency or cell used for the SDT procedure. Fig.4 is a flow chart illustrating a method according to various embodiments. The method in Fig.4 may be performed by a RAN network node (e.g. the RAN network node 510 or RAN network node 700 as described later with reference to Fig.5 and 7 respectively). The RAN node may perform the method in response to executing suitably formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium. The computer readable medium may be part of a computer program product. In step 401, the first RAN node receives a measurement report from a UE. The measurement report comprises values of one or more metrics relating to a SDT procedure the UE used for transmitting data to, and / or receiving data from, the first RAN node. Although not shown in Fig. 4, the method by the first RAN node can further comprise determining an updated SDT configuration based on the values of the one or more metrics comprised in the received measurement report. The first RAN node can send this updated SDT configuration to the UE. The SDT procedure may be a RA-SDT procedure or a CG-SDT procedure. The SDT procedure may be MO-SDT or MT-SDT. During the SDT procedure the UE is in a dormant state with respect to the first RAN node. The dormant state may an idle state or an inactive state, such as a RRC idle state or a RRC inactive state. The metrics in the measurement report may relate to successfully completed SDT procedures and / or unsuccessfully completed SDT procedures. The one or more metrics relating to the SDT procedure can comprise any one or more of: • a number of successfully completed SDT procedures; • a number of successfully completed RA-SDT procedures; • a number of successfully completed CG-SDT procedures; • a number of successfully completed MO-SDT procedures; • a number of successfully completed MT-SDT procedures; • a number of unsuccessfully completed SDT procedures; • a number of unsuccessfully completed RA-SDT procedures; • a number of unsuccessfully completed CG-SDT procedures; • a number of unsuccessfully completed MO-SDT procedures; • a number of unsuccessfully completed MT-SDT procedures; • a number or data volume of transmitted SDT transmissions / packets; • a number or data volume of received SDT transmissions / packets; • a number or data volume of transmitted or received SDT packets when using a configured grant or semi-persistent resource; • a number or data volume of transmitted or received SDT packets when using a dynamic grant or assignment; • a duration of one or more SDT procedures; • a number of SDT packets transmitted or received during one or more SDT procedures; • a number of SDT packets transmitted or received during one or more RA-SDT procedures; • a number of SDT packets transmitted or received during one or more CG-SDT procedures; • a SDT data volume transmitted or received during one or more SDT procedures; • a SDT data volume transmitted or received during one or more RA-SDT procedures; • a SDT data volume transmitted or received during one or more CG-SDT procedures; • a type of one or more SDT procedures; • a delay of transmitted or received SDT packets; • measurements of one or more downlink radio channel quality parameters. • a change of SSB during a CG-SDT procedure; • a number of transmitted SRS; • a number of transmitted uplink HARQ acknowledgements; • cell identifiers where the UE has performed transmission or reception using the SDT procedure; • RACH configurations which are applied by the UE. Prior to step 401, the first RAN node may send a request for a measurement report to the UE. This request can be sent in RRC signalling. The method by the first RAN node can further comprise sending a configuration relating to the measurement report to the UE. The values in the received measurement report can be values per BWP; per cell; per SDT procedure; per RACH procedure; per radio bearer service; and / or per LCH. The values in the received measurement report may further comprise values of the one or more metrics for a neighbour frequency or neighbouring cell to a frequency or cell used for the SDT procedure. Fig. 5 shows an example of a communication system 500 in accordance with some embodiments. In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as access network nodes 510a and 510b (which are interchangeably referred to as RAN network nodes 510 herein), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point (AP). Moreover, as will be appreciated by those of skill in the art, a RAN network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 502, including one or more network nodes 510 and / or core network nodes 508. Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O- CU user plane (O-CU-UP), a RAN intelligent controller (RIC) (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The access network nodes 510 facilitate direct or indirect connection of wireless devices (also referred to interchangeably herein as user equipment (UE)), such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. The access network nodes 510 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) NodeBs (gNBs)). Unless otherwise indicated, the general term ‘network node’ as used herein refers to access network nodes 510 and core network nodes 508. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The wireless devices / UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the access network nodes 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 512 and / or with other network nodes or equipment in the telecommunication network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 502. In the depicted example, the core network 506 connects the access network nodes 510 to one or more hosts, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one more core network nodes (e.g. core network node 508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices / UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and / or pre-recorded audio / video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system 500 of Fig. 5 enables connectivity between the wireless devices / UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g.6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive Internet of Things (IoT) services to yet further UEs. In some examples, the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-radio access technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UTRA (UMTS Terrestrial Radio Access) Network) New Radio – Dual Connectivity (EN-DC). In the example illustrated in Fig.5, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g. UE 512c and / or 512d) and access network nodes (e.g. access network node 510b). In some examples, the hub 514 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a Virtual Reality VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (IoT) devices. The hub 514 may have a constant / persistent or intermittent connection to the network node 510b. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g. UE 512c and / or 512d), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510b. In other embodiments, the hub 514 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Fig.6 shows a wireless device or UE 600 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a wireless device / UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle- mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A wireless device / UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g. a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g. a smart power meter). The UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a power source 608, a memory 610, a communication interface 612, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig.6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 610. The processing circuitry 602 may be implemented as one or more hardware-implemented state machines (e.g. in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 602 may include multiple central processing units (CPUs). The processing circuitry 602 may be operable to provide, either alone or in conjunction with other UE 600 components, such as the memory 610, to provide UE 600 functionality. For example, the processing circuitry 602 may be configured to cause the UE 602 to perform the methods as described with reference to Fig.3. In the example, the input / output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g. a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 608 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g. an electricity outlet), photovoltaic device, or power cell, may be used. The power source 608 may further include power circuitry for delivering power from the power source 608 itself, and / or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied. The memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems. The memory 610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a Universal Subscriber Identity Module (USIM) and / or integrated SIM (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 610 may allow the UE 600 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off- load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device- readable storage medium. The processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g. another UE or a network node in an access network). Each transceiver may include a transmitter 618 and / or a receiver 620 appropriate to provide network communications (e.g. optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g. antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately. In some embodiments, communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) or other Global Navigation Satellite System (GNSS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g. once every 15 minutes if it reports the sensed temperature), random (e.g. to even out the load from reporting from several sensors), in response to a triggering event (e.g. when moisture is detected an alert is sent), in response to a request (e.g. a user initiated request), or a continuous stream (e.g. a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence on the intended application of the IoT device in addition to other components as described in relation to the UE 600 shown in Fig.6. As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Fig.7 shows an access network node 700 or RAN network node 700 in accordance with some embodiments. As used herein, access network node or RAN network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other RAN network nodes or equipment or core network nodes, in a telecommunication network. Examples of access network nodes include, but are not limited to, access network nodes such as APs (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), Open RAN (O-RAN) nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A RAN network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of access network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g. Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The RAN network node 700 includes processing circuitry 702, a memory 704, a communication interface 706, and a power source 708, and / or any other component, or any combination thereof. The RAN network node 700 may be composed of multiple physically separate components (e.g. a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the RAN network node 700 comprises multiple separate components (e.g. BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the RAN network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g. separate memory 704 for different RATs) and some components may be reused (e.g. a same antenna 710 may be shared by different RATs). The RAN network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into RAN network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within RAN network node 700. The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other RAN network node 700 components, such as the memory 704, to provide network node 700 functionality. For example, the processing circuitry 702 may be configured to cause the RAN network node to perform the methods as described with reference to Fig.4. In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the radio frequency (RF) transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units. The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 702. The memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 702 and utilized by the RAN network node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated. The communication interface 706 is used in wired or wireless communication of signalling and / or data between network nodes, the access network, the core network, and / or a UE. As illustrated, the communication interface 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. The communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710. Radio front-end circuitry 718 comprises filters 720 and amplifiers 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 720 and / or amplifiers 722. The radio signal may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the access network node 700 does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown). The antenna 710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the RAN network node 700 through an interface or port. The antenna 710, communication interface 706, and / or the processing circuitry 702 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 710, the communication interface 706, and / or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source 708 provides power to the various components of RAN network node 700 in a form suitable for the respective components (e.g. at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the RAN network node 700 may be connectable to an external power source (e.g. the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the RAN network node 700 may include additional components beyond those shown in Fig.7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the RAN network node 700 may include user interface equipment to allow input of information into the RAN network node 700 and to allow output of information from the RAN network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the RAN network node 700. Fig. 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, a wireless device / UE, a core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g. a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the Open-RAN (O-RAN) Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 800 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808. The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802. Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units. Although the computing devices described herein (e.g. UEs, RAN network nodes, core network node, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

Claims

Claims 1. A method performed by a user equipment, UE, in a communication network, the method comprising: obtaining (301) values of one or more metrics relating to a Small Data Transmission, SDT, procedure used for transmitting data to, and / or receiving data from, a first Radio Access Network, RAN, node in the communication network; and sending (303), to the first RAN node, a measurement report comprising the obtained values.

2. A method as claimed in claim 1, wherein the UE is in a dormant state with respect to the first RAN node during the SDT procedure.

3. A method as claimed in claim 2, wherein the dormant state is an idle state or an inactive state.

4. A method as claimed in claim 2 or 3, wherein the dormant state is a Radio Resource Control, RRC, idle state or a RRC inactive state.

5. A method as claimed in any of claims 1-4, wherein the method further comprises: following the sending of the measurement report, receiving an updated SDT configuration from the first RAN node.

6. A method as claimed in any of claims 1-5, wherein the SDT procedure is one of Random Access SDT, RA-SDT, and Configured Grant SDT, CG-SDT.

7. A method as claimed in any of claims 1-6, wherein the SDT procedure is one of Mobile Originating SDT, MO-SDT, and Mobile Terminating SDT, MT-SDT.

8. A method as claimed in any of claims 1-7, wherein the metrics relate to successfully completed SDT procedures and / or unsuccessfully completed SDT procedures.

9. A method as claimed in any of claims 1-8, wherein the one or more metrics relating to the SDT procedure comprise any one or more of: ^ a number of successfully completed SDT procedures; ^ a number of successfully completed Random Access SDT, RA-SDT, procedures;^ a number of successfully completed Configured Grant SDT, CG-SDT, procedures; ^ a number of successfully completed Mobile Originating SDT, MO-SDT, procedures; ^ a number of successfully completed Mobile Terminating SDT, MT-SDT, procedures; ^ a number of unsuccessfully completed SDT procedures; ^ a number of unsuccessfully completed RA-SDT procedures; ^ a number of unsuccessfully completed CG-SDT procedures; ^ a number of unsuccessfully completed MO-SDT procedures; ^ a number of unsuccessfully completed MT-SDT procedures; ^ a number or data volume of transmitted SDT transmissions / packets; ^ a number or data volume of received SDT transmissions / packets; ^ a number or data volume of transmitted or received SDT packets when using a configured grant or semi-persistent resource; ^ a number or data volume of transmitted or received SDT packets when using a dynamic grant or assignment; ^ a duration of one or more SDT procedures; ^ a number of SDT packets transmitted or received during one or more SDT procedures; ^ a number of SDT packets transmitted or received during one or more RA-SDT procedures; ^ a number of SDT packets transmitted or received during one or more CG-SDT procedures; ^ a SDT data volume transmitted or received during one or more SDT procedures; ^ a SDT data volume transmitted or received during one or more RA-SDT procedures; ^ a SDT data volume transmitted or received during one or more CG-SDT procedures; ^ a type of one or more SDT procedures; ^ a delay of transmitted or received SDT packets; ^ measurements of one or more downlink radio channel quality parameters. ^ a change of Synchronisation Signal Block, SSB, during a CG-SDT procedure; ^ a number of transmitted Sounding Reference Signals, SRS; ^ a number of transmitted uplink Hybrid Automatic Repeat Request, HARQ, acknowledgements; ^ cell identifiers where the UE has performed transmission or reception using the SDT procedure; ^ Random Access Channel, RACH, configurations which are applied by the UE.

10. A method as claimed in any of claims 1-9, wherein the step of obtaining values (301) is performed during a measurement time window.

11. A method as claimed in any of claims 1-10, wherein the step of obtaining values (301) is performed in response to a request from the first RAN node.

12. A method as claimed in claim 11, wherein the request from the first RAN node is received in Radio Resource Control, RRC, signalling.

13. A method as claimed in any of claims 1-12, wherein the step of obtaining values (301) is performed according to a configuration provided by the first RAN node.

14. A method as claimed in any of claims 1-13, wherein the step of obtaining values (301) is performed if a trigger condition or criteria is met.

15. A method as claimed in claim 14, wherein the trigger condition or criteria relates to one or more of a number of completed SDT procedures, a number of completed SDT transmissions, a number of completed SDT receptions, initiation of a NthSDT procedure, and triggering a NthRandom Access Channel, RACH, procedure.

16. A method as claimed in claim 14, wherein the trigger condition or criteria relates to an area in which the UE is located.

17. A method as claimed in claim 14 or 16, wherein the trigger condition or criteria is one of: ^ the UE is camping in a cell supporting Random Access SDT, RA-SDT; ^ the UE is camping in a cell supporting 4-step RA-SDT; ^ the UE is camping in a cell supporting 2-step RA-SDT; ^ the UE is camping in a cell supporting Configured Grant-SDT, CG-SDT; ^ the UE is camping in a cell supporting CG-SDT and 4-step RA-SDT; ^ the UE is camping in a cell supporting CG-SDT and 2-step RA-SDT.

18. A method as claimed in any of claims 1-17, wherein the step of obtaining values (301) is performed any one or more of: ^ per bandwidth part, BWP; ^ per cell; ^ per SDT procedure;^ per Random Access Channel, RACH, procedure; ^ per radio bearer service; and ^ per Logical Channel, LCH.

19. A method as claimed in any of claims 1-18, wherein the step of obtaining (301) further comprises obtaining values of the one or more metrics for a neighbour frequency or neighbouring cell to a frequency or cell used for the SDT procedure.

20. A method performed by a first radio access network, RAN, node in a communication network, the method comprising: receiving (401), from a user equipment, UE, in the communication network, a measurement report comprising obtained values of one or more metrics relating to a Small Data Transmission, SDT, procedure used for transmitting data to, and / or receiving data from, the first RAN node.

21. A method as claimed in claim 20, wherein the method further comprises: determining an updated SDT configuration based on the values of the one or more metrics comprised in the received measurement report.

22. A method as claimed in claim 21, wherein the method further comprises: sending the updated SDT configuration to the UE.

23. A method as claimed in any of claims 20-22, wherein the UE is in a dormant state with respect to the first RAN node during the SDT procedure.

24. A method as claimed in claim 23, wherein the dormant state is an idle state or an inactive state.

25. A method as claimed in claim 23 or 24, wherein the dormant state is a Radio Resource Control, RRC, idle state or a RRC inactive state.

26. A method as claimed in any of claims 20-25, wherein the SDT procedure is one of Random Access SDT, RA-SDT, and Configured Grant SDT, CG-SDT.

27. A method as claimed in any of claims 20-26, wherein the SDT procedure is one of Mobile Originating SDT, MO-SDT, and Mobile Terminating SDT, MT-SDT.

28. A method as claimed in any of claims 20-27, wherein the metrics relate to successfully completed SDT procedures and / or unsuccessfully completed SDT procedures.

29. A method as claimed in any of claims 20-28, wherein the one or more metrics relating to the SDT procedure comprise any one or more of: ^ a number of successfully completed SDT procedures; ^ a number of successfully completed Random Access SDT, RA-SDT, procedures; ^ a number of successfully completed Configured Grant SDT, CG-SDT, procedures; ^ a number of successfully completed Mobile Originating SDT, MO-SDT, procedures; ^ a number of successfully completed Mobile Terminating SDT, MT-SDT, procedures; ^ a number of unsuccessfully completed SDT procedures; ^ a number of unsuccessfully completed RA-SDT procedures; ^ a number of unsuccessfully completed CG-SDT procedures; ^ a number of unsuccessfully completed MO-SDT procedures; ^ a number of unsuccessfully completed MT-SDT procedures; ^ a number or data volume of transmitted SDT transmissions / packets; ^ a number or data volume of received SDT transmissions / packets; ^ a number or data volume of transmitted or received SDT packets when using a configured grant or semi-persistent resource; ^ a number or data volume of transmitted or received SDT packets when using a dynamic grant or assignment; ^ a duration of one or more SDT procedures; ^ a number of SDT packets transmitted or received during one or more SDT procedures; ^ a number of SDT packets transmitted or received during one or more RA-SDT procedures; ^ a number of SDT packets transmitted or received during one or more CG-SDT procedures; ^ a SDT data volume transmitted or received during one or more SDT procedures; ^ a SDT data volume transmitted or received during one or more RA-SDT procedures; ^ a SDT data volume transmitted or received during one or more CG-SDT procedures; ^ a type of one or more SDT procedures; ^ a delay of transmitted or received SDT packets; ^ measurements of one or more downlink radio channel quality parameters. ^ a change of Synchronisation Signal Block, SSB, during a CG-SDT procedure;^ a number of transmitted Sounding Reference Signals, SRS; ^ a number of transmitted uplink Hybrid Automatic Repeat Request, HARQ, acknowledgements; ^ cell identifiers where the UE has performed transmission or reception using the SDT procedure; ^ Random Access Channel, RACH, configurations which are applied by the UE.

30. A method as claimed in any of claims 20-29, wherein the method further comprises: sending a request for a measurement report to the UE.

31. A method as claimed in claim 30, wherein the request is sent in Radio Resource Control, RRC, signalling.

32. A method as claimed in any of claims 20-31, wherein the method further comprises: sending a configuration relating to the measurement report to the UE.

33. A method as claimed in any of claims 20-32, wherein the values in the measurement report relate to SDT procedures: ^ per bandwidth part, BWP; ^ per cell; ^ per SDT procedure; ^ per Random Access Channel, RACH, procedure; ^ per radio bearer service; and ^ per Logical Channel, LCH.

34. A method as claimed in any of claims 20-33, wherein the received measurement report further comprises values of the one or more metrics for a neighbour frequency or neighbouring cell to a frequency or cell used for the SDT procedure.

35. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-34.

36. A user equipment, UE, configured to perform the method of any of claims 1-19.

37. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of claims 1-19.

38. A first radio access network, RAN, node, configured to perform the method of any of claims 20-34.

39. A first radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first RAN node is operative to perform the method of any of claims 20-34.

Images