Random access reporting techniques

Abstract

Techniques for a communication device to indicate assistance information to a network device are described. An example wireless communication method includes transmitting, by a communication device, information stored by the communication device, where the information includes a suspend indication indicating whether the communication device has received a suspend notification of a counter associated with a power climb for a random access attempt, and wherein the rule specifies whether the information includes a pending indication and / or content related to the pending indication included in the information.

Description

Technical Field

[0001] This document generally relates to digital wireless communication. Background Technology

[0002] Mobile communication technologies are driving the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies need to support a wider range of use case characteristics and meet more complex, granular access requirements and flexibility.

[0003] LTE (Long Term Evolution) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE-Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system (5G) iterates and upgrades upon the LTE and LTE-A wireless standards, aiming to support higher data rates, a larger number of connections, ultra-low latency, high reliability, and meet the needs of other emerging services. Summary of the Invention

[0004] The technology disclosed is used to indicate information and related signaling formats to introduce auxiliary information to help the network (NW) obtain the preamble transmission power used in the random access procedure (RA procedure) and to introduce a triggering event that triggers a scheduling request (SR) in the RA information stored by the UE, so that the NW can know the root cause of the improper information due to the SR configuration.

[0005] A first example wireless communication method includes: transmitting information stored in the communication device via a communication device, wherein the information includes a suspend indication indicating whether the communication device has received a suspend notification of a counter associated with power ramping for a random access attempt, and wherein a rule specifies whether the information includes the suspend indication and / or content related to the suspend indication included in the information. In some embodiments, the information includes a suspend indication indicating whether a suspend notification of a power ramp counter has been received from a lower layer of the communication device for a random access attempt, wherein the power ramp counter suspend notification indicates that the communication device has suspended the counter associated with power ramping for the random access attempt, and wherein a rule specifies whether the information includes the suspend indication and / or content related to the suspend indication included in the information.

[0006] In some implementations, the rule specifies that the suspend indication includes a message indicating that the communication device has received a suspend notification for a counter associated with power ramp-up. In some implementations, the rule specifies that the suspend indication includes a bit value including a first value indicating that a suspend notification with a counter having power ramp-up has been received and the communication device has suspended the counter associated with power ramp-up; and the rule specifies that the suspend indication includes a bit value including a second value indicating that a suspend notification with a counter having power ramp-up has been received and the communication device has not yet suspended the counter associated with power ramp-up. In some implementations, the method further includes storing the suspend indication in response to performing a random access attempt for a random access procedure.

[0007] In some implementations, the rule specifies that a suspend indication exists in the information indicating that a suspend notification for the power ramp counter has been received from the lower layer, and that the communication device has suspended the counter associated with the power ramp. In some implementations, the rule specifies that the suspend indication includes a bit value including a first value indicating that a suspend notification for the power ramp counter has been received from the lower layer, and that the communication device has suspended the counter associated with the power ramp; and the rule specifies that the suspend indication includes a bit value including a second value indicating that a suspend notification for the power ramp counter has not yet been received from the lower layer, and that the communication device has not yet suspended the counter associated with the power ramp. In some implementations, the method further includes: in response to performing a random access attempt for a random access procedure, the communication device stores the suspend indication.

[0008] The second example wireless communication method includes: transmitting information stored in the communication device via a communication device, wherein the information includes a suspension count, the suspension count indicating the number of times a transmission beam for a random access attempt to perform a random access procedure has received a suspension indication notification, wherein the suspension indication indicates that the communication device has suspended a counter associated with power ramping, and wherein a rule specifies whether the information includes the suspension count and / or content related to the suspension count included in the information.

[0009] In some implementations, the rule specifies that the value of a field included in the information indicates the number of pending connections received by the communication device. In some implementations, the rule specifies that the absence of a field associated with the number of pending connections in the information indicates that the number of pending connections is equal to zero. In some implementations, the method further includes storing the number of pending connections in response to performing a random access attempt for a random access procedure.

[0010] In some implementations, the rule specifies that the value of a field included in the information indicates the number of suspension notifications received by the lower layer of the communication device for suspending the power ramp-up counter. In some implementations, the rule specifies that the absence of a field associated with the number of suspensions in the information indicates that the number of power ramp-up counter suspension notifications received by the communication device from the lower layer is equal to zero. In some implementations, the method further includes: in response to performing a random access attempt for a random access procedure, the communication device storing the number of suspension notifications received by the lower layer of the communication device for suspending the power ramp-up counter.

[0011] A third example wireless communication method includes: transmitting information stored in the communication device via a communication device, wherein the information includes a hangup count, the hangup count indicating the number of times a hangup indication notification has been received during a random access procedure performed for the communication device, wherein the hangup indication indicates that the communication device has suspended a counter associated with power ramp-up, and wherein a rule specifies whether the information includes the hangup count and / or content related to the hangup count included in the information.

[0012] In some implementations, the rule specifies that the value of a field included in the information indicates the number of pending connections received by the communication device. In some implementations, the rule specifies that the absence of a field associated with the number of pending connections in the information indicates that the number of pending connections is zero. In some implementations, the method further includes storing the number of pending connections in response to performing a random access procedure.

[0013] In some implementations, the rule specifies that the value of the field included in the information indicates the number of suspension notifications for suspending the power ramp-up counter received by the lower layer of the communication device. In some implementations, the rule specifies that if no associated field exists, the number of power ramp-up counter suspension notifications received by the communication device from the lower layer is equal to zero. In some implementations, the method further includes: in response to performing a random access procedure, the communication device storing the suspension notifications for suspending the power ramp-up counter received by the lower layer of the communication device.

[0014] The fourth example wireless communication method includes: transmitting information stored in the communication device via a communication device, wherein the information includes a field indicating an event that triggers a scheduling request, and wherein the information includes the field indicating that the scheduling request was triggered due to beam fault recovery (BFR) or due to listen-before-speak (LBT).

[0015] In some implementations, the information is public random access information for one or more random access attempts. In some implementations, the information is a random access report, which includes random access information used in the random access procedure. In some implementations, the method further includes: in response to failure to execute a scheduling request or in response to the absence of one or more resources for executing the scheduling request, the communication device stores the field.

[0016] In another exemplary aspect, the above-described method is implemented in the form of processor-executable code and stored in a non-transitory computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the method described in this patent document.

[0017] In yet another exemplary embodiment, a device configured or operable to perform the methods described above is disclosed.

[0018] The above and other aspects, and their implementation methods, are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0019] Figure 1 The procedure for requesting or reporting UE information stored by the user equipment (UE) is illustrated.

[0020] Figures 2-5 An exemplary flowchart for transmitting information stored in a communication device is shown.

[0021] Figure 6 Examples of wireless communication including a base station (BS) and a user equipment (UE) based on some implementations of the disclosed technology are shown.

[0022] Figure 7 An exemplary block diagram of a hardware platform is shown, which may be part of a network device or a communication device. Detailed Implementation

[0023] The network (NW) can perform random access channel (RACH) configuration optimization by receiving random access (RA) related information, which is stored by the user equipment (UE) in one or more of the following reports: random access (RA) report, radio link failure (RLF) report, successful handover report (SHR), and / or connection failure report (CEF). In this patent document, NW can refer to a base station, a base station functional entity (e.g., an operation, management, and maintenance (OAM) entity), or an NW node. The base station or NW node receiving UE information can be connected to different NW nodes or core network nodes. After receiving information reported by the UE, the base station / NW node can forward the received information to different NW nodes or to one or more functional entities within the base station / NW, thereby processing, analyzing, and performing optimization (if necessary).

[0024] One technical feature that the NW needs to optimize includes RACH configuration (e.g., parameters related to preamble transmission power). If the NW can understand or determine the preamble transmission power used for each RA attempt, it can determine whether the maximum transmission power has been reached during the RA process, and which RA attempt that maximum transmission power was used for. If the maximum transmission power has already been used early on, this may mean that the transmission power configuration is inappropriate (e.g., the power step size is set too large) or that RA resources are too limited, which can be determined based on other RA-related information collected. The NW can perform corresponding RACH optimizations based on the preamble transmission power information obtained from the stored RA information, such as adjusting the preamble transmission step size or adjusting the initial preamble transmission power.

[0025] The UE stores RA-related information in the order of the attempted beams, and for consecutive RA attempts within the same beam (SSB or CSI-RS), for example, the UE can create new entries when the selected beam used for preamble transmission changes (e.g., as shown below). perRASSBInfoList-r16 or perRACSI-RSInfoList-r16 Initially, the UE could only gradually increase the transmission power when the selected beam remained unchanged. Then, by analyzing each RA attempt information stored in each entry of the RA report, the NW could obtain the order of the attempted beams, beam changes, the preamble transmission power ramp-up time, and the number of power ramps that occurred during an RA process. Simultaneously, using the preamble transmission power parameters configured by the NW (e.g., power ramp-up step size), the NW could obtain the transmission power used for each preamble transmission.

[0026] However, due to the introduction of Listen-Before-Speak (LBT) and power suspend indication in unlicensed spectrum, UE preamble transmission power control may depend on several factors, such as whether the beam used for the preamble has changed, whether a preamble transmission counter suspend notification has been received from the lower layer, and whether an LBT failure indication has been received from the lower layer. Currently, the UE will only gradually increase the preamble transmission power if: (1) the UE has not yet received a power ramp counter suspend notification from the lower layer; (2) the UE has not received an LBT failure indication from the lower layer for the last random access preamble transmission; and (3) the selected SSB or CSI-RS is consistent with the selection in the last random access preamble transmission. Therefore, one technical problem is that if the NW does not receive additional information from the UE regarding whether the UE has received a power ramp counter indication suspend notification and whether the UE has received an LBT failure indication for the last preamble transmission, the NW may not be able to obtain or determine the correct preamble transmission power intended for the NW. Therefore, this patent document describes one or more technical solutions related to auxiliary information that helps NW obtain preamble transmission power.

[0027] Another technical issue related to RACH optimization is further identifying the root cause of the RACH procedure. Currently, the UE can store the RA purpose that triggers the random access procedure, including RAs triggered due to scheduling request (SR) failure or due to an SR being triggered but without a valid PUCCH configuration. However, when the RA procedure is triggered due to SR failure or due to an SR being triggered but without PUCCH resources, the root cause may be more related to improper SR configuration than to RACH configuration. If a dedicated SR configuration has been configured for LBT or beam fault recovery (BFR), the UE may not need to use valuable RA resources to request uplink (UL) resources. However, the RA information stored by the UE lacks information about the reason for triggering the SR, making it difficult for the NW to know how to optimize the SR configuration. Therefore, this patent document describes one or more technical solutions related to auxiliary information for identifying SRs triggered during BFR or LBT procedures.

[0028] The example technologies described in this patent document can be applied to non-terrestrial networks (NTN), terrestrial networks (TN), or air-to-ground (ATG) networks.

[0029] The example headings in the following sections are for illustrative purposes only and do not limit the scope of the claimed subject matter in any way. Therefore, one or more features of one example section may be combined with one or more features of another example section. Furthermore, the term "5G" is used for ease of explanation, but the technologies disclosed in this document are not limited to 5G technology and can also be applied to wireless systems employing other protocols.

[0030] I. Introduction to UE Information Request and UE Information Response Figure 1 The procedure for requesting or reporting UE information stored by a UE is illustrated, where the UE information may include RA information. The network uses the UE information procedure to request UE report information. In this example, this is achieved by including one or more request indications... UEInformationRequest In the message, the NW can use this message to request the UE to report one or more reports stored by the UE. For example, when including ra-ReportReq-r16 At this time, the UE is requested to report stored RACH reports (if any available RACH reports are stored in the UE). Each information element (IE) included in this message can be used to request the UE to report the corresponding report or information, and UEInformationRequest The IE field description provides a detailed description. Based on the NW request, the UE can access the system as described in this patent. UEInformationResponse The message reports the stored information to NW.

[0031] – UEInformationRequest Network usage UEInformationRequest Message retrieval retrieves information from the UE.

[0032] Signaling radio bearer: SRB1 RLC-SAP: AM Logical Channel: DCCH Direction: From Network to UE UEInformationRequest message -- ASN1START -- TAG-UEINFORMATIONREQUEST-START UEInformationRequest-r16 ::=SEQUENCE { rrc-TransactionIdentifierRRC-TransactionIdentifier, criticalExtensionsCHOICE { ueInformationRequest-r16UEInformationRequest-r16-IEs, criticalExtensionsFutureSEQUENCE {} } } UEInformationRequest-r16-IEs ::= SEQUENCE { idleModeMeasurementReq-r16ENUMERATED{true}OPTIONAL, -- Need N logMeasReportReq-r16ENUMERATED {true}OPTIONAL, -- Need N connEstFailReportReq-r16ENUMERATED {true}OPTIONAL, -- Need N ra-ReportReq-r16ENUMERATED {true}OPTIONAL, -- Need N rlf-ReportReq-r16ENUMERATED {true}OPTIONAL, -- Need N mobilityHistoryReportReq-r16ENUMERATED {true}OPTIONAL, -- Need N lateNonCriticalExtensionOCTET STRINGOPTIONAL, nonCriticalExtensionUEInformationRequest-v1700-IEsOPTIONAL } UEInformationRequest-v1700-IEs ::= SEQUENCE { successHO-ReportReq-r17ENUMERATED {true}OPTIONAL, -- Need N coarseLocationRequest-r17ENUMERATED {true}OPTIONAL, -- Need N nonCriticalExtensionSEQUENCE {}OPTIONAL } -- TAG-UEINFORMATIONREQUEST-STOP -- ASN1STOP

[0033] II. Information regarding RACH reports Based on current technology, the parameters shown below can be configured for the RA procedure to help the UE adjust the transmission power used for uplink transmission (e.g., preamble): PREAMBLE_POWER_RAMPING_COUNTER: This is used to count the number of power ramps during the RA process. PREAMBLE_POWER_RAMPING_STEP: Power ramp-up factor used for preamble transmission. For each power ramp-up, the UE increases the current preamble transmission power by the indicated power ramp-up factor until it reaches the maximum permissible preamble transmission power as indicated in PCMAX.

[0034] PREAMBLE_RECEIVED_TARGET_POWER: Initial random access preamble power PCMAX: Can also refer to Pcmax,f,c, the configured maximum UE output power of the selected carrier. For RA information associated with a completed RA procedure, the UE stores the RA information in an RA report. Each RA report may contain one or more of the following fields: A RA-InformationCommon field is used to indicate some public RA information that may be included in RA reports, RLF reports, or SHRs.

[0035] An RA purpose field is used to indicate the purpose of the RA process. A cell identity field, used to indicate the cell where the RA procedure takes place. A SpCell indicator indicates the SpCell (e.g., the PCCell of the primary cell group or the PSCell of the secondary cell group) when the RA procedure occurs in the cell.

[0036] The RA-InformationCommon contains one or more Information Elements (IEs) that indicate the RA resource configuration used during the RA process and performance-related information for each RA attempt. The standard specifies that the UE can store RA-related information in the order of the attempted beams, and for consecutive RA attempts within the same beam (SSB or CSI-RS), i.e., the UE will create a new entry when the selected beam used for preamble transmission changes (e.g., as shown in ASN.1 below). perRASSBInfoList-r16 or perRACSI-RSInfoList-r16 For each entry in the same beam, the UE stores information related to each RA attempt. PerRASSBInfo-r16 (If the selected beam is SSB) or perRACSI-RSInfo-r16 (If the selected beam is CSI-RS) information includes, for example, the beam index and each RA attempt information (e.g., indicators indicating whether contention was detected in this attempt, whether the RSRP of the selected beam is higher than the RSRP threshold configured for beam selection, etc.). Since the UE can only gradually increase the transmission power when the selected beam does not change, by analyzing each RA attempt information in each entry of the RA report, the NW can obtain the order of the attempted beams, beam changes, the preamble transmission power ramp-up time, and the number of power ramps that occurred in a RA process. Simultaneously, using the preamble transmission power parameters configured by the NW (e.g., power ramp-up step size), the NW can obtain the transmission power used for each preamble transmission.

[0037] RA information can be stored in RA reports, RLF reports, successful handover reports, or connection failure reports. Stored RA information can be reported to the NW through the UE information request and UE information response procedures. Below is an example ASN.1 of UE-stored RA information: –UEInformationResponse UE usage UEInformationResponse Message passing information about network requests.

[0038] Signaling radio bearer: SRB1 or SRB2 (when including recorded measurement information) RLC-SAP: AM Logical Channel: DCCH Direction: From UE to Network The bold italicized text shown below indicates the RA information content stored in the RA report. RA-InformationCommon is public RA information that can be stored in RA reports, RLF reports, or successful HO reports. PerRAInfoList (part of RA-InformationCommon), which stores information related to all RA attempts, can also be included in connection failure reports.

[0039] UEInformationResponse message -- ASN1START -- TAG-UEINFORMATIONRESPONSE-START UEInformationResponse-r16 ::=SEQUENCE { rrc-TransactionIdentifierRRC-TransactionIdentifier, criticalExtensionsCHOICE { ueInformationResponse-r16UEInformationResponse-r16-IEs, criticalExtensionsFutureSEQUENCE {} } } UEInformationResponse-r16-IEs ::=SEQUENCE { measResultIdleEUTRA-r16MeasResultIdleEUTRA-r16OPTIONAL, measResultIdleNR-r16MeasResultIdleNR-r16OPTIONAL, logMeasReport-r16LogMeasReport-r16OPTIONAL, connEstFailReport-r16ConnEstFailReport-r16OPTIONAL, ra-ReportList-r16RA-ReportList-r16OPTIONAL, rlf-Report-r16RLF-Report-r16OPTIONAL, mobilityHistoryReport-r16MobilityHistoryReport-r16OPTIONAL, lateNonCriticalExtensionOCTET STRINGOPTIONAL, nonCriticalExtensionUEInformationResponse-v1700-IEsOPTIONAL } UEInformationResponse-v1700-IEs ::=SEQUENCE { successHO-Report-r17SuccessHO-Report-r17OPTIONAL, connEstFailReportList-r17ConnEstFailReportList-r17OPTIONAL, coarseLocationInfo-r17OCTET STRINGOPTIONAL, nonCriticalExtensionSEQUENCE {}OPTIONAL } LogMeasReport-r16 ::=SEQUENCE { absoluteTimeStamp-r16AbsoluteTimeInfo-r16, traceReference-r16TraceReference-r16, traceRecordingSessionRef-r16OCTET STRING (SIZE (2)), tce-Id-r16OCTET STRING (SIZE (1)), logMeasInfoList-r16LogMeasInfoList-r16, logMeasAvailable-r16ENUMERATED {true}OPTIONAL, logMeasAvailableBT-r16ENUMERATED {true}OPTIONAL, logMeasAvailableWLAN-r16ENUMERATED {true}OPTIONAL, ... } LogMeasInfoList-r16 ::=SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OFLogMeasInfo-r16 LogMeasInfo-r16 ::=SEQUENCE { locationInfo-r16LocationInfo-r16OPTIONAL, relativeTimeStamp-r16INTEGER (0..7200), servCellIdentity-r16CGI-Info-Logging-r16OPTIONAL, measResultServingCell-r16MeasResultServingCell-r16OPTIONAL, measResultNeighCells-r16SEQUENCE { measResultNeighCellListNRMeasResultListLogging2NR-r16OPTIONAL, measResultNeighCellListEUTRAMeasResultList2EUTRA-r16OPTIONAL }, anyCellSelectionDetected-r16ENUMERATED {true}OPTIONAL, ..., [[ inDeviceCoexDetected-r17ENUMERATED {true}OPTIONAL ]] } ConnEstFailReport-r16 ::=SEQUENCE { measResultFailedCell-r16MeasResultFailedCell-r16, locationInfo-r16LocationInfo-r16OPTIONAL, measResultNeighCells-r16SEQUENCE { measResultNeighCellListNRMeasResultList2NR-r16OPTIONAL, measResultNeighCellListEUTRAMeasResultList2EUTRA-r16OPTIONAL }, numberOfConnFail-r16INTEGER (1..8), perRAInfoList-r16PerRAInfoList-r16, timeSinceFailure-r16TimeSinceFailure-r16, ... } ConnEstFailReportList-r17 ::= SEQUENCE (SIZE (1..maxCEFReport-r17))OF ConnEstFailReport-r16 MeasResultServingCell-r16 ::=SEQUENCE { resultsSSB-CellMeasQuantityResults, resultsSSBSEQUENCE{ best-ssb-IndexSSB-Index, best-ssb-ResultsMeasQuantityResults, numberOfGoodSSBINTEGER (1..maxNrofSSBs-r16) }OPTIONAL } MeasResultFailedCell-r16 ::=SEQUENCE { cgi-InfoCGI-Info-Logging-r16, measResult-r16SEQUENCE { cellResults-r16SEQUENCE{ resultsSSB-Cell-r16MeasQuantityResults }, rsIndexResults-r16SEQUENCE{ resultsSSB-Indexes-r16ResultsPerSSB-IndexList } } } RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA- Report-r16 RA-Report-r16 ::=SEQUENCE { cellId-r16CHOICE { cellGlobalId-r16CGI-Info-Logging-r16, pci-arfcn-r16PCI-ARFCN-NR-r16 }, ra-InformationCommon-r16RA-InformationCommon-r16OPTIONAL, raPurpose-r16ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, msg3RequestForOtherSI-r17, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, ..., [[ spCellID-r17CGI-Info-Logging-r16OPTIONAL ]] } RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks- 1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25, kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks- 1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlo cks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25, kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations) OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBloc ks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB- IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo- v1660 PerRAInfo-r16 ::=CHOICE { perRASSBInfoList-r16 PerRASSBInfo-r16, perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 } PerRASSBInfo-r16 ::=SEQUENCE { ssb-Index-r16 SSB-Index, numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 } PerRACSI-RSInfo-r16 ::=SEQUENCE { csi-RS-Index-r16 CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::=SEQUENCE { csi-RS-Index-v1660 INTEGER (1..96) OPTIONAL } PerRAAttemptInfoList-r16 ::=SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::=SEQUENCE { contentionDetected-r16 BOOLEAN OPTIONAL, dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, ..., [[ fallbackToFourStepRA-r17 ENUMERATED {true} OPTIONAL ]] } SIB-Type-r17 ::= ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare6, spare5, spare4, spare3, spare2, spare1} RLF-Report-r16 ::=CHOICE { nr-RLF-Report-r16SEQUENCE { measResultLastServCell-r16MeasResultRLFNR-r16, measResultNeighCells-r16SEQUENCE { measResultListNR-r16MeasResultList2NR-r16OPTIONAL, measResultListEUTRA-r16MeasResultList2EUTRA-r16OPTIONAL }OPTIONAL, c-RNTI-r16RNTI-Value, previousPCellId-r16CHOICE { nrPreviousCell-r16CGI-Info-Logging-r16, eutraPreviousCell-r16CGI-InfoEUTRALogging }OPTIONAL, failedPCellId-r16CHOICE { nrFailedPCellId-r16CHOICE { cellGlobalId-r16CGI-Info-Logging-r16, pci-arfcn-r16PCI-ARFCN-NR-r16 }, eutraFailedPCellId-r16CHOICE { cellGlobalId-r16CGI-InfoEUTRALogging, pci-arfcn-r16PCI-ARFCN-EUTRA-r16 } }, reconnectCellId-r16CHOICE { nrReconnectCellId-r16CGI-Info-Logging-r16, eutraReconnectCellId-r16CGI-InfoEUTRALogging }OPTIONAL, timeUntilReconnection-r16TimeUntilReconnection-r16OPTIONAL, reestablishmentCellId-r16CGI-Info-Logging-r16OPTIONAL, timeConnFailure-r16INTEGER (0..1023)OPTIONAL, timeSinceFailure-r16TimeSinceFailure-r16, connectionFailureType-r16ENUMERATED {rlf, hof}, rlf-Cause-r16ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, lbtFailure-r16, bh-rlfRecoveryFailure, t312-expiry-r17, spare1}, locationInfo-r16LocationInfo-r16OPTIONAL, noSuitableCellFound-r16ENUMERATED {true}OPTIONAL, ra-InformationCommon-r16RA-InformationCommon-r16OPTIONAL, ..., [[ csi-rsRLMConfigBitmap-v1650BIT STRING (SIZE (96))OPTIONAL ]], [[ lastHO-Type-r17ENUMERATED {cho, daps, spare2, spare1}OPTIONAL, timeConnSourceDAPS-Failure-r17TimeConnSourceDAPS-Failure-r17OPTIONAL, timeSinceCHO-Reconfig-r17TimeSinceCHO-Reconfig-r17OPTIONAL, choCellId-r17CHOICE { cellGlobalId-r17CGI-Info-Logging-r16, pci-arfcn-r17PCI-ARFCN-NR-r16 }OPTIONAL, choCandidateCellList-r17ChoCandidateCellList-r17OPTIONAL ]] }, eutra-RLF-Report-r16SEQUENCE { failedPCellId-EUTRACGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-r16OCTET STRING, [[ measResult-RLF-Report-EUTRA-v1690OCTET STRINGOPTIONAL ..., ]] } } SuccessHO-Report-r17 ::=SEQUENCE { sourceCellInfo-r17SEQUENCE { sourcePCellId-r17CGI-Info-Logging-r16, sourceCellMeas-r17MeasResultSuccessHONR-r17OPTIONAL, rlf-InSourceDAPS-r17ENUMERATED {true}OPTIONAL }, targetCellInfo-r17SEQUENCE { targetPCellId-r17CGI-Info-Logging-r16, targetCellMeas-r17MeasResultSuccessHONR-r17OPTIONAL }, measResultNeighCells-r17SEQUENCE { measResultListNR-r17MeasResultList2NR-r16OPTIONAL, measResultListEUTRA-r17MeasResultList2EUTRA-r16OPTIONAL }OPTIONAL, locationInfo-r17LocationInfo-r16OPTIONAL, timeSinceCHO-Reconfig-r17TimeSinceCHO-Reconfig-r17OPTIONAL, shr-Cause-r17SHR-Cause-r17OPTIONAL, ra-InformationCommon-r17RA-InformationCommon-r16OPTIONAL, upInterruptionTimeAtHO-r17UPInterruptionTimeAtHO-r17OPTIONAL, c-RNTI-r17RNTI-ValueOPTIONAL, ... } … --TAG-UEINFORMATIONRESPONSE-STOP -- ASN1STOP

[0040]

[0041]

[0042] III. Example techniques for transmitting or receiving RA information In some implementations, the techniques described below can allow the UE to collect RA information using the following example steps: Step 1: When completing the RA procedure, the UE stores the relevant RA information. Step 2 (optional): The UE reports the availability to the NW. Step 3: NW requests the UE to report one or more reports stored in the UE's database. Step 4: The UE transmits the requested report to the NW (if the report is available on the UE side). For step 1, the RA process can succeed or fail. RA-related information can be stored in RA reports, RLF reports, CEF reports, SHR reports, successful PSCell change / addition reports (SPR reports), or multiple reports, thereby collecting information related to small data transfers (such as SDT reports).

[0043] For step 2, if the RA information is stored in the RLF report, the UE can indicate to the NW that an RLF report is available for capture using a single indicator. If the RA information is stored in one or more CEF reports, the UE can indicate to the NW that one or more CEF reports are available for capture using a single indicator. If the RA information is stored in the SHR, the UE can indicate to the NW that an SHR is available using a single indicator. If the RA information is stored in the SPR, the UE can indicate to the NW that an SHR is available for capture using a single indicator. If the RA information is stored in the SDT report, the UE can indicate to the NW that an SDT report is available for capture using a single indicator. If the RA information is stored in the RA report, the UE can indicate to the NW that one or more RA reports are available for capture using a single indicator. In some examples, when the RA information is stored in the RA report, the UE does not need to report the availability of the RA report to the NW.

[0044] For step 3, NW can use individual bit requests as discussed in steps 1 / 2, or new reports that can be introduced to store RA information (e.g., reports for collecting information related to small data transfers). In some examples, UEInformationRequest Used to request the UE to report reports or information stored by the UE.

[0045] For step 4, upon receiving a request from the NW, the UE can transmit a report of the NW request to the NW (if available). The stored RA information can then be transmitted to the NW as part of the report. In some examples, the message carrying the report is... UEInformationResponse information.

[0046] Upon receiving a message carrying the requested report, the receiving node can forward the received report to the relevant NW node (if necessary) based on the cell identity included in the report. Both the receiving node and the forwarding node can analyze the report and perform optimizations (e.g., optimize RACH configuration).

[0047] III.A. Auxiliary information used for transmission power calculation For step 1: As described in the previous section, the RA information stored in the UE requires auxiliary information, and this auxiliary information needs to be transmitted to the NW through the UE so that the NW can correctly obtain the preamble transmission power. The RA information can be transmitted to the NW by the UE using step 4 above. The auxiliary information can be stored in the UE as part of the RA information, and can be one or more of the following information. The terms "Alt" and "Opt" in this patent document can refer to alternatives and optional solutions, respectively.

[0048] Alt1: An indication of each RA attempt (or one RA attempt), used to indicate whether a power ramp counter hang notification has been received from the lower layer for an RA attempt. An example of an encoding scheme is shown below, which can be used to indicate this information: ○Opt1: Uses a one-bit indicator, where 1 can indicate that a power ramp counter hang notification has been received from the lower layer for this RA attempt, and zero can indicate the opposite meaning. Conversely, 0 indicates the opposite meaning.

[0049] ○Opt2: The presence of this field indicates that an attempt has been made to receive a power ramp counter suspension notification from a lower layer for this RA; otherwise, the field does not exist.

[0050] Alt2: The number of power ramp counter hang notifications received from lower layers for each beam used in the RA process. The beam type can be SSB or CSI-RS.

[0051] In another example, this information can be statistically analyzed for each RA process (or for a single RA process).

[0052] Alt3: Number of power climbs during the RA process, or number of power climbs within the beam (SSB or CSI-RS) used during the RA process. Alt4: The maximum transmission power used during the RA process (in another example, this can be rephrased as the transmission power used for the last preamble transmission during the RA process). Alt5: The transmission power level used for the last transmission in the RA process, or, in another example, the maximum transmission power level used in the RA process. ○An example of the transmission power level discussed in Alt5 could be a percentage of the maximum allowed transmission power (e.g., 0.1, 0.2…1). When performing calculations, the UE can round up to the nearest number.

[0053] Example implementation 1a of Alt1: PerRAAttemptInfo-r16 Terminology in suspensionIndication-rxx It is an enumeration type IE, where, PerRAAttemptInfo-r16 Terminology in suspensionIndication-rxx The addition instruction has received a power ramp counter hang notification from the lower layer.

[0054] PerRAAttemptInfo-r16 ::=SEQUENCE { contentionDetected-r16BOOLEANOPTIONAL, dlRSRPAboveThreshold-r16BOOLEANOPTIONAL, ..., [[ fallbackToFourStepRA-r17ENUMERATED {true}OPTIONAL ]] [[ suspensionIndication-rxxENUMERATED {true}OPTIONAL ]] }

[0055] In this example, an indication of an enumeration type (e.g., suspensionIndication-rxx) is added to perRAAttemptInfo. The detailed meaning of this field has been given in the field description above. The term xx in suspensionIndication-rxx refers to the version number, which indicates in which version the indication was introduced (e.g., version 18).

[0056] The terminology used here is for illustrative purposes only. When storing RA information, for each RA attempt, if a power ramp counter suspension notification has been received from a lower layer for this RA attempt, the UE will include suspensionIndication-rxx in the stored RA information.

[0057] Example implementation 1b for Alt1: Terminology in PerRAAttemptInfo-r16 suspensionIndication-rxx It is a boolean type in IE, where the field suspensionIndication-rxx The value indicated in the text indicates whether a power ramp counter hangup notification has been received from the lower layer.

[0058] PerRAAttemptInfo-r16 ::=SEQUENCE { contentionDetected-r16BOOLEANOPTIONAL, dlRSRPAboveThreshold-r16BOOLEANOPTIONAL, ..., [[ fallbackToFourStepRA-r17ENUMERATED {true}OPTIONAL ]] [[ suspensionIndication-rxxBOOLEANOPTIONAL ]] }

[0059] In this example, a boolean indicator (e.g., suspensionIndication-rxx) is introduced into perRAAttemptInfo. The detailed meaning of this field has been given in the field description above. The term xx in suspensionIndication-rxx refers to the version number, which indicates in which version the indicator was introduced (e.g., version 18).

[0060] The terminology used here is illustrative. When storing RA information, for each RA attempt, if a power ramp counter hangup notification has been received from the lower layer for this RA attempt, the UE will... suspensionIndication-rxx The value is set to 1, otherwise it is set to zero.

[0061] In another example, the indication of this value can be reversed; for example, a value of 0 could indicate that a power ramp counter hang notification has been received from the lower layer for this RA attempt, while otherwise it would be set to 1.

[0062] Example implementation 2a of Alt2: exist PerRAInfoList-vxxyy In this context, xx can indicate the version number, and yy can indicate a sub-version within the version. In one example, xx could be equal to 18, and yy could be equal to 00, which would indicate that the field is introduced into version zero of version 18.

[0063] RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ perRAInfoList-vxxyy ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-vxxyy ]] } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 PerRAInfoList-vxxyy ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-vxxyy PerRAInfo-r16 ::=CHOICE { perRASSBInfoList-r16PerRASSBInfo-r16, perRACSI-RSInfoList-r16PerRACSI-RSInfo-r16 } PerRAInfo-vxxyy ::=CHOICE { perRASSBInfoList-vxxyyPerRASSBInfo-vxxyy, perRACSI-RSInfoList-vxxyyPerRACSI-RSInfo-vxxyy } PerRASSBInfo-r16 ::=SEQUENCE { ssb-Index-r16SSB-Index, numberOfPreamblesSentOnSSB-r16INTEGER (1..200), perRAAttemptInfoList-r16PerRAAttemptInfoList-r16 } PerRASSBInfo-vxxyy ::=SEQUENCE { numberOfSuspensionReceived--rxxINTEGER (1..nn)OPTIONAL, } PerRACSI-RSInfo-r16 ::=SEQUENCE { csi-RS-Index-r16CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::=SEQUENCE { csi-RS-Index-v1660INTEGER (1..96)OPTIONAL } PerRACSI-RSInfo-v1660 ::=SEQUENCE { PerRACSI-RSInfo-v1660 ::=SEQUENCE { PerRACSI-RSInfo-vxxyy ::=SEQUENCE { numberOfSuspensionReceived-rxxINTEGER (1..nn)OPTIONAL, } PerRAAttemptInfoList-r16 ::=SEQUENCE (SIZE (1..200)) OFPerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::=SEQUENCE { contentionDetected-r16BOOLEANOPTIONAL, dlRSRPAboveThreshold-r16BOOLEANOPTIONAL, ..., [[ fallbackToFourStepRA-r17ENUMERATED {true}OPTIONAL ]] }

[0064] In this example, this field is introduced to indicate the number of suspension indication notifications received from the lower layer for the beam used for RA attempts, the suspension indication being used for the suspension power ramp-up counter. This field is of integer type. In the example above, the value of this field ranges from 1 to n, with an interval or step size of 1, and n is an integer; the first example value could be 200. The selected beam type can be SSB or CSI-RS.

[0065] When storing RA information, for consecutive RA attempts for the selected beam, if at least one power ramp counter hangup notification is received from the lower layer, the UE sets... numberOfSuspensionReceived-rxx This indicates the number of pending notifications received for this beam. If multiple power ramp counter pending notifications are received from a lower layer for the same RA, they will only be counted as one notification. The selected beam type can be SSB or CSI-RS.

[0066] In another example, the value can range from zero to n. Here, n is an integer, and the first example value could be 200. In this example, when storing RA information, the UE sets the RA for consecutive RA attempts used for the selected beam. numberOfSuspensionReceived-rxxThis indicates the number of pending notifications received for this beam. If multiple power ramp counter pending notifications are received from a lower layer for the same RA, they will only be counted as one notification. The selected beam type can be SSB or CSI-RS. The terminology used here is for illustrative purposes only.

[0067] The difference between the two examples above is that in the first example, the information element (IE) is used to indicate a value of zero when it is not present. This means that if no power ramp counter hangup notification is received in the beam used for RA attempts, the UE does not need to include this IE.

[0068] Example implementation 2b for Alt2: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ numberOfSuspensionReceived-rxxINTEGER (1..nn)OPTIONAL, ]] }

[0069] In this example, this field is introduced to indicate the number of suspend indication notifications received from the lower layer for the RA process, which are used to suspend the power ramp-up counter. This field is of integer type. In the example above, the value of this field ranges from 1 to n, with an interval or step size of 1, and n is an integer. The first example value could be 200.

[0070] If at least one power ramp counter hangup notification is received from a lower layer, the UE sets... numberOfSuspensionReceived-rxx This indicates the number of hangback notifications received for the RA process. If multiple power ramp counter hangback notifications are received from a lower layer for the same RA, they will only be counted as one notification.

[0071] In another example, the value can be an integer ranging from zero to n, where n is an integer. In one example, the value of n can be 200. In this example, the UE is set... numberOfSuspensionReceived-rxx This indicates the number of hangback notifications received for the RA process. If multiple power ramp counter hangback notifications are received from a lower layer for the same RA, they will only be counted as one notification.

[0072] The difference between the two examples above is that in the first example, the value used to indicate when the IE is not present is zero, which means that the UE does not need to include this IE if no power ramp counter hangup notification is received.

[0073] The terminology used here to indicate fields (which indicate the number of times the power ramp counter hangs for the RA process) is exemplary.

[0074] Example implementation 3a of Alt3: exist PerRAInfoList-vxxyy In this context, xx can indicate the version number, and yy can indicate a sub-version within the version. In one example, xx could be equal to 18, and yy could be equal to 00, which would indicate that the field is introduced into version zero of version 18.

[0075] RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ PerRAInfoList-vxxyy ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-vxxyy ]] } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 PerRAInfoList-vxxyy ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-vxxyy PerRAInfo-r16 ::=CHOICE { perRASSBInfoList-r16PerRASSBInfo-r16, perRACSI-RSInfoList-r16PerRACSI-RSInfo-r16 } PerRAInfo-vxxyy ::=CHOICE { perRASSBInfoList-vxxyyPerRASSBInfo-vxxyy, perRACSI-RSInfoList-vxxyyPerRACSI-RSInfo-vxxyy } PerRASSBInfo-r16 ::=SEQUENCE { ssb-Index-r16SSB-Index, numberOfPreamblesSentOnSSB-r16INTEGER (1..200), perRAAttemptInfoList-r16PerRAAttemptInfoList-r16 } PerRASSBInfo-vxxyy ::=SEQUENCE { numberOfPowerRamping-rxxINTEGER (1..nn)OPTIONAL, } PerRACSI-RSInfo-r16 ::=SEQUENCE { csi-RS-Index-r16CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::=SEQUENCE { csi-RS-Index-v1660INTEGER (1..96)OPTIONAL } PerRACSI-RSInfo-v1660 ::=SEQUENCE { PerRACSI-RSInfo-v1660 ::=SEQUENCE { PerRACSI-RSInfo-vxxyy ::=SEQUENCE { numberOfPowerRamping-rxxINTEGER (1..nn)OPTIONAL, } PerRAAttemptInfoList-r16 ::=SEQUENCE (SIZE (1..200)) OFPerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::=SEQUENCE { contentionDetected-r16BOOLEANOPTIONAL, dlRSRPAboveThreshold-r16BOOLEANOPTIONAL, ..., [[ fallbackToFourStepRA-r17ENUMERATED {true}OPTIONAL ]] }

[0076] In this example, a field is introduced to indicate the number of preamble power ramps performed for the beam, where the field is of integer type. In the example above, the value of this field ranges from 1 to n, with an interval or step size of 1, and n is an integer; the first example value could be 200, and another example value could be 199.

[0077] When storing RA information, for consecutive RA attempts for the selected beam, if the UE has progressively increased the preamble power ramp counter at least once for the selected beam, then the UE sets... numberOfPowerRamping-rxx This indicates the number of preamble power ramps performed for that beam. The selected beam type can be SSB or CSI-RS.

[0078] In another example, the value can come from an integer ranging from zero to n, where n is an integer. In one example, the value of n could be 199. In this example, when storing RA information, the UE sets the RA for consecutive RA attempts used for the selected beam. numberOfPowerRamping-rxx This indicates the number of times a preamble power ramp is performed for that beam. Furthermore, the UE still sets this even when no power ramp is performed. numberOfPowerRamping-rxx The value is zero. The selected beam type can be SSB or CSI-RS.

[0079] The terms and ranges of values ​​listed here are exemplary.

[0080] Example implementation 3b for Alt3: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ numberOfPowerRamping-rxxINTEGER (1..nn)OPTIONAL, ]] }

[0081] In this example, a field is introduced to indicate the number of preamble power ramps performed for the RA process, where the field is of integer type. In the example above, the value of this field ranges from 1 to n, with an interval or step size of 1, and n is an integer; the first example value could be 200, and another example value could be 199.

[0082] When storing RA information, if the UE increments the preamble power ramp-up counter at least once during the RA process, then the UE sets... numberOfPowerRamping-rxx This indicates the number of preamble power ramps performed during the RA process.

[0083] In another example, the value can be an integer ranging from zero to 200 or zero to 199. In this example, when storing RA information, the UE sets... numberOfPowerRamping-rxx This indicates the number of times a preamble power ramp is performed for the RA procedure. Furthermore, the UE still sets this even when no power ramp is performed. numberOfPowerRamping-rxx The value is zero. The terms and ranges of values ​​listed here are merely illustrative.

[0084] Alt4: The maximum transmission power used during the RA process (in another example, it can be rephrased as the power used for the last...). (Transmission power of preamble transmission) Example implementation 4a for Alt4: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ maxPreamblePowerReceived-rxxINTEGER (aa..bb),OPTIONAL, ]] }

[0085] In the RA-InformationCommon IE, a field is introduced that indicates the maximum preamble power level received at the network receiver during the RA process. The value of this field is in the range of aa to bb.

[0086] aa and bb are numbers, and the example value range can be (-200, -60). Other value ranges are also possible. In some examples, only multiples of 2 can be chosen within the given range of aa and bb. In some examples, the unit of power level can be dBm.

[0087] When storing RA information, the UE sets maxPreambleReceivedPower to indicate the maximum preamble power level received at the network receiver during the RA process. The terms and value ranges listed here are for illustrative purposes only.

[0088] In another example, the IE is only included if the configured maximum UE output power of the selected carrier is not reached. For example:

[0089] When storing RA information, if the maximum preamble power level received at the network receiver is less than PCMAX, f, c of the selected carrier in the RA procedure (as specified in TS 38.321), then the UE sets... maxPreambleReceivedPower This indicates the maximum preamble power level received at the network receiver during the RA process. The terms and value ranges listed here are for illustrative purposes only.

[0090] In another example, the maximum preamble power level received at the network receiver during the RA process can be described as the power level of the last preamble received at the NW side during the RA process. This is because during the RA process, the power level can only be increased or maintained, not decreased. Therefore, the power level of the last preamble received at the NW side during the RA process can be used to indicate the maximum preamble power level received at the network receiver during the RA process.

[0091] In yet another example, if the selected carrier type (UL or SUL) in the RA procedure is known to be NW, then the P of the selected carrier in the RA procedure... CMAX, f, c (As specified in TS 38.321) may be known in the NW, and then the UE may report the percentage of the maximum preamble power level received at the network receiver side during the RA process, instead of reporting the actual power level used.

[0092] Example implementation 5a for Alt5: In the RA-InformationCommon IE, a field is introduced to indicate the percentage of the maximum preamble power level received at the network receiver during the RA process. This field can be an enumerated type field. An example is given below: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ maxPreamblePowerReceivedPercentage-rxxENUMERATED {0Dot1, 0Dot2,0Dot3, 0Dot4, 0Dot5, 0Dot6, 0Dot7, 0Dot8, 0Dot9, lDot0}OPTIONAL, ]] }

[0093] When storing RA information, the UE is configured. maxPreamblePowerReceivedPercentage-rxx To indicate: P of the selected carrier in the RA process CMAX, f, c Compared to (as specified in TS 38.321), this is the percentage of the maximum preamble power level received at the network receiver during the RA process. In some examples, the UE rounds the calculated value up to the nearest indicated value. In another example, the UE rounds the calculated value up to the nearest smaller number, or in yet another example, the UE rounds the calculated value up to the nearest larger number. The terms and value ranges listed here are merely illustrative.

[0094] Example implementation 5b for Alt5: Another example is shown below, which indicates the percentage of the maximum preamble power level received at the network receiver side during the RA process: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ maxPreamblePowerReceivedPercentage-rxxENUMERATED {p10, p20, p30, p40,p5, p60, p70, p80, p90, pl00}OPTIONAL, ]] }

[0095] When storing RA information, the UE is configured. maxPreamblePowerReceivedPercentage-rxx To indicate: P of the selected carrier in the RA process CMAX, f, c Compared to (as specified in TS 38.321), this is the percentage of the maximum preamble power level received at the network receiver during the RA process. In some examples, the UE rounds the calculated value up to the nearest indicated value. In another example, the UE rounds the calculated value up to the nearest smaller number, or in yet another example, the UE rounds the calculated value up to the nearest larger number. The terms and value ranges listed here are merely illustrative.

[0096] Example implementation 5c for Alt5: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]] [[ maxPreamblePowerReceivedPercentage-rxxinteger (1..cc)OPTIONAL, ]] }

[0097] When storing RA information, the UE is configured. maxPreamblePowerReceivedPercentage-rxx To indicate: P of the selected carrier in the RA process CMAX, f, c Compared to (as specified in TS 38.321), this is the percentage of the maximum preamble power level received at the network receiver during the RA process. In some examples, the UE rounds the calculated value up to the nearest indicated value. In another example, the UE rounds the calculated value up to the nearest smaller number, or in yet another example, the UE rounds the calculated value up to the nearest larger number. The terms and value ranges listed here are merely illustrative.

[0098] For example, as given in 5a / 5b / 5c, the maximum preamble power level received at the network receiver during the RA process can be rewritten as the power level of the last preamble received at the NW side during the RA process. This is because, currently, during the RA process, the power level can only be increased or maintained, not decreased. Therefore, the power level of the last preamble received at the NW side during the RA process can be used to indicate the maximum preamble power level received at the network receiver during the RA process.

[0099] III.B. Dispatch Request (SR) Purpose Indication When a BFR is detected in the SCell, the UE can transmit a truncated BFR MAC CE or a BFR MAC CE; or when an LBT is detected in the SCell, the UE can transmit an LBT MAC CE. If no available or valid UL resources are available for transmitting the corresponding MAC CE, the UE will trigger a scheduling request (SR) to request UL resources to transmit a BFR MAC CE or a truncated BFR MAC CE (if an SR is triggered for BFR) or to request UL resources to transmit an LBT MAC CE (if an SR is triggered for LBT). The NW can optionally configure a dedicated SR configuration for the UE for BFR and / or a dedicated SR configuration for LBT. When a dedicated SR resource is configured, the UE can use that dedicated resource to transmit the SR.

[0100] For step 1: As discussed in the previous chapter, for LBT / BFR triggered in a SCell, the RA purpose of RACH is set to: (1) no valid SR PUCCH resource is configured when the SR is triggered, or (2) the SR fails. The required optimization may be related not only to the RACH configuration but also to the SR configuration. Since the SR may be triggered due to BFR or LBT or other reasons, when the RA process purpose is set to indicate SR failure or no valid SR PUCCH resource is configured for the triggered SR, auxiliary information is needed to indicate the purpose of triggering the SR (or in other words, the event that triggers the SR) in order to know which SR configuration NW may need to optimize. When storing the RA process RA information, where the RA purpose is set to indicate SR failure (e.g. schedulingRequestFailure ) or indicates that no valid SR PUCCH resource is configured for the triggered SR (e.g. noPUCCHResourceAvailable One or more of the following alternatives can be considered to indicate the event that triggers the SR: Alt1: An enumerated type indicator can be introduced to indicate that the event that triggered SR is {LBT, BFR}. In this example, spare bits can be introduced for future expansion.

[0101] Alt2: A separate indicator can be introduced to indicate whether the SR is triggered by the LBT or the BFR. For example, the presence of the LBT indicator can be used to indicate that the SR is triggered by the LBT; the presence of the BFR indicator can be used to indicate that the SR is triggered by the BFR.

[0102] Alt3: A single bit can be introduced to indicate whether the event that triggered the SR was LBT or BFR. For example, a value of 1 indicates that the SR was triggered by LBT, and a value of 0 indicates that the SR was triggered by BFR. The reverse is also true.

[0103] Example implementation 1a of Alt1: In some implementations, fields sr-Trigger It can be included RA-InformationCommon middle, RA- InformationCommon It can be included in one or more reports transmitted by the UE to the NW.

[0104] RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]], [[ sr-Trigger-rxxENUMERATED {BFR, LBT, spare2, spare1}OPTIONALOPTIONAL, ]] }

[0105] The terminology used here is for illustrative purposes only.

[0106] Example implementation 1b for Alt1: In some implementations, fields sr-Trigger It can be included RA-Report middle, RA-Report It can be transmitted from the UE to the NW.

[0107] RA-Report-r16 ::=SEQUENCE { cellId-r16CHOICE { cellGlobalId-r16CGI-Info-Logging-r16, pci-arfcn-r16PCI-ARFCN-NR-r16 }, ra-InformationCommon-r16RA-InformationCommon-r16OPTIONAL, raPurpose-r16ENUMERATED {accessRelated, beamFailureRecovery,reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable,requestForOtherSI, msg3RequestForOtherSI-r17, spare8, spare7, spare6, spare5, spare4,spare3, spare2, spare1}, ..., [[ spCellID-r17CGI-Info-Logging-r16OPTIONAL ]], [[ sr-Trigger-rxxENUMERATED {BFR, LBT, spare2, spare1}OPTIONAL, ]] }

[0108] The terminology used here is for illustrative purposes only.

[0109] Alt2: A separate indicator can be introduced to indicate whether the SR is triggered by the LBT or the BFR. For example, the presence of the LBT bit can be used to indicate that the SR is triggered by the LBT; the presence of the BFR bit can be used to indicate that the SR is triggered by the BFR.

[0110] Example implementation 2a of Alt2: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]], [[ sr-TriggerBFR-rxxENUMERATED {true}OPTIONAL, sr-TriggerLBT-rxxENUMERATED{true}OPTIONAL ]] }

[0111] The terminology used here is for illustrative purposes only. In some examples, only one of the two IEs shown above may be included.

[0112] Example implementation 2b for Alt2: RA-Report-r16 ::=SEQUENCE { cellId-r16CHOICE { cellGlobalId-r16CGI-Info-Logging-r16, pci-arfcn-r16PCI-ARFCN-NR-r16 }, ra-InformationCommon-r16RA-InformationCommon-r16OPTIONAL, raPurpose-r16ENUMERATED {accessRelated, beamFailureRecovery,reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable,requestForOtherSI, msg3RequestForOtherSI-r17, spare8, spare7, spare6, spare5, spare4,spare3, spare2, spare1}, ..., [[ spCellID-r17CGI-Info-Logging-r16OPTIONAL ]], [[ sr-TriggerBFR-rxxENUMERATED {true}OPTIONAL, sr-TriggerLBT-rxxENUMERATED{true}OPTIONAL ]] }

[0113] The terminology used here is for illustrative purposes only. In some examples, only one of the two IEs shown above may be included.

[0114] Example implementation 3a of Alt3: RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]], [[ sr-Trigger-rxxBOOLEANOPTIONAL ]] }

[0115] In another example, a value of zero could indicate that the SR is triggered by a BFR, while a value of 1 could indicate that the SR is triggered by an LBT. The terminology used here is for illustrative purposes only.

[0116] Example implementation 3b for Alt3: RA-Report-r16 ::=SEQUENCE { cellId-r16CHOICE { cellGlobalId-r16CGI-Info-Logging-r16, pci-arfcn-r16PCI-ARFCN-NR-r16 }, ra-InformationCommon-r16RA-InformationCommon-r16OPTIONAL, raPurpose-r16ENUMERATED {accessRelated, beamFailureRecovery,reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable,requestForOtherSI, msg3RequestForOtherSI-r17, spare8, spare7, spare6, spare5, spare4,spare3, spare2, spare1}, ..., [[ spCellID-r17CGI-Info-Logging-r16OPTIONAL ]], [[ sr-Trigger-rxxBOOLEANOPTIONAL ]] }

[0117] In another example, a value of zero could indicate that the SR is triggered by a BFR, while a value of 1 could indicate that the SR is triggered by an LBT. The terminology used here is for illustrative purposes only.

[0118] III.C. Information regarding the number of LBT failure indications received. For step 1: Currently, when a persistent LBT failure is detected in the current BWP, the UE can switch to another bandwidth portion (BWP) to initiate RACH. Informing the NW of the number of LBT failures detected in each BWP is highly beneficial for the NW to understand the severity of LBT problems in each BWP. However, including this information would incur significant overall signaling overhead. This is because the UE can only initiate RACH after reaching a configured number of LBT failures that trigger persistent LBT failures (e.g., ...). lbt-FailureInstanceMaxCount The BWP is only activated when a persistent LBT failure occurs. Therefore, by adding new BWP information to the RA information stored by the UE, there can be an implicit indication that the UE has reached the configured number of LBT failures that trigger a persistent LBT failure in a previous BWP. In this case, the UE only needs to store the difference between the "total number of LBT failures detected in the BWP" and the "configured number of LBT failures that trigger a persistent LBT failure" (e.g., the remaining number of LBT failure indications detected in the BWP) in the RA information. When the NW receives this information from the UE, the NW can obtain the total number of LBT failures detected in the BWP by adding the remaining number of detected LBT failure indications to the configured number of LBT failures that trigger a persistent LBT failure. In one example, the UE includes this remaining number for each BWP in a continuous RACH process triggered by a persistent LBT failure. In another example, the UE includes the remaining number for each BWP in a continuous RACH process triggered by a persistent LBT failure (except for the last BWP in which the UE has already tried RACH).

[0119] The following is an example of how this information is encoded in signaling.

[0120] RA-InformationCommon-r16 ::=SEQUENCE { absoluteFrequencyPointA-r16ARFCN-ValueNR, locationAndBandwidth-r16INTEGER (0..37949), subcarrierSpacing-r16SubcarrierSpacing, msg1-FrequencyStart-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-FrequencyStartCFRA-r16INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msg1-SubcarrierSpacing-r16SubcarrierSpacingOPTIONAL, msg1-SubcarrierSpacingCFRA-r16SubcarrierSpacingOPTIONAL, msg1-FDM-r16ENUMERATED {one, two, four, eight}OPTIONAL, msg1-FDMCFRA-r16ENUMERATED {one, two, four, eight}OPTIONAL, perRAInfoList-r16PerRAInfoList-r16, ..., [[ perRAInfoList-v1660PerRAInfoList-v1660OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16ENUMERATED {kHz1dot25,kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-RO-FrequencyStartCFRA-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, msgA-SubcarrierSpacing-r17SubcarrierSpacingOPTIONAL, msgA-RO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-RO-FDMCFRA-r17ENUMERATED {one, two, four, eight}OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17ENUMERATED {kHz1dot25,kHz5, spare2, spare1}OPTIONAL, msgA-TransMax-r17ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100,n200}OPTIONAL, msgA-MCS-r17INTEGER (0..15)OPTIONAL, nrofPRBs-PerMsgA-PO-r17INTEGER (1..32)OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17INTEGER (1..maxNrofUL-Allocations)OPTIONAL, frequencyStartMsgA-PUSCH-r17INTEGER (0..maxNrofPhysicalResourceBlocks-1)OPTIONAL, nrofMsgA-PO-FDM-r17ENUMERATED {one, two, four, eight}OPTIONAL, dlPathlossRSRP-r17RSRP-RangeOPTIONAL, intendedSIBs-r17SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17OPTIONAL, ssbsForSI-Acquisition-r17SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-IndexOPTIONAL, msgA-PUSCH-PayloadSize-r17BIT STRING (SIZE (5))OPTIONAL, onDemandSISuccess-r17ENUMERATED {true}OPTIONAL ]], [[ attemptedBWPInfo-r18SEQUENCE (SIZE (1..maxNrofBWPs-1-r18)) OFAttemptedBWPInfo-r18OPTIONAL,]] } AttemptedBWPInfo-r18::=SEQUENCE { locationAndBandwidth-r18INTEGER (0..37949), subcarrierSpacing-r18SubcarrierSpacing numberOfRemainingLBTFailures-r18INTEGER (1..nn)OPTIONAL }

[0121] A field has been introduced in the RA-InformationCommon IE that indicates the remaining number of LBT failure indications detected in the BWP. This occurs when RA information is stored, and the number of LBT failure indications detected in the BWP exceeds the configured number of LBT failures for triggering persistent LBT failures in that BWP (i.e., ...). lbt-FailureInstanceMaxCount When this occurs, the UE stores this field in the stored RA information and sets the value of this field to a value obtained through the following calculation: the total number of LBT failures detected in the BWP minus the configured number of LBT failures configured for triggering persistent LBT failures for the BWP (i.e., lbt- FailureInstanceMaxCount ).

[0122] In the example above, this field is an integer type, and its value can be in the range of 1 to n, with a step size of 1. n is an integer. An example value for n could be 128. In some examples, the UE obtains the value of this field by subtracting the configured number of LBT failures configured for triggering persistent LBT failures for the BWP from the total number of LBT failures detected in the BWP (i.e., lbt- FailureInstanceMaxCount The terms and ranges of values ​​listed here are for illustrative purposes only.

[0123] Figure 2 An exemplary flowchart for transmitting information stored by a communication device is shown. Operation 202 includes transmitting the information stored by the communication device, wherein the information includes a suspend indication indicating whether the communication device has received a suspend notification of a counter associated with power ramping for a random access attempt, and wherein a rule specifies whether the information includes the suspend indication and / or content related to the suspend indication included in the information.

[0124] In some implementations, the rule specifies that the suspend indication includes a message indicating that the communication device has received a suspend notification for a counter associated with power ramp-up. In some implementations, the rule specifies that the suspend indication includes a bit value including a first value indicating that a suspend notification with a counter having power ramp-up has been received and the communication device has suspended the counter associated with power ramp-up; and the rule specifies that the suspend indication includes a bit value including a second value indicating that a suspend notification with a counter having power ramp-up has been received and the communication device has not yet suspended the counter associated with power ramp-up. In some implementations, the method further includes storing the suspend indication in response to performing a random access attempt for a random access procedure.

[0125] Figure 3Another exemplary flowchart for transmitting information stored by a communication device is shown. Operation 302 includes: transmitting the information stored by the communication device, wherein the information includes a hang count, the hang count indicating the number of times a hang count notification has been received for a transmission beam for performing a random access procedure, wherein the hang count indicates that the communication device has hung a counter associated with power ramping, and wherein a rule specifies whether the information includes the hang count and / or content related to the hang count included in the information.

[0126] In some implementations, the rule specifies that the value of a field included in the information indicates the number of pending connections received by the communication device. In some implementations, the rule specifies that the absence of a field associated with the number of pending connections in the information indicates that the number of pending connections is equal to zero. In some implementations, the method further includes storing the number of pending connections in response to performing a random access attempt for a random access procedure.

[0127] Figure 4 Another exemplary flowchart for transmitting information stored by a communication device is shown. Operation 402 includes: transmitting the information stored by the communication device, wherein the information includes a hang count, the hang count indicating the number of times a hang count notification has been received during a random access procedure performed for the communication device, wherein the hang count indicates that the communication device has hung a counter associated with power ramping, and wherein a rule specifies whether the information includes the hang count and / or content related to the hang count included in the information.

[0128] In some implementations, the rule specifies that the value of a field included in the information indicates the number of pending connections received by the communication device. In some implementations, the rule specifies that the absence of a field associated with the number of pending connections in the information indicates that the number of pending connections is zero. In some implementations, the method further includes storing the number of pending connections in response to performing a random access procedure.

[0129] Figure 5 Another exemplary flowchart for transmitting information stored in a communication device is shown. Operation 502 includes transmitting the information stored in the communication device via the communication device, wherein the information includes a field indicating an event that triggers a scheduling request, and wherein the information includes the field indicating that the scheduling request was triggered due to beam fault recovery (BFR) or due to listen-before-tell (LBT).

[0130] In some implementations, the information is public random access information for one or more random access attempts. In some implementations, the information is a random access report, which includes random access information used in the random access procedure. In some implementations, the method further includes: in response to a failure to execute a scheduling request or in response to the absence of one or more resources for executing the scheduling request, the communication device stores the field.

[0131] The implementation methods discussed above are applied to wireless communication. Figure 6 An example of a wireless communication system (e.g., a 5G or NR cellular network) is illustrated, comprising a base station 620 and one or more user equipments (UEs) 611, 612, and 613. In some embodiments, the UE accesses the BS (e.g., the network) using a communication link to the network (sometimes referred to as the uplink, as shown by dashed arrows 631, 632, and 633), enabling the BS to subsequently communicate with the UE (e.g., along the direction from the network to the UE, sometimes referred to as the downlink, as shown by arrows 641, 642, and 643). In some embodiments, the BS sends information to the UE (sometimes referred to as the downlink, as shown by arrows 641, 642, and 643), enabling the UE to subsequently communicate with the BS (e.g., along the direction from the UE to the BS, sometimes referred to as the uplink, as shown by dashed arrows 631, 632, and 633). The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, Internet of Things (IoT) device, etc.

[0132] Figure 7 An exemplary block diagram of a hardware platform 700 is shown, which may be part of a network device (e.g., a base station) or a communication device (e.g., a user equipment (UE)). The hardware platform 700 includes at least one processor 710 and a memory 705 thereon storing instructions. When executed by the processor 710, the instructions configure the hardware platform 700 to perform... Figures 1 to 6 And the operations described in the various embodiments described in this patent document. Transmitter 715 transmits or sends information or data to another device. For example, a network device transmitter is capable of sending a message to a user equipment. Receiver 720 receives information or data transmitted or sent by another device. For example, a user equipment is capable of receiving a message from a network device.

[0133] In this document, the term “exemplary” is used to mean “an example” and, unless otherwise stated, does not imply that it is an ideal or preferred implementation.

[0134] Some embodiments described herein are described in the general context of a method or process, which in one embodiment can be implemented by a computer program product contained in a computer-readable medium, including computer-executable instructions, such as program code executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Generally, a program module may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in such steps or processes.

[0135] Some embodiments of the disclosed examples may be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components, such as those integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include digital signal processors (DSPs), which are special-purpose microprocessors with an architecture optimized for the operational requirements of digital signal processing associated with the disclosed functions of this application. Similarly, various components or sub-components within each module may be implemented using software, hardware, or firmware. Connectivity between modules and / or components within modules may be provided using any of the connection methods and media known in the art, including but not limited to communication over the Internet, wired, or wireless networks using appropriate protocols.

[0136] While this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or the scope that may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described in this document within the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as functioning in certain combinations, or even initially claimed, in some cases one or more features from the claimed combination may be removed, and the claimed combination may refer to a sub-combination or a variation of the sub-combination. Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or requiring the performance of all shown operations to achieve the desired result.

[0137] Only a few implementations and examples have been described, and other implementations, enhancements and variations may be made based on what is described and shown in this disclosure.

Claims

1. A wireless communication method, comprising: The information stored in the communication device is transmitted through the communication device. The information includes a suspend indication, which indicates whether the communication device has received a suspend notification from a counter associated with power ramping for a random access attempt, and The rules specify whether the information includes the suspension instruction and / or content related to the suspension instruction included in the information.

2. The method of claim 1, wherein the rule specifies that the suspension indication includes an indication in the information that the communication device has received the suspension notification of the counter associated with the power ramp.

3. The method according to claim 1, The rule states that the suspend indication includes a one-bit value, the one-bit value including a first value indicating that a suspend notification with the counter associated with the power climb has been received, and that the communication device has suspended the counter associated with the power climb. The rule states that the suspension indication includes a one-bit value, the one-bit value including a second value, the second value indicating that a suspension notification has been received with the counter having the power climb, and the communication device has not yet suspended the counter associated with the power climb.

4. The method according to claim 1, further comprising: In response to performing the random access attempt for the random access procedure, the communication device stores the hangup indication.

5. A wireless communication method, comprising: The information stored in the communication device is transmitted through the communication device. The information includes a suspension count, which indicates the number of times a suspension indication notification has been received for the transmission beam used to perform a random access procedure. The suspension indication indicates that the communication device has suspended the counter associated with the power ramp-up, and The rules specify whether the information includes the number of suspensions and / or content related to the number of suspensions included in the information.

6. The method of claim 5, wherein the rule specifies that the value of a field included in the information indicates the number of suspends received by the communication device.

7. The method of claim 5, wherein the rule specifies that there is no field associated with the number of pending items in the information indicating that the number of pending items is equal to zero.

8. The method according to claim 5, further comprising: In response to performing the random access attempt for the random access procedure, the communication device stores the number of pending attempts.

9. A wireless communication method, comprising: The information stored in the communication device is transmitted through the communication device. The information includes a suspension count, which indicates the number of times a suspension indication notification has been received during a random access procedure performed for the communication device. The suspension indication indicates that the communication device has suspended the counter associated with the power ramp-up, and The rules specify whether the information includes the number of suspensions and / or content related to the number of suspensions included in the information.

10. The method of claim 9, wherein the rule specifies that the value of a field included in the information indicates the number of suspends received by the communication device.

11. The method of claim 9, wherein the rule specifies that there is no field associated with the number of pending items in the information indicating that the number of pending items is equal to zero.

12. The method according to claim 9, further comprising: In response to performing the random access procedure, the communication device stores the number of pending connections.

13. A wireless communication method, comprising: The information stored in the communication device is transmitted through the communication device. The information mentioned includes a field indicating the event that triggered the scheduling request, and The information includes the field indicating that the scheduling request was triggered due to beam fault recovery (BFR) or talk-before-listen (LBT).

14. The method of claim 13, wherein the information is public random access information for one or more random access attempts.

15. The method of claim 13, wherein the information is a random access report, which includes random access information for the random access procedure.

16. The method of claim 13, further comprising: In response to failure to execute the scheduling request or in response to the absence of one or more resources to execute the scheduling request, the communication device stores the field.

17. A wireless communication device comprising a processor configured to implement the method of one or more of claims 1 to 16.

18. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method of one or more of claims 1 to 16.

Images