Wireless communication method, wireless terminal and wireless network node thereof

Abstract

A wireless communication method for use in a wireless terminal is disclosed. The method comprises reporting random access (RA) information for at least one RA procedure to a wireless network node.

Description

[0001] This document relates generally to wireless communications and, more particularly, to reporting random access information.

[0002] RACH (random access channel) optimization is already part of SON (self-organizing networks) functionality, which serves multiple purposes, such as avoiding RACH resource congestion between neighboring cells / networks and helping to optimize RACH configuration to improve resource efficiency. RACH resource configuration is enhanced to support RA (random access) partitioned resources, thereby allowing RA resources to be partitioned to support different characteristics of different types of UE (user equipment). However, reports from UEs may not provide enough log-specific information associated with RA resources related to RA partitioning. Under such conditions, the NW (network) cannot confirm whether and how to perform corresponding optimization on the RACH configuration. In addition, since the UE does not log RA information for RA procedures initiated in unlicensed spectrum, similar problems also exist in RA procedures initiated for LBT (ListenBeforeTalk) recovery in unlicensed spectrum.

[0003] The present document relates to methods, systems and devices for reporting RA information, and more particularly to methods, systems and devices for reporting RA information associated with RA partition-related RA resources and / or unlicensed spectrum.

[0004] The present disclosure relates to a wireless communication method used in a wireless terminal. The method includes: reporting RA information of at least one random access (RA) procedure to a wireless network node.

[0005] Various embodiments may preferably achieve the following features:

[0006] Preferably, the RA information includes information associated with utilizing RA channel (RACH) resources, wherein the RACH resources are associated with one or more features applicable to the RA procedure.

[0007] Preferably, the RA information of each RA process includes at least one of the following: a feature type, the feature type indicating one or more features in a feature combination associated with the RA process; a first preamble, the first preamble being associated with the feature combination associated with the RA process; for each synchronization signal / physical broadcast channel block (SSB), the number of consecutive preambles associated with the feature combination; for each SSB, the number of consecutive preambles associated with a preamble group for the feature combination; a feature priority, the feature priority indicating the priority of the one or more features in the feature combination; for each RA process, each beam or each RA attempt, an indication of whether message 3 (Msg3) repetition is enabled; the number of Msg3 repetitions for each RA attempt or each beam; a modulation and coding scheme for the Msg3 repetition; a repetition of a physical uplink shared channel transmission scheduled by an RA radio network temporary identifier uplink grant and downlink control information format 0_0 number of repetitions; network slice related information associated with the RA process; at least one network slice group identifier associated with the RA process; at least one backoff value associated with the RA process; at least one scaling factor associated with the at least one backoff value; an indication of whether a backoff index is received for the RA process; at least one power boost step used in the RA process; at least one purpose associated with the at least one power boost step; an access identifier associated with the RA process; an indication of whether the RA process is successful; an indication of whether the DL RSRP is higher than a threshold configured for Msg3 repetition selection for each RA process or each RA attempt or each beam or each consecutive RA attempt in the same beam or each BWP; or a threshold used by the UE to determine whether to select resources indicating Msg3 repetition in the BWP.

[0008] Preferably, the one or more features of the feature combination associated with the RA process include at least one of: capability reduction, Msg3 repetition, small data transmission, or network slicing.

[0009] Preferably, the first preamble associated with the feature combination associated with the RA process is indicated by an integer ranging from 1 to 64.

[0010] Preferably, for each SSB, the number of consecutive preamble codes associated with the feature combination is indicated by an integer ranging from 1 to 64.

[0011] Preferably, for each SSB, the number of consecutive preambles associated with the preamble group for the feature combination is indicated by an integer ranging from 1 to 64.

[0012] Preferably, each feature priority is indicated by an integer ranging from 0 to 7.

[0013] Preferably, the number of Msg3 repetitions for each RA attempt or each beam is indicated by: an integer ranging from 1 to 16, or at least one value in a value set.

[0014] Preferably, the modulation and coding scheme used for the Msg3 repetition is indicated by an integer ranging from 0 to 31.

[0015] Preferably, each network slice group identifier is indicated by a bit string.

[0016] Preferably, the at least one backoff value is indicated by at least one backoff index.

[0017] Preferably, each boosting step size used in the RA process is indicated as a value in a value set.

[0018] Preferably, the RA information includes information associated with the RA process in the shared spectrum.

[0019] Preferably, the RA information includes at least one of the following: a configuration for detecting persistent uplink listen-before-talk (LBT) failure in shared spectrum channel access; an indication of initiating the RA process for LBT failure recovery; an indication of whether an LBT failure indication is received for each RA attempt in the shared spectrum; an indication of whether the RA process in the shared spectrum is successful, including the number of LBT failure indications received for each beam in the RA process or each consecutive attempt in a beam or for each RA process in the shared spectrum; an indication of whether LBT recovery is successful; the number of transmission opportunities configured for each bandwidth part for each RA process in the unlicensed spectrum; the running time of a timer associated with LBT failure detection; the number of LBT failures detected for each bandwidth part or each cell; or an indication of whether persistent LBT is detected in a bandwidth part.

[0020] Preferably, the configuration for detecting the persistent uplink LBT failure in the shared spectrum channel access includes at least one of: the length of a timer for detecting the persistent uplink LBT failure, or the maximum number of LBT failure indications received from the physical layer before triggering uplink LBT failure recovery.

[0021] Preferably, the wireless communication method further comprises: receiving, from the wireless network node, an RA configuration determined based on the RA information.

[0022] Preferably, the wireless communication method further comprises: transmitting, to the radio network node, a capability indication associated with reporting the RA information related to an RA process, wherein the RA process utilizes RA resources associated with a feature combination of the RA process.

[0023] Preferably, the wireless communication method further comprises: receiving a request for the capability indication from the wireless network node.

[0024] The present disclosure relates to a wireless communication method used in a wireless network node. The method includes receiving RA information of at least one random access RA procedure from a wireless terminal, and determining a RA configuration associated with the RA procedure of the wireless terminal.

[0025] Various embodiments may preferably achieve the following features:

[0026] Preferably, the RA information includes information associated with utilizing a random access channel RACH resource, wherein the RACH resource is associated with one or more features applicable to the RA process.

[0027] Preferably, the RA information of each RA process includes at least one of the following: a feature type, the feature type indicating one or more features in a feature combination associated with the RA process; a first preamble, the first preamble being associated with the feature combination associated with the RA process; for each synchronization signal / physical broadcast channel block (SSB), the number of consecutive preambles associated with the feature combination; for each SSB, the number of consecutive preambles associated with a preamble group for the feature combination; a feature priority, the feature priority indicating the priority of the one or more features in the feature combination; for each RA process, each beam or each RA attempt, an indication of whether message 3 (Msg3) repetition is enabled; the number of Msg3 repetitions for each RA attempt or each beam; the modulation and Coding scheme; number of repetitions of physical uplink shared channel transmission scheduled by RA radio network temporary identifier uplink grant and downlink control information format 0_0; network slice related information associated with the RA process; at least one network slice group identifier associated with the RA process; at least one backoff value associated with the RA process; at least one scaling factor associated with the at least one backoff value; an indication of whether a backoff index is received for the RA process; at least one power boost step used in the RA process; at least one purpose associated with the at least one power boost step; an access identifier associated with the RA process; an indication of whether the RA process is successful; an indication of whether the DL RSRP is higher than the threshold configured for Msg3 repetition selection for each RA process or each RA attempt or each beam or each consecutive RA attempt in the same beam or each BWP; or a threshold used by the UE to determine whether to select resources indicating Msg3 repetition in the BWP.

[0028] Preferably, the one or more features of the feature combination associated with the RA process include at least one of: capability reduction, Msg3 repetition, small data transmission, or network slicing.

[0029] Preferably, the first preamble associated with the feature combination associated with the RA process is indicated by an integer ranging from 1 to 64.

[0030] Preferably, for each SSB, the number of consecutive preamble codes associated with the feature combination is indicated by an integer ranging from 1 to 64.

[0031] Preferably, for each SSB, the number of consecutive preambles associated with the preamble group for the feature combination is indicated by an integer ranging from 1 to 64.

[0032] Preferably, each feature priority is indicated by an integer ranging from 0 to 7.

[0033] Preferably, the number of Msg3 repetitions for each RA attempt or each beam is indicated by: an integer ranging from 1 to 16, or at least one value in a value set.

[0034] Preferably, the modulation and coding scheme used for the Msg3 repetition is indicated by an integer ranging from 0 to 31.

[0035] Preferably, each network slice group identifier is indicated by a bit string.

[0036] Preferably, the at least one backoff value is indicated by at least one backoff index.

[0037] Preferably, each boosting step size used in the RA process is indicated as a value in a value set.

[0038] Preferably, the RA information includes information associated with the RA process in the shared spectrum.

[0039] Preferably, the RA information includes at least one of the following: a configuration for detecting persistent uplink listen-before-talk (LBT) failure in shared spectrum channel access; an indication of initiating the RA process for LBT failure recovery; an indication of whether an LBT failure indication is received for each RA attempt in the shared spectrum; an indication of whether the RA process in the shared spectrum is successful, including the number of LBT failure indications received for each beam in the RA process or each consecutive attempt in a beam or for each RA process in the shared spectrum; an indication of whether LBT recovery is successful; the number of transmission opportunities configured for each bandwidth part for each RA process in the unlicensed spectrum; the running time of a timer associated with LBT failure detection; the number of LBT failures detected for each bandwidth part or each cell; or an indication of whether persistent LBT is detected in a bandwidth part.

[0040] Preferably, the configuration for detecting the persistent uplink LBT failure in the shared spectrum channel access includes at least one of: the length of a timer for detecting the persistent uplink LBT failure, or the maximum number of LBT failure indications received from the physical layer before triggering uplink LBT failure recovery.

[0041] Preferably, the wireless communication method further comprises: transmitting to the wireless terminal an RA configuration determined based on the RA information.

[0042] Preferably, the wireless communication method further comprises: receiving a capability indication associated with reporting the RA information related to an RA process from the wireless terminal, the RA process utilizing RA resources associated with a feature combination of the RA process.

[0043] Preferably, the wireless communication method further comprises: transmitting a request for the capability indication to the wireless terminal.

[0044] Preferably, the wireless communication method further comprises: transmitting the RA information to at least one of another wireless network node, a core network or a network function.

[0045] The present disclosure relates to a wireless terminal. The wireless terminal comprises:

[0046] The communication unit is configured to report RA information of at least one random access (RA) procedure to a radio network node.

[0047] Various embodiments may preferably implement the following features:

[0048] Preferably, the wireless terminal further comprises a processor, and the processor is configured to execute any of the aforementioned wireless communication methods.

[0049] The present disclosure relates to a wireless network node. The wireless network node comprises:

[0050] a communication unit configured to receive RA information of at least one random access (RA) procedure from a wireless terminal; and

[0051] A processor is configured to determine an RA configuration associated with the RA procedure of the wireless terminal.

[0052] Various embodiments may preferably achieve the following features:

[0053] Preferably, the processor is further configured to execute any of the aforementioned wireless communication methods.

[0054] The present disclosure relates to a computer program product, which includes a computer-readable program medium. Codes are stored on the computer-readable program medium. When the codes are executed by a processor, the processor is prompted to implement the wireless communication method according to any of the aforementioned methods.

[0055] The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description when combined with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0056] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented.

[0057] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims.

[0058] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0059] Figure 2 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0060] Figure 3 A flow chart of a method according to an embodiment of the present disclosure is shown.

[0061] Figure 4 A schematic diagram of reporting capability information according to an embodiment of the present disclosure is shown.

[0062] Figure 5 A schematic diagram of reporting random access channel information according to an embodiment of the present disclosure is shown.

[0063] Figure 6 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0064] Figure 7 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0065] In this disclosure, unlicensed spectrum may refer to shared spectrum, and vice versa.

[0066] Figure 1 A schematic diagram of a network (architecture) according to an embodiment of the present disclosure is shown. Figure 1In the 5G network, the network includes user equipment (UE), next generation radio access network (NG-RAN) and 5G core network (5GC). 5GC is the core network (CN) in the new radio (NR) and includes various network entities and / or network functions, such as session management function (SMF), access and mobility management function (AMF), user plane function (UPF), policy control function (PCF), etc. Figure 1 Only AMF and UPF are shown for illustration. NG-RAN includes multiple base stations (BS) (or in other words, RAN nodes), such as gNB and ng-eNB (next generation eNB, next generation eNB)...etc. Figure 1 In the present invention, the UE communicates with the NG-RAN (i.e., gNB and / or ng-eNB) via the Uu interface and / or communicates with the 5GC via the NG-RAN. Figure 1 Only examples for NR (new air interface) architecture are shown. Note that the methods and devices disclosed in the present disclosure can also be applied to existing systems (e.g., LTE (long term evolution)) or future systems to be defined. For LTE, the BS discussed can be an eNB or en-gNB connected to an LTE CN (e.g., EPC (Evolved Packet Core)). In one embodiment, the UE can operate in dual-connectivity (DC) and access two BSs, wherein one of the two BSs accessed is used as an MN (master node) and the other of the two BSs accessed is used as an SN (secondary node).

[0067] In the present disclosure, NW (network) may refer to a BS or a RAN node.

[0068] In the present disclosure, the UE may store RA information when completing the RA process, and report the stored RA information to the NW (e.g., BS) when the RA information is requested to enable RACH optimization. The BS receiving the RACH information may also forward the received RACH information to other related BSs (e.g., the BS where the UE initiates the RACH process) for optimization. Alternatively or additionally, the BS receiving the RACH information may share the RACH information between (one or more) neighboring BSs to adjust the configuration of RACH resources, thereby avoiding conflicts in RACH resources. In addition, the BS receiving the RACH information may also forward the RACH information to another management system to optimize the RACH configuration. The management system may be OAM (Operations, Administration and Maintenance) and / or TCE (Trace Collection Entity) and / or AMF (Access and Mobility Management Function) of CN (Core Network), and / or another management system.

[0069] In the present disclosure, after receiving the RACH information reported from the UE, the NW and / or the management system may optimize (one or more) RACH resources and / or access-related configurations to help improve RACH performance or improve RACH capabilities. The following shows some examples of how the NW and / or the management system use RACH information for optimization. These use cases are not limited to the examples given in the present disclosure. For example, the NW and / or the management system may optimize the RACH resource partitioning between different features. For example, the NW (or the management system) may adjust the priorities of different features. The NW (or the management system) may decide whether to configure additional RACH resources for a particular feature. The NW (or the management system) may change the RA resource partitioning by adjusting the starting preambles of different resource groups and the number of preambles allocated for each resource group. For example, the NW (or the management system) may allocate more resources to reduce the RACH load for features with more requirements. The NW (or the management system) may adjust the power boost step size and / or the scaling factor for high priority features to prioritize the RA process associated with the feature. That is, the NW (or management system) can assign a smaller scaling factor and / or increase the power boost step size to improve the success rate of features that are considered high priority. The NW (or management system) can adjust the configuration for persistent LBT failure recovery, such as the maximum allowed LBT failure time, and the timer length for persistent LBT failure detection (e.g., lbt-FailureDetectionTimer).

[0070] Figure 2 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 2 In this embodiment, the UE operates in the DC, that is, it is connected to the MN and the SN. In this embodiment, the UE can report the collected RA information to the MN through the UEInformationRequest (UE information request) / UEInformationResponse (UE information response) process. After receiving the RACH information, the MN can also forward the SN-related RA information to the SN for optimization. In addition, the MN can forward the collected RACH information to its OAM (operation, administration and maintenance) or CN for optimization. The SN can also forward the collected RACH information to its OAM for optimization. Please note that Figure 2 Not all of the operations listed in may be required. That is, you can omit Figure 2 In other embodiments, the RACH information may also be delivered to the MN via different (one or more) RRC (Radio Resource Control) messages. In some examples, the UE may report SN-related RACH information to the SN based on the SN's request. In addition, in order to allow this behavior, the MN may need to forward the received UE capability information to the SN.

[0071] In one embodiment, in the case where the RAN node requests RA information, the UE may report the RA information of each RAN node to each RAN node respectively.

[0072] In one embodiment, Figure 2 The MN and SN in the RAN node may be RAN node 1 and RAN node 2, which may be independent or in DC. The RACH information may be forwarded to a management system. The management system may include at least one of the following: OAM, AMF, TCE (Trace Collection Entity) or other functional entities for optimizing RACH configuration. Based on different deployments, the management system may be connected to only RAN node 1, RAN node 2 or both.

[0073] In some embodiments, the RA related information reported from the UE to the NW through one or more UE reports includes RA report, RLF (radio link failure) report, CEF (connection establishment failure) report (or accessibility measurement), successful HO (handover) report and SCG (secondary cell group) failure information. RA report / RLF report / CEF report / successful HO report is reported to the NW through UEInformationRequest or UEInformationResponseInformation (UE information response information).

[0074] Figure 3 A flow chart of a method according to an embodiment of the present disclosure is shown. Specifically, in step 301, the UE receives a RA configuration from the NW. In an embodiment, the RA configuration may include a configuration related to RA partitioning (eg, a RACH configuration including FeatureCombinationPreambles).

[0075] In step 302, the UE performs a RACH procedure and stores RA information in a UE variable.

[0076] In step 303, when the NW requests RA information, the UE reports the RA information.

[0077] In step 304, the NW optimizes the RACH configuration based on the analysis of the received RA reports.

[0078] In the present disclosure, RA information may be equal to RACH information, and vice versa.

[0079] In some embodiments, after step 302, based on the ability of the NW to decide whether to request the UE to report RA information, the UE may report to the NW (stored in its storage unit (e.g., memory)) the availability of RA reports to the NW via MAC (media access control) signaling (e.g., MAC CE (control element)) or RRC signaling.

[0080] In some embodiments, the NW may share / transmit RACH information with another NW (e.g., another BS / gNB / NG-RAN) and / or CN (e.g., a network function / entity in the CN).

[0081] In addition, if the UE performs a RACH procedure in an unlicensed spectrum, the stored RA information may also include information related to (the RACH procedure in) the unlicensed spectrum. In this case, the RA configuration of the UE may or may not include RA partition information.

[0082] In the present disclosure, the RACH procedure type may be a 2-step RA (procedure), a 4-step RA (procedure), or any type of RACH procedure.

[0083] In some embodiments, RA information collection and reporting may help the NW optimize RA resource partitioning and / or LBT recovery configuration for different feature combinations.

[0084] In one embodiment, the feature combination indicates a feature or a combination of multiple features associated with a RA / RACH resource set. The NW may associate a RACH resource set with (one or more) of the following features applicable to the RA procedure: such as Network Slicing, RedCap (Reduced capability), SDT (small data transmission), and Msg3 repetition (or in other words, NR (New Air Interface) coverage enhancement). A RACH resource set associated with one feature is valid only for (one or more) RA procedures applicable to at least that feature; and a RACH resource set associated with several features is valid only for a RA procedure having at least all of these associated features. The UE selects the applicable (one or more) RACH resource sets after selecting an uplink carrier (i.e., NUL (normal uplink) or SUL (supplementary uplink)) and BWP (bandwidth part) and before selecting the RA type.

[0085] For example, the RA information collected and / or reported by the UE of a (completed) RA procedure may include at least one of the following fields:

[0086] - Feature type, which indicates one or more types of feature combinations associated with the RA process, where possible values ​​of the type of feature combination may include Msg3 repetition (or coverage enhancement (CE)), SDT, RedCap, and network slicing, etc.,

[0087] - a first preamble, the first preamble being associated with a signature combination associated with the RA procedure,

[0088] - the number of consecutive preambles associated with the corresponding feature combination starting from the starting preamble(s) for each SSB (synchronization signal / physical broadcast channel (PBCH) block),

[0089] - the number of consecutive preambles associated with a preamble group (e.g., Group A) for each SSB and starting from the starting preamble(s) of the corresponding feature combination,

[0090] - Feature priority, which indicates the priority for features such as RedCap, Slice, SDT, and Msg3-Repetition for coverage enhancement;

[0091] - an indication of whether the two-step RACH preamble identified by this FeatureCombinationPreambles is mapped to a PUSCH slot separate from the slot defined in MsgA-ConfigCommon-r16,

[0092] - an indication of whether Msg3 repetition is enabled for each RA procedure or each beam or each RA attempt or each consecutive RA attempt in the same beam,

[0093] - an indication of whether the DL (downlink) RSRP (Reference Signal Receiving Power) is above the threshold configured for Msg3 repetition selection for each RA process or each RA attempt or each beam or each consecutive RA attempt in the same beam or each BWP,

[0094] - a threshold used by the UE to determine whether to select a resource indicating Msg3 repetition in this BWP,

[0095] - the number of Msg3 repetitions for each RA process or each RA attempt or each beam or each consecutive RA attempt in the same beam or each BWP,

[0096] - the number of Msg3 retransmissions per RA process or per RA attempt or per beam or per consecutive RA attempts in the same beam or per BWP,

[0097] -MCS (modulation and coding scheme) used for Msg3 repetition,

[0098] - the number of repetitions of PUSCH (physical uplink shared channel) transmissions scheduled by RAR (Random Access Response) UL (uplink) grant and DCI (downlink control information) format 0_0 with CRC (cyclic redundancy check) scrambled by TC-RNTI (temporary cell radio network temporary identifier),

[0099] - Slice related information,

[0100] - Slice group identifier,

[0101] - a backoff value, which is used to indicate one or more backoff values ​​used in the RA process,

[0102] - Whether an indication of a BI has been received for this RA attempt,

[0103] - one or more power boost steps for the RA process,

[0104] - access identification,

[0105] - whether ra-PrioritizationForSlicing (ra-priority for slicing) / ra-PrioritizationForSlicingTwoStep (ra-priority for slicing two steps) should override the indication of ra-PrioritizationForAccessIdentity (ra-priority for access identification),

[0106] - an indication of whether the ra-Prioritization information should be used for the access identity,

[0107] -msg3 or msgA - power offset between PUSCH and RACH preamble transmission,

[0108] - Whether deltaPlreamble is configured, or

[0109] -NR-U (New Radio-Unlicensed spectrum) related information.

[0110] In one embodiment, the RA information may further include additional information, for example, other RA parameters.

[0111] For the parameters mentioned in the present disclosure, when the parameters are set for each beam, the beam type can be SSB or CSI-RS.

[0112] In one embodiment, the RA information collected and / or reported by the UE of the (completed) RA procedure may include at least one of the following fields:

[0113] - a feature combination type, which may indicate one or more types of feature combinations associated with the RA process;

[0114] - the first preamble associated to the signature combination associated with the RA process,

[0115] - the number of consecutive preambles associated with the corresponding feature combination starting from the starting preamble(s) for each SSB,

[0116] - For each RA process or each beam or each RA attempt, an indication of whether Msg3 repetition is enabled,

[0117] - an indication whether the DL RSRP is above the threshold configured for Msg3 repetition selection for each RA process or each RA attempt or each beam or each consecutive RA attempt in the same beam or each BWP,

[0118] - a threshold used by the UE to determine whether to select a resource indicating Msg3 repetition in this BWP,

[0119] - the number of Msg3 repetitions per beam for each attempt,

[0120] - MCS for Msg3 repeats,

[0121] - Slice group ID, or

[0122] - An indication of whether a BI has been received for this RA attempt.

[0123] Note that, in this embodiment, the RA information may also include (one or more) other aforementioned fields and / or RA parameters.

[0124] More details and embodiments of the aforementioned fields / parameters included in the RA message are shown below, for example, via an exemplary ASN.1 (Abstract syntax notation). Please note that the embodiments given below are only illustrative examples, and the aforementioned fields / parameters in the RA message may be carried in different ASN.1 formats. In addition, the terminology / name and / or value range of each parameter discussed may also be modified to have values ​​different from those given in the examples.

[0125] In one embodiment, the feature combination type (which indicates one or more types of feature combinations (FeatureCombination) associated with the RA process) can be implemented as:

[0126]

[0127] NSAG-List-r17::=SEQUENCE(SIZE(1..maxSliceInfo-r17))OF NSAG-ID-r17(NSAG-ID(Identification, identification)-r17 size(1..maxSliceInfo-r17))

[0128]

[0129] Alternatively, the trait composite type can be implemented as:

[0130]

[0131]

[0132]

[0133] Note that the fields in the feature combination type may be changed to be represented by Boolean type. That is, for each feature / field / parameter, an indication is used to indicate whether the associated RA resource is used in the RA process, and the indication is of Boolean type, where a bit value of '1' means that the feature is part of the feature combination associated with the RA process, and a bit value of '0' means that the feature is not part of the feature combination. Vice versa.

[0134] For example, redcap-r17 in the feature combination type may be represented by using a Boolean type as: "redCap-r17 BOOLEAN OPTIONAL" in the ASN.1 format.

[0135] In one embodiment, the first preamble associated with the feature combination of the RA process can be represented / indicated by an integer type. For example, the value range of the integer type representing the first preamble can be from 1 to 64. This parameter can be used to calculate the first preamble associated with the feature combination. For example, assume that the number of SSBs per PRACH opportunity is N. If N<1, the first preamble in each PRACH opportunity is a preamble with the same index indicated by this field. If N>=1, N preamble blocks associated with the feature combination are defined in each PRACH opportunity, each preamble block having a starting index Refers to the total number of preambles configured for this RA type.

[0136] In one embodiment, the number of consecutive preambles associated with the corresponding feature combination starting from (one or more) starting preambles for each SSB can be represented / indicated by an integer type. For example, the value range of the integer type representing the number of consecutive preambles can be from 1 to 64.

[0137] In one embodiment, the number of consecutive preambles associated with a preamble group (e.g., group A) for each SSB and starting from the (one or more) starting preambles of the corresponding feature combination can be represented / indicated by an integer type. In this embodiment, the value range of the integer type can be from 1 to 64.

[0138] In one embodiment, a feature priority for indicating the priority of a feature associated with a RA process (e.g., RedCap, Slice, SDT, and / or MSG-3 repetition for coverage enhancement) may be represented / indicated by an integer type, for example, the integer type having a value range from 0 to 7. When a feature is mapped to more than one FeatureCombinationPreambles, the feature priority is used to determine which FeatureCombinationPreambles the UE should use. In the present disclosure, the lower the value of the feature priority, the higher the priority of the corresponding feature.

[0139] In one embodiment, the indication of whether the 2-step RACH preamble identified by FeatureCombinationPreambles is mapped to a PUSCH slot separate from the slot defined in MsgA-ConfigCommon-r16 may be represented / indicated by:

[0140] - Enumeration type: For example, the presence of the enumeration type indication means that the 2-step RACH preamble identified by the FeatureCombinationPreambles is mapped to a PUSCH slot separated from the slot defined in MsgA-ConfigCommon-r16, and the absence of the enumeration type indication means that the 2-step RACH preamble identified by the FeatureCombinationPreambles is not mapped to a PUSCH slot separated from the slot defined in MsgA-ConfigCommon-r16; or

[0141] - Boolean type: A bit value of '1' means that the 2-step RACH preamble identified by this FeatureCombinationPreambles is mapped to a PUSCH slot separated from the slots defined in MsgA-ConfigCommon-r16, while a bit value of '0' means that the 2-step RACH preamble identified by this FeatureCombinationPreambles is not mapped to a PUSCH slot separated from the slots defined in MsgA-ConfigCommon-r16. Note that the meanings of the bit values ​​'1' and '0' are interchangeable.

[0142] In one embodiment, for each RA process or each beam or each RA attempt or each consecutive RA attempt in the same beam, the indication of whether Msg3 repetition is enabled may be represented / indicated by:

[0143] - Enumeration type: For example, the presence of an enumeration type indication means that Msg3 repetition is used in the RA attempt or in the RA process, while the absence of an enumeration type indication means that Msg3 repetition is not used.

[0144] - Boolean type: Bit value '1' means that Msg3 repetition is used in this RA attempt or this RA process, while bit value '0' means that Msg3 repetition is not used. Alternatively, bit value '1' means that Msg3 repetition is not used in this RA attempt or this RA process, while bit value '0' means that Msg3 repetition is used in this RA attempt or this RA process.

[0145] In an embodiment, for each beam or each RA attempt or each consecutive RA attempt or each RA process in one beam, an indication of whether the DL RSRP is above the threshold configured for Msg3 repetition selection is included in the RA information and may be represented / indicated by:

[0146] - Enumerated type: For example, the presence of an enumerated type indication means that the measured DL RSRP in this RA attempt or this RA process is above the threshold configured for Msg3 repetition selection, while the absence means not.

[0147] - Boolean type: A bit value of '1' means that the DL RSRP measured for this RA attempt or during this RA process is above the threshold configured for Msg3 repetition selection, while a bit value of '0' means that it is not. Alternatively, a bit value of '1' means that the DL RSRP measured for this RA attempt or during this RA process is above the threshold configured for Msg3 repetition selection, while a bit value of '0' means that the DL RSRP measured for this RA attempt or during this RA process is not above the threshold configured for Msg3 repetition selection.

[0148] In one embodiment, the threshold used by the UE to determine whether to select a resource indicating Msg3 repetition in the BWP may be represented / indicated by an integer type, and the possible value range may be from 0 to 127.

[0149] In an embodiment, for each RA attempt or each beam or each RA procedure, the number of Msg3 repetitions (which indicates the number of repetitions of PUSCH transmissions scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI) may be represented / indicated by:

[0150] - Integer type: The possible values ​​indicated by the integer type can be from 1 to 16.

[0151] - Enumerated type: The possible values ​​of the enumerated type indication are {n1,n2,n3,n4,n7,n8,n12,n16}; or

[0152] - A series of integers: An example of an indication of the series of integers is shown in the following ASN.1 format:

[0153] numberOfMsg3-RepetitionsList-r17 (Number of Msg3 repetition lists-r17)SEQUENCE(SIZE(4))OF NumberOfMsg3-Repetitions-r17 (Size of Msg3 repetitions-r17(4)),

[0154] NumberOfMsg3-Repetitions-r17(Number of Msg3 repetitions-r17)::=ENUMERATED{n1,n2,n3,n4,n7,n8,n12,n16}

[0155] In one embodiment, for each beam or each attempt or each consecutive attempt in a beam or each RA process, the number of Msg3 retransmissions indicates the number of Msg3 retransmissions for each beam or each attempt or each consecutive attempt in a beam or each RA process. The beam type can be SSB and / or CSI-RS (channel state information reference signal).

[0156] In an embodiment, for the RA attempt or for each consecutive RA attempt in one beam or for each RA process, the MCS for (one or more) Msg3 repetitions may be represented / indicated by:

[0157] -Integer type indication: The value range of the integer type indication can be from 0 to 31.

[0158] In an embodiment, the MCS for (one or more) Msg3 repetitions may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0159] In one embodiment, the slice group identifier may be represented / indicated by:

[0160] - Bit string: For example, the bit string indicates the slice group identifier where the RA process is initiated. In one embodiment, the slice group identifier can be represented by a bit string of 8 bits, for example, NSAG-ID-r17::=BIT STRING(SIZE(8)) (bit string (size(8))); or

[0161] - Bit string list: The bit string list indicates the list of slice groups associated with the RA resources used in this RA process. Each group identifier of a slice group may have the format indicated by the above alternative of a bit string (e.g., NSAG-ID-r17::=BIT STRING(SIZE(8))).

[0162] In one embodiment, the backoff value (field / parameter) includes one or more backoff values ​​utilized in the RA process. During the RA process, in the event of resource congestion, the UE may receive (one or more) RA responses containing a backoff index (BI) corresponding to the backoff value. The UE delays the next RA attempt for a time period equal to the time indicated by the backoff value. In addition, if the UE is configured with a priority parameter including a scaling factor for the BI, the actual delay time is determined as the product of the backoff value indicated by the received BI and the scaling factor (i.e., (backoff value) × (scaling factor)). For example, the BI and the corresponding backoff value may be indicated as shown in Table I below:

[0163] Table I: Backoff parameter values

[0164] index Backoff parameter value (milliseconds) 0 5 1 10 2 20 3 30 4 40 5 60 6 80 7 120 8 160 9 240 10 320 11 480 12 960 13 1920 14 Reserved seat 15 Reserved seat

[0165] In one embodiment, one or more backoff values ​​may be used in an RA process. Therefore, the backoff value used in the RA process may be represented / indicated by the following items:

[0166] - the actual backoff value included for each RA attempt, or

[0167] - A received backoff index included for each RA attempt, which is optionally present if a backoff was received for that RA attempt. Additionally, the UE may include a scaling factor if one was utilized in the RA procedure.

[0168] In one embodiment, different IEs (information elements) are used to indicate the scaling factors used for each RA process for 2-step RA (process) types and 4-step RA (process) types, respectively. Since the NW can configure the scaling factors for BI for 2-step RA resources and / or 4-step RA resources, respectively, and the UE can switch RA types during one RA process, the UE can set different scaling factors for different RA types. Therefore, in this embodiment, different IEs are used to indicate the scaling factors used for each RA process for 2-step RA types and 4-step RA types, respectively. For example, the IE may be an enumeration type that may take values ​​of [0, 0.25, 0.5, 0.75]. Note that other values ​​are still possible for different scenarios. An example of the IE in this embodiment is given below:

[0169] scalingFactorBI-TwoStepRA ENUMERATED{zero,dot25,dot5,dot75}OPTIONAL (scaling factor BI-2 step RA enumerated {0,.25,.5,.75} optional),

[0170] scalingFactorBI-FourStepRA ENUMERATED{zero,dot25,dot5,dot75}OPTIONAL (scaling factor BI-4 step RA enumerated {0,.25,.5,.75} optional).

[0171] In one embodiment, the NW may configure different scaling factors for the UE for dedicated resources and / or for beam failure recovery (BFR) configuration and / or for different slice groups. To indicate whether the scaling factor used is specifically configured for a specific type of UE / specific RA purpose / specific (network) slice, the following options may be considered:

[0172] -Different IEs are used to represent scaling factors configured separately for different purposes, and the difference between IEs for different scaling factors is achieved by using different IE names. For example, if the UE sets the scaling type using a value specifically configured for BFR, the UE includes scalingFactorBIBFR (scaling factor BI BFR), which may have the same format as given in the above example for the scaling factor used for each RA process. In addition, a list of one-bit indications may additionally be included in the IE, where each bit (indication) indicates whether the scaling factor used is specifically configured for a specific purpose. The purpose may be for BFR, for network slicing, for reconfiguration of synchronization, ..., etc. An example of an IE for indicating scaling factors configured for different purposes is given below:

[0173]

[0174] Taking the IE for BFR as an example, this indication is used to indicate whether the scaling factor used is specifically configured for BFR. As shown in the above example, the indication can be represented by a Boolean type or an enumeration type. If a Boolean type is used, a bit value of "1" means that the scaling factor is specifically configured for BFR, while a bit value of "0" means the opposite. If an enumeration type is used, the presence of the indication (which is indicated by enumerate{true}) means that the scaling factor is specifically configured for BFR, while the absence of the indication means the opposite. Similar logic applies to synchronous (sync) reconfiguration and slicing.

[0175] Note that the indication associated with the scaling factor (i.e., ScallingFactorBIPurpose-rxx) can be changed to be implemented by a sequence type other than the selection type shown in the above example. In addition, in some embodiments, the following IEs can be used simultaneously: an IE indicating a scaling factor for different types of RA (processes) and an IE indicating a scaling factor for a specific purpose.

[0176] In one embodiment, the UE includes a BI indication for each RA attempt in the RA information, and the BI indication is used to indicate whether a BI is received in the RA response for the RA attempt. In addition, the UE includes the BI index received for each RA process and the scaling factor utilized. The BI index can be represented by an integer type (indication) with a value range from 0 to 15. The format for indicating the scaling factor can reuse the above-mentioned exemplary IE associated with the scaling factor. The BI indication for each RA attempt can be represented by a Boolean type or an enumeration type. If a Boolean type is used, a bit value of "1" indicates that a BI is received in a random access response for the RA attempt, while a bit value of "0" means the opposite. If an enumeration type is used, the presence of the indication (which is indicated by enumerate{true}) means that a BI is received in a random access response for the RA attempt, while the absence of the indication means the opposite.

[0177] In an embodiment, the BI indication may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0178] In some embodiments, the UE may be configured with different power boost step sizes, and the UE may use different power boost step sizes in one RA process. Therefore, the UE may include information about the used (one or more) power boost step sizes in the RA information. The following method may be considered to indicate the (one or more) power boost step sizes used in the RA process.

[0179] In one embodiment, different IEs are used to indicate the power boost step size (or steps) utilized for each RA procedure for 2-step RA type and 4-step RA type, respectively. For example, the IE may be an enumerated type with possible values ​​of [0, 2, 4, 6] in dB. Note that other values ​​of the IE are still possible. An example of an IE indicating the power boost step size (or steps) utilized for each RA procedure is given below:

[0180] powerRampingStep-TwoStepRA ENUMERATED{dB0,dB2,dB4,dB6}OPTIONAL (power boost step-2 step RA enumerated {dB0,dB2,dB4,dB6} optional), powerRampingStep-FourStepRA ENUMERATED{dB0,dB2,dB4,dB6}OPTIONAL (power boost step-4 step RA enumerated {dB0,dB2,dB4,dB6} optional).

[0181] Similar to BI (field), different power boost step sizes can be configured for different purposes, such as for BFR, for reconfiguration of synchronization, and / or for different network slice groups. Therefore, additional information can be considered to allow the NW to know whether the reported power boost step size is for (one or more) specific purposes. Therefore, the following embodiments can be considered.

[0182] In one embodiment, different IEs may be used to represent power boost steps configured for different purposes, and the differences between the IEs are achieved by using different IE names. For example, if the UE sets the power boost step using a value specifically configured for BFR, the UE includes an IE powerRampingStepBFR, which may have the same format as given in the above example for the power boost step.

[0183] In another embodiment, a list of one-bit indications may also be included, where each bit indicates whether the power boost step size used for the RA process is specifically configured for (one or more) specific purposes. (One or more) purposes may be for BFR, for (network) slicing, and for reconfiguration of synchronization, etc.

[0184] An example of an IE indicating a power boost step size for a RA procedure is given as follows:

[0185]

[0186] Note that the two aforementioned embodiments of the IE indicating the power boost step size for the RA procedure (i.e., different IEs for different power boost step sizes for different purposes and a list of one-bit indications of different power boost step sizes for different purposes) can be used together in embodiments.

[0187] In one embodiment, the information of the power boost step size(s) used in the RA information may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0188] In one embodiment, the access identifier (field) indicates the access identifier associated with the RA process. The access identifier (field) may be an integer type (indication) with a value range from 1 to n.

[0189] In one embodiment, the RA information of the RA process includes an indication of whether ra-PrioritizationForSlicing / ra-PrioritizationForSlicingTwoStep should override ra-PrioritizationForAccessIdentity in the RA process. The indication can be a Boolean type or an enumeration type. In a Boolean type embodiment, a bit value of "1" may indicate that the priority parameter from ra-PrioritizationForSlicing / ra-PrioritizationForSlicingTwoStep overrides the priority parameter in ra-PrioritizationForAccessIdentity and is used in the RA process, while a bit value of "0" means the opposite. Or vice versa. In an enumeration type embodiment, the presence of such an indication (i.e., enumerate{true}) indicates that the priority parameter is overwritten, while the absence of the indication means the opposite.

[0190] In one embodiment, the power offset between msg3 or msgA-PUSCH and RACH preamble transmission in the RA procedure is included in the RA information of the RA procedure.

[0191] In one embodiment, an indication of whether deltaPlreamble is configured is included in the RA information of the RA process. The indication may be of Boolean type or of enumerated type. In a Boolean embodiment, a bit value of "1" may indicate that deltaPlreamble is configured, while a bit value of "0" means that deltaPlreamble is not configured. Or vice versa. In an enumerated embodiment, the presence of such an indication (i.e., enumerate{true}) indicates that deltaPlreamble is configured, while the absence of the indication means the opposite.

[0192] In one embodiment, the RA information stored and / or reported by the UE may also include NR-U related information. For example, the NR-U related information may include at least one of the following:

[0193] (a) Configuration of LBT failure related information:

[0194] In one embodiment, the configuration of LBT failure related information may be implemented as LBT-FailureRecoveryConfig-r16 in the following ASN.1 format:

[0195]

[0196] (b) Information indicating that the RA process is initiated to perform recovery from a persistent LBT failure:

[0197] For example, this information may be implemented as the following ASN.1 format raPurpose(-r16):

[0198] raPurpose-r16 ENUMERATED{accessRelated,beamFailureRecovery,reconfigurationWithSync,ulUnSynchronized,schedulingRequestFailure,noPUCCHResourceAvailable,requestForOtherSI,msg3RequestForOtherSI-r17,lbtFailureRecovery-rxx,spare7,spare6,spare5,spare4,spare3,spare2,spare1}(list{accessRelated,beamFailureRecovery,reconfigurationWithSync,ulUnSynchronized,schedulingRequestFailure,noPUCCHResourceAvailable,requestForOtherSI,msg3RequestForOtherSI-r17,lbtFailureRecovery-rxx,spare7,spare6,spare5,spare4,spare3,spare2,spare1}).

[0199] In one embodiment, if the RA procedure is performed for persistent LBT failure recovery, the UE sets raPurpose(-r16) to lbtFailureRecovery (LBT failure recovery).

[0200] In one embodiment, when a persistent LBT failure indication is triggered in a SpCell (special cell), the UE sets raPurpose(-r16) to consistentLBTFailure (persistent LBT failure).

[0201] In addition, in some embodiments, it is beneficial to further clarify whether the RA (process) is triggered by the lack of PUCCH resources of the SR (scheduling request) for the UL resources for requesting the LBT failure MAC CE. In one embodiment, the UE sets raPurpose to noPUCCHResourceAvailable (no PUCCH resources are available). Alternatively, if the SR is used to transmit the LBT failure MAC CE, the UE sets raPurpose to consistentLBTFailure. In addition, in the case where raPurpose is set to noPUCCHResourceAvailable or SRFailure (SR failure), an additional bit can be introduced to indicate whether the SR is used to transmit the LBT failure MAC CE. By introducing an additional bit, when the RA (process) is triggered due to the lack of PUCCH resources, if the UE sets raPurpose to noPUCCHResourceAvailable, the NW can avoid missing the LBT failure triggered in the SCell (secondary cell), and can correctly confirm whether the RA is triggered due to the lack of PUCCH resources. Note that the indication bit can also be applied to the BFR in the SCell.

[0202] In one embodiment, a bit may be introduced to indicate whether SR is used to transmit LBT failure MAC CE, which is optionally present when raPurpose is set to noPUCCHResourceAvailable or SRFailure. When SR is used for LBT failure MAC CE transmission, the bit is set to "1", otherwise the bit is set to "0". Or vice versa.

[0203] In one embodiment, a bit may be introduced to indicate whether the SR is used to transmit a BFR MAC CE (or a truncated BFR MAC CE), which is optionally present when raPurpose is set to noPUCCHResourceAvailable or SRFailure. When the SR is used for BFR MAC CE (or a truncated BFR MAC CE) transmission, the bit is set to "1", otherwise the bit is set to "0". Or vice versa.

[0204] As an alternative, a field (e.g., srPurpose (SR purpose)) can be introduced in the RA information / report of the RA procedure to indicate whether the SR is for BFR MAC CE or for LBT failure MAC CE. This field can be selected in {BFR, consistentLBTFailure}. In addition, this field can also include specific spare bits for future extensions.

[0205] (c) LBT failure indication for each RA attempt, which is used to indicate whether an LBT failure indication from the PHY (Physical) layer is received for each RA attempt:

[0206] In one embodiment, the LBT failure indication may be implemented by:

[0207] - Boolean type: A bit value of "1" means that at least one LBT failure indication has been received from lower layers for this RA attempt, while a bit value of "0" means the opposite.

[0208] - Enumeration type: For example, the presence of an LBT failure indication (i.e., enumerate{true}) means that at least one LBT failure indication has been received from a lower layer for this RA attempt, while the absence of an LBT failure indication means that no LBT failure indication has been received for this RA attempt.

[0209] In one embodiment, the LBT failure indication may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0210] In one embodiment, the UE includes an LBT failure indication for each consecutive RA attempt in a beam, instead of including the LBT failure indication for each RA attempt, wherein the beam type may be CSI-RS (channel state information reference signal) or SSB. The LBT failure indication in this embodiment may be designed as an LBT failure indication for each RA attempt.

[0211] In an embodiment, the LBT failure indication may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0212] In this embodiment, since the UE does not transmit a preamble when an LBT failure indication is received, it is still unclear whether each received LBT failure is counted as an RA attempt if the preamble is not transmitted. Therefore, an LBT failure indication for each (one or more) (continuous) RA attempt is introduced. In one embodiment, an IE perRA-InfoList (per RA-information list) may be included in the RA-related information for each RA attempt (i.e., each preamble transmission, if NR-U is not considered), where the maximum size of perRA-InfoList is equal to the maximum transmission time (e.g., 200). Since the LBT failure indication does not increase the transmission count, the maximum size of perRA-InfoList may be increased to the sum of the maximum transmission time and the maximum LBT failure time (e.g., 200+128=328) to support LBT failure indication for each RA attempt. In one embodiment, the UE may count the number of LBT failure indications received from the lower layer for each beam or for each consecutive attempt in a beam based on the current RA structure.

[0213] (d) The number of LBT failure indications received for each beam (SSB or CSI-RS) or for each consecutive attempt within a beam (e.g., SSB or CSI-RS) in one RA process:

[0214] In one embodiment, an integer type may be used to indicate this information, and the value range may be from 1 to n. An example is given below in ASN.1 format:

[0215] numberOfLBTFailureReceivedOnSSB INTEGER(1..n),OPTIONAL (number of LBT failures received on SSB integer (1..n), optional);

[0216] numberOfLBTFailureReceivedOnCSI-RS INTEGER(1..n), OPTIONAL (number of LBT failures received on CSI-RS integer (1..n), optional).

[0217] (e) Indication of whether the RA process was successful:

[0218] In one embodiment, the indication is implemented by using a Boolean type (indication), where a bit value of "1" means that the RA procedure is successful, and a bit value of "0" means that the RA procedure fails.

[0219] Alternatively, an enumeration type may be used to indicate whether the RA procedure was successful. For example, the UE includes an indication set to enumerate{true}, which means that the RA procedure was successful, otherwise the indication is absent, which means that the RA procedure failed.

[0220] As yet another alternative, an indication is used to indicate whether the RA failed. The UE includes this indication only when the RA procedure failed, otherwise the indication is absent, which means that the RA was successful.

[0221] (f) Indication of whether LBT recovery is successful

[0222] In one embodiment, the indication of whether the LBT recovery is successful may be implemented as an indication for indicating whether the RA process is successful.

[0223] (g) (For each RA attempt) Time from the most recent LBT failure to the most recent RA attempt:

[0224] In one embodiment, the information may be implemented as an integer type (indication) whose value range is from 0 to nm ms (milliseconds).

[0225] (h) Time from LBT failure to next available transmission opportunity:

[0226] In one embodiment, the information may be of integer type (indication), and its value range is from 0 to n ms.

[0227] (i) The number of LBT failures detected for each RA process or during the logging period or during the sampling period. In an embodiment, the number of LBT failures may be set for each RA process, each beam, each RA attempt, or each consecutive RA attempt in the same beam. The beam type may be SSB and / or CSI-RS.

[0228] (j) Time from the last LBT failure to the most recent BWP switch:

[0229] This information indicates the time elapsed from the last detected LBT failure indication to the most recent BWP switch. In one embodiment, this information may be an integer type (indication) with a value range from 0 to n ms.

[0230] (k) The number of transmission opportunities for each RA resource configured for each BWP.

[0231] (l) lbt-FailureDetectionTimer (LBT failure detection timer) running time:

[0232] This information indicates the running time of lbt-FailureDetectionTimer until the RA process is completed.

[0233] (m) The number of LBT failures detected (e.g., LBT_COUNTER):

[0234] In an embodiment, the granularity of this information may be per BWP and / or per cell.

[0235] (n) Maximum number of allowed LBT failures:

[0236] In one embodiment, the maximum allowed number / times of LTB failures is configured by lbt-FailureInstanceMaxCount (LBT-failure instance maximum count).

[0237] (o) Whether an indication of a persistent LBT failure is detected in this BWP:

[0238] In one embodiment, the indication may be included in the RA information of the RA procedure as:

[0239] - Boolean type: wherein a bit value of "1" means that a persistent LBT failure is detected in this BWP, while a bit value of "0" means the opposite, or vice versa.

[0240] - Enumeration type: For example, the UE includes an indication set to enumerate{true}, meaning that a persistent LBT failure is detected in this BWP, otherwise the indication is absent, meaning that no persistent LBT failure is detected in this BWP.

[0241] When new features are adopted or existing features are enhanced for further optimization, there may be additional requirements on the UE. In addition, the NW may also need to know which features the UE supports so that the NW can act accordingly.

[0242] In one embodiment, in order to record the feature combination information in the RACH resource, the following embodiments may be considered to indicate the UE capability.

[0243] (1) Capability signaling options

[0244] In this embodiment, the logging of RA reports associated with the features listed in the feature combination is optional for the UE. In addition, an indication is used to indicate to the NW whether the UE supports logging of RA reports associated with the features listed in the feature combination, for example, the indication is Figure 4Note that the NW may transmit a UEcapabilityEnquiry to the UE to request this indication.

[0245] An example of signaling is given below:

[0246] –SON-Parameters

[0247] The IE SON parameters contain SON related parameters.

[0248] SON parameter information element

[0249] --ASN1START (ASN.1 start)

[0250] --TAG-SON-PARAMETERS-START (Tag-SON-parameters-start)

[0251] SON-Parameters-r16::=SEQUENCE{

[0252] [Omit irrelevant parts]

[0253] featureCombinationRACH-Report-rxx ENUMERATED {supported} OPTIONAL ]]

[0255] }

[0256] --TAG-SON-PARAMETERS-STOP (Tag-SON-Parameters-Stop)

[0257] --ASN1STOP (ASN.1 stop)

[0258]

[0259] Note that field M in the above table indicates whether the corresponding parameter is mandatory, the field "FDD-TDDDIFF" indicates whether the corresponding parameter needs to be distinguished in FDD (Frequency-Division Duplex) and TDD (Time-Division Duplex), and the field "FR1-FR2 DIFF" indicates whether the corresponding parameter needs to be distinguished in FR1 (Frequency Range 1) and FR2 (Frequency Range 2).

[0260] In an embodiment of dual connectivity (DC), the MN (primary node) may forward the received UE capability information to the SN (secondary node), so that the SN can also know the UE capability information.

[0261] (2) Options for No Capability Signaling

[0262] In this embodiment, the recording of RA reports associated with the features listed in the feature combination is optional for the UE. Note that in this embodiment, the UE does not need to signal the capabilities to the NW.

[0263] (3) Conditional mandatory options

[0264] If the UE supports at least one of the features indicated in the feature combination, and the UE supports 4-step RA reporting and / or 2-step RA reporting, the UE supports logging RA reports associated with the features listed in the feature combination.

[0265] In an embodiment where the RA information includes NR-U related information, the following embodiments may be considered to indicate the UE capability for recording NR-U related information:

[0266] (1) Capability signaling options

[0267] In this embodiment, the recording of RA reports initiated on unlicensed spectrum is optional for the UE. Figure 4 UECapabiityInformation shown in ) is used to indicate to the NW whether the UE supports recording RA reports initiated on the unlicensed spectrum.

[0268] Alternatively or additionally, logging of RA reports initiated for (persistent) LBT failure recovery is optional for the UE and an indication is used to indicate to the NW whether the UE supports logging of RA reports initiated for LBT recovery.

[0269] The following signaling bit designs in ASN.1 format show some exemplary examples of this embodiment:

[0270] –SON parameters

[0271] The IE SON parameter includes SON-related parameters.

[0272] SON parameter information element

[0273] --ASN1START

[0274] --TAG-SON-PARAMETERS-START

[0275] SON-Parameters-r16::=SEQUENCE{

[0276] [Omit irrelevant parts]

[0277] unlicensedRACH-Report-rxx (unlicensed RACH-Report-rxx)ENUMERATED{supported}OPTIONAL ]]

[0279] }

[0280] --TAG-SON-PARAMETERS-STOP

[0281] --ASN1STOP

[0282]

[0283] As an alternative:

[0284]

[0285] Note that the field "M" in the above table indicates whether the corresponding parameter is mandatory, the field "FDD-TDDDIFF" indicates whether the corresponding parameter needs to be distinguished in FDD and TDD, and the field "FR1-FR2 DIFF" indicates whether the corresponding parameter needs to be distinguished in FR1 and FR2.

[0286] In the case of DC, the MN may forward the received UE capability information to the SN to notify the SN of the UE capability information.

[0287] (2) Options for No Capability Signaling

[0288] In this embodiment, the logging of RA reports initiated on unlicensed spectrum is optional for the UE, and the UE does not need to signal the capability to the NW.

[0289] Alternatively or additionally, logging of RA reports initiated for LBT recovery is optional for the UE and the UE does not need to signal the capability to the NW.

[0290] (3) Conditional mandatory options

[0291] In one embodiment, if the UE supports operation on the unlicensed spectrum and supports 4-step RA reporting and / or 2-step RA reporting, the UE supports logging of RA reports initiated on the unlicensed spectrum.

[0292] Alternatively or additionally, if the UE supports operation on unlicensed spectrum and supports 4-step RA reporting and / or 2-step RA reporting, the UE supports logging of RA reports initiated for continuous LBT recovery.

[0293] Figure 5 FIG. 4 shows a schematic diagram of reporting RA information according to an embodiment of the present disclosure. Figure 5 In the embodiment, the NW transmits a UEInformationRequest to the UE, wherein the UEInformationRequest includes an indication associated with requesting a RACH information report. The UE transmits a UEInformationResponse including the RACH information to the NW.

[0294] In some embodiments, a single RA report may include one or more RA entries, wherein each RA entry is used to include RA information associated with a completed RA process. In one embodiment, the RA report may include only RA information belonging to (one or more) successfully completed RA processes, while RA information belonging to (one or more) unsuccessfully completed RA processes is included in the RLF (Radio Link Failure) report or CEF (Connection Establishment Failure) report or SCG failure information. RACH information may also be carried in a successful handover report of the MN or SN. Alternatively, the RA report includes RA information for all RA processes, regardless of whether each RA process is successfully completed. The maximum number of RA entries included in an RA report may be predefined in the protocol or configured by the NW.

[0295] In one embodiment, a RA report including RA information related to NR-U may be separated from a RA report related to the remaining parameters. For optimization purposes, a separate report may be defined to include NR-U related information, which may include NR-U related RACH information discussed in the present disclosure. In addition, when a separate report is defined, a separate request bit may also be defined to request a report carrying NR-U related RACH information. In addition, in some examples, an availability bit may be used to indicate the availability of NR-U related RACH information on the UE side that may be requested by the NW.

[0296] In an embodiment, a separate RA report may also be defined to collect RACH partition information (e.g., to collect information about RACH procedures associated with a feature combination). In addition, when a separate report is defined, a separate request bit may also be defined to request a report carrying RACH partition information. In addition, in some examples, an availability bit may be used to indicate the availability of RACH partition information on the UE side that may be requested by the NW.

[0297] That is, there may be a type of RA report designed to carry RA information associated with NR-U and / or RACH partition information (eg, RACH information associated with a feature combination).

[0298] In one embodiment, RACH information may be carried on other existing RRC messages or newly defined RRC messages.

[0299] In the following examples, IEs that can be used to signal RACH information are described in ASN.1 format. Note that the following IEs are only illustrative examples, and RA information can also be carried in IEs with different ASN.1 formats. And in other examples, the location of the IEs can be different. In addition, only one or more of the IEs listed in the following examples may be implemented. In addition, the term / name or value range of each IE can also be modified. In addition, different IEs (e.g., parameters discussed in the present disclosure) can also be included.

[0300] Example:

[0301] In this example, RACH information is sent via Figure 4 The UEInformationResponse message shown is reported.

[0302] –UEInformationResponse

[0303] –UEInformationResponse

[0304] The UEInformationResponse message is used by the UE to convey information requested by the network.

[0305] Signalling radio bearer: SRB1 or SRB2 (when logged measurement information is included)

[0306] RLC-SAP (Radio Link Control - Service Access Point): AM (Acknowledged Mode)

[0307] Logical channel: DCCH (Downlink Control Channel)

[0308] Direction: UE to network

[0309] UEInformationResponse message

[0310] --ASN1START

[0311] --TAG-UEINFORMATIONRESPONSE (UE information response)-START (start)

[0312]

[0313]

[0314] [Omit some IE]

[0315] RA-ReportList-r16::=SEQUENCE(SIZE(1..maxRAReport-r16))OF RA-Report-r16 (size of RA-report-r16 (1..maxRAReport-r16))

[0316]

[0317]

[0318]

[0319]

[0320]

[0321] [Omit some IE]

[0322] --TAG-UEINFORMATIONRESPONSE (UE information response)-STOP (stop)

[0323] --ASN1STOP

[0324]

[0325]

[0326] Figure 6A schematic diagram of a wireless terminal 60 according to an embodiment of the present disclosure is provided. The wireless terminal 60 may be a user equipment (UE), a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, and is not limited thereto. The wireless terminal 60 may include a processor 600 (such as a microprocessor or an application specific integrated circuit (ASIC)), a storage unit 610, and a communication unit 620. The storage unit 610 may be any data storage device that stores program code 612, and the program code 612 may be accessed and executed by the processor 600. Embodiments of the storage unit 610 include, but are not limited to, a subscriber identity module (Subscriber Identity Module, SIM), a read-only memory (Read-Only Memory, ROM), a flash memory, a random access memory (Random-Access Memory, RAM), a hard disk, and an optical data storage device. The communication unit 620 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) according to the processing results of the processor 600. In one embodiment, the communication unit 620 communicates with the communication unit 620 via Figure 6 At least one antenna 622 is shown for transmitting and receiving signals.

[0327] In an embodiment, the storage unit 610 and the program code 612 may be omitted, and the processor 600 may include a storage unit with stored program code.

[0328] The processor 600 may implement any of the steps in the exemplary embodiments on the wireless terminal 60 , for example, by executing the program code 612 .

[0329] The communication unit 620 may be a transceiver. Alternatively or additionally, the communication unit 620 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless network node (eg, a base station), respectively.

[0330] Figure 7A schematic diagram of a radio network node 70 according to an embodiment of the present disclosure is provided. The radio network node 70 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN-Gateway, P-GW), a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB distributed unit, gNB-DU), a data network, a core network or a radio network controller (Radio Network Controller, RNC), and the present invention is not limited thereto. In addition, the radio network node 70 may include (execute) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), an application function (AF), etc. The radio network node 70 may include a processor 700 (such as a microprocessor or an ASIC), a storage unit 710 and a communication unit 720. The storage unit 710 may be any data storage device that stores program code 712 accessed and executed by the processor 700. Examples of the storage unit 710 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 720 may be a transceiver and is used to transmit and receive signals (e.g., messages or data packets) according to the processing results of the processor 700. In an example, the communication unit 720 communicates with the processor 700 via a Figure 7 At least one antenna 722 is shown in the figure to transmit and receive signals.

[0331] In one embodiment, the storage unit 710 and the program code 712 may be omitted. The processor 700 may include a storage unit with stored program code.

[0332] The processor 700 may implement any of the steps described in the exemplary embodiments on the radio network node 70 , for example via executing the program code 712 .

[0333] The communication unit 720 may be a transceiver. Alternatively or additionally, the communication unit 720 may combine a transmission unit and a reception unit configured to transmit and receive signals to and from a wireless terminal (e.g., a user equipment or another wireless network node), respectively.

[0334] Although various embodiments of the present disclosure have been described above, it should be understood that these embodiments are presented only by way of example, and not by way of limitation. Similarly, each diagram may depict an example architecture or configuration, and these example architectures or configurations are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these people will understand that the present disclosure is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0335] It should also be understood that any reference to an element using names such as "first", "second" etc. herein does not generally limit the quantity or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing two or more elements or two or more instances of an element. Therefore, reference to a first element and a second element does not mean that only two elements are used, or that the first element must be before the second element in some way.

[0336] In addition, it should be understood by those skilled in the art that various different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits and symbols such as those referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0337] Those skilled in the art should also understand that any of the various illustrative logical blocks, units, processors, means, circuits, methods, and functions described in conjunction with the various aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design codes containing instructions (for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0338] In order to clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits and steps are generally described above according to their functions. Whether this function is implemented in hardware, firmware or software or a combination of these technologies depends on the specific application and the design constraints imposed on the overall system. The technician can implement the described functions in various ways for each specific application, but such implementation decisions will not lead to deviations from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions in the functions described herein. As used herein with respect to a specified operation or function, the term "configured to" or "configured for" refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and / or arranged to perform a specified operation or function.

[0339] Further, it should be understood by those skilled in the art that the various illustrative logic blocks, units, devices, components and circuits described herein may be implemented in or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or a combination of any other suitable configurations for performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0340] Computer-readable media include computer storage media and communication media, including any media that can transfer a computer program or code from one location to another. Storage media can be any available media that a computer can access. For example, but not limited to, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other media that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0341] In this document, the term "unit" used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various units are described as discrete units; however, it is obvious to those of ordinary skill in the art that two or more units can be combined to form a single unit that performs the associated functions according to the embodiments of the present disclosure.

[0342] In addition, memory or other storage devices and communication components may be used in embodiments of the present disclosure. It will be understood that, for the purpose of clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution may be used between different functional units, processing logic elements or domains without detracting from the present disclosure. For example, functions shown as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions, without indicating a strict logical or physical structure or organization.

[0343] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein as described in the following claims.

Claims

1. A wireless communication method used in a wireless terminal, the method comprising: Reporting RA information of at least one random access RA procedure to the radio network node.

2. The wireless communication method according to claim 1, wherein: The RA information includes information associated with utilizing a random access channel RACH resource, wherein the RACH resource is associated with one or more features applicable to the RA procedure.

3. The wireless communication method according to claim 1 or 2, wherein: The RA information of each RA process includes at least one of the following: a feature type indicating one or more features in a feature combination associated with the RA process; a first preamble code, the first preamble code being associated with the feature combination associated with the RA process; for each synchronization signal / physical broadcast channel block SSB, the number of consecutive preambles associated with the characteristic combination; for each SSB, the number of consecutive preambles associated with the preamble group for the feature combination; a feature priority, the feature priority indicating a priority of the one or more features in the feature combination; For each RA process, each beam or each RA attempt, message 3 Msg3 repeats whether it is enabled; The number of Msg3 repetitions for each RA attempt or each beam; a modulation and coding scheme for the Msg3 repetition; The number of repetitions of physical uplink shared channel transmissions scheduled by RA Radio Network Temporary Identifier Uplink Grant and Downlink Control Information Format 0_0; Network slice related information associated with the RA process; at least one network slice group identifier associated with the RA process; at least one backoff value associated with the RA procedure; at least one scaling factor associated with the at least one backoff value; an indication of whether a backoff index is received for the RA procedure; at least one power boost step size used in the RA process; at least one purpose associated with the at least one power boost step; an access identifier associated with the RA process; or An indication as to whether the RA process was successful.

4. The wireless communication method according to claim 3, wherein: The one or more features of the feature combination associated with the RA process include at least one of the following: Reduced ability, Msg3 repeats, Small data transfer, or Network slicing.

5. The wireless communication method according to claim 3 or 4, wherein: The first preamble associated with the feature combination associated with the RA process is indicated by an integer ranging from 1 to 64.

6. The wireless communication method according to any one of claims 3 to 5, wherein: For each SSB, the number of consecutive preambles associated with the signature combination is indicated by an integer ranging from 1 to 64.

7. The wireless communication method according to any one of claims 3 to 6, wherein: For each SSB, the number of consecutive preambles associated with the preamble group for the feature combination is indicated by an integer ranging from 1 to 64.

8. The wireless communication method according to any one of claims 3 to 7, wherein: Each feature priority is indicated by an integer ranging from 0 to 7.

9. The wireless communication method according to any one of claims 3 to 8, wherein: The number of Msg3 repetitions for each RA attempt or each beam is indicated by: An integer ranging from 1 to 16, or At least one value in the value set.

10. The wireless communication method according to any one of claims 3 to 9, wherein: The modulation and coding scheme used for the Msg3 repetition is indicated by an integer ranging from 0 to 31.

11. The wireless communication method according to any one of claims 3 to 10, wherein: Each network slice group identifier is indicated by a bit string.

12. The wireless communication method according to any one of claims 3 to 11, wherein: The at least one backoff value is indicated by at least one backoff index.

13. The wireless communication method according to any one of claims 3 to 12, wherein: Each boosting step size used in the RA process is indicated as a value in a value set.

14. The wireless communication method according to any one of claims 1 to 13, wherein: The RA information includes information associated with the RA process in a shared spectrum.

15. The wireless communication method according to any one of claims 1 to 14, wherein: The RA information includes at least one of the following: Configuration for detecting persistent uplink listen-before-talk (LBT) failures in shared spectrum channel access; An indication of initiating the RA process for LBT failure recovery; an indication of whether an LBT failure indication is received for each RA attempt in the shared spectrum; the number of LBT failure indications received for each beam in the RA process or for each consecutive attempt in a beam or for each RA process in the shared spectrum, an indication of whether the RA procedure in the shared spectrum was successful; An indication of whether LBT recovery was successful; a number of transmission opportunities configured for each bandwidth portion during each RA process in the unlicensed spectrum; The running time of the timer associated with LBT failure detection; The number of LBT failures detected for each bandwidth part or each cell; or An indication of whether persistent LBT is detected in the bandwidth portion.

16. The wireless communication method according to claim 15, wherein: The configuration for detecting the persistent uplink LBT failure in the shared spectrum channel access comprises at least one of: the length of the timer used to detect the persistent uplink LBT failure, or Maximum number of LBT failure indications received from the physical layer before uplink LBT failure recovery is triggered.

17. The wireless communication method according to any one of claims 1 to 16, further comprising: An RA configuration determined based on the RA information is received from the wireless network node.

18. The wireless communication method according to any one of claims 1 to 17, further comprising: A capability indication associated with reporting the RA information related to an RA procedure utilizing RA resources associated with a feature combination of the RA procedure is transmitted to the radio network node.

19. The wireless communication method according to claim 18, further comprising: A request for the capability indication is received from the radio network node.

20. A wireless communication method for use in a wireless network node, the method comprising: receiving RA information of at least one random access RA procedure from a wireless terminal, and An RA configuration associated with the RA procedure for the wireless terminal is determined.

21. The wireless communication method according to claim 20, wherein: The RA information includes information associated with utilizing a random access channel RACH resource, wherein the RACH resource is associated with one or more features applicable to the RA procedure.

22. The wireless communication method according to claim 20 or 21, wherein: The RA information of each RA process includes at least one of the following: a feature type indicating one or more features in a feature combination associated with the RA process; a first preamble code, the first preamble code being associated with the feature combination associated with the RA process; for each synchronization signal / physical broadcast channel block SSB, the number of consecutive preambles associated with the characteristic combination; for each SSB, the number of consecutive preambles associated with the preamble group for the feature combination; a feature priority, the feature priority indicating a priority of the one or more features in the feature combination; For each RA process, each beam or each RA attempt, message 3 Msg3 repeats whether it is enabled; The number of Msg3 repetitions for each RA attempt or each beam; a modulation and coding scheme for the Msg3 repetition; The number of repetitions of physical uplink shared channel transmissions scheduled by RA Radio Network Temporary Identifier Uplink Grant and Downlink Control Information Format 0_0; Network slice related information associated with the RA process; at least one network slice group identifier associated with the RA process; at least one backoff value associated with the RA procedure; at least one scaling factor associated with the at least one backoff value; an indication of whether a backoff index is received for the RA procedure; at least one power boost step size used in the RA process; at least one purpose associated with the at least one power boost step; an access identifier associated with the RA process; or An indication as to whether the RA process was successful.

23. The wireless communication method according to claim 22, wherein: The one or more features of the feature combination associated with the RA process include at least one of the following: Reduced ability, Msg3 repeats, Small data transfer, or Network slicing.

24. The wireless communication method according to claim 22 or 23, wherein: The first preamble associated with the feature combination associated with the RA process is indicated by an integer ranging from 1 to 64.

25. The wireless communication method according to any one of claims 22 to 24, wherein: For each SSB, the number of consecutive preambles associated with the signature combination is indicated by an integer ranging from 1 to 64.

26. The wireless communication method according to any one of claims 22 to 25, wherein: For each SSB, the number of consecutive preambles associated with the preamble group for the feature combination is indicated by an integer ranging from 1 to 64.

27. The wireless communication method according to any one of claims 22 to 26, wherein: Each feature priority is indicated by an integer ranging from 0 to 7.

28. The wireless communication method according to any one of claims 22 to 27, wherein: The number of Msg3 repetitions for each RA attempt or each beam is indicated by: An integer ranging from 1 to 16, or At least one value in the value set.

29. The wireless communication method according to any one of claims 22 to 28, wherein: The modulation and coding scheme used for the Msg3 repetition is indicated by an integer ranging from 0 to 31.

30. The wireless communication method according to any one of claims 22 to 29, wherein: Each network slice group identifier is indicated by a bit string.

31. The wireless communication method according to any one of claims 22 to 30, wherein: The at least one backoff value is indicated by at least one backoff index.

32. The wireless communication method according to any one of claims 22 to 31, wherein: Each boosting step size used in the RA process is indicated as a value in a value set.

33. The wireless communication method according to any one of claims 20 to 32, wherein: The RA information includes information associated with the RA process in a shared spectrum.

34. The wireless communication method according to any one of claims 20 to 33, wherein: The RA information includes at least one of the following: Configuration for detecting persistent uplink listen-before-talk (LBT) failures in shared spectrum channel access; An indication of initiating the RA process for LBT failure recovery; an indication of whether an LBT failure indication is received for each RA attempt in the shared spectrum; the number of LBT failure indications received for each beam in the RA process or for each consecutive attempt in a beam or for each RA process in the shared spectrum, an indication of whether the RA procedure in the shared spectrum was successful; An indication of whether LBT recovery was successful; a number of transmission opportunities configured for each bandwidth portion during each RA process in the unlicensed spectrum; The running time of the timer associated with LBT failure detection; The number of LBT failures detected for each bandwidth part or each cell; or An indication of whether persistent LBT is detected in the bandwidth portion.

35. The wireless communication method according to claim 34, wherein: The configuration for detecting the persistent uplink LBT failure in the shared spectrum channel access comprises at least one of: the length of the timer used to detect the persistent uplink LBT failure, or Maximum number of LBT failure indications received from the physical layer before uplink LBT failure recovery is triggered.

36. The wireless communication method according to any one of claims 20 to 35, further comprising: An RA configuration determined based on the RA information is transmitted to the wireless terminal.

37. The wireless communication method according to any one of claims 20 to 36, further comprising: A capability indication associated with reporting the RA information related to an RA procedure utilizing RA resources associated with a feature combination of the RA procedure is received from the wireless terminal.

38. The wireless communication method according to claim 37, further comprising: A request for the capability indication is transmitted to the wireless terminal.

39. The wireless communication method according to any one of claims 20 to 38, further comprising: The RA information is transmitted to at least one of another radio network node, a core network, or a network function.

40. A wireless terminal, comprising: The communication unit is configured to report RA information of at least one random access RA process to a radio network node.

41. The wireless terminal according to claim 40, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 2 to 19.

42. A wireless network node, comprising: A communication unit, configured to receive RA information of at least one random access RA process from a wireless terminal; as well as A processor is configured to determine an RA configuration associated with the RA procedure of the wireless terminal.

43. The wireless network node of claim 42, wherein: The processor is further configured to perform the wireless communication method according to any one of claims 21 to 39.

44. A computer program product, comprising a computer-readable program medium, on which codes are stored, which, when executed by a processor, cause the processor to implement the wireless communication method according to any one of claims 1 to 39.

Images