Computer-readable method, terminal, node and medium for wireless communication

Description

1 / 64 COMPUTER-READABLE METHOD, TERMINAL, NODE AND MEDIUM FOR WIRELESS COMMUNICATION

[0001] This document is generally aimed at wireless communications, and in particular at 5th generation (5G) or 6th generation (6G) communications.

[0002] The current NTN (non-terrestrial network) is based on the premise that the transmission delay between the UE (user equipment) and the satellites can be pre-compensated by a UE and / or a NW (network). The NW will broadcast assistance information (e.g., satellite ephemeris, relevant common TA (time advance) parameters, etc.) based on which the UE can derive the satellite location (using satellite ephemeris), and the distance between the satellite and the UL synchronization reference point (RP) (using common TA parameters).

[0003] This document refers to methods, systems and devices for wireless communication.

[0004] One aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: receiving, by a wireless communication terminal from a network node, configuration information for a transfer procedure without a Random Access Channel, RACH procedure; initiating, by the wireless communication terminal, the transfer procedure without a RACH procedure in accordance with the configuration information; and transmitting, by the wireless communication terminal to a wireless communication node, uplink, UL, data for the transfer procedure without a RACH procedure in accordance with the configuration information. Petition 870250121348, dated 12 / 30 / 2025, page 9 / 170 2 / 64

[0005] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: transmitting, via a network node to a wireless communication terminal, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure, to enable the wireless communication terminal to initiate the transfer procedure without a RACH procedure, in accordance with the configuration information, and transmitting uplink (UL) data for the transfer procedure without a RACH procedure, in accordance with the configuration information.

[0006] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to: receive, through the communication unit from a network node, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure; initiate the transfer procedure without a RACH procedure, according to the configuration information; and transmit, through the communication unit to a wireless communication node, uplink (UL) data for the transfer procedure without a RACH procedure, according to the configuration information.

[0007] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: transmit, through the communication unit, to a wireless communication terminal, Petition 870250121348, dated 12 / 30 / 2025, page 10 / 170 3 / 64 configuration information for a transfer procedure without a Random Access Channel (RACH) procedure, to enable the wireless communication terminal to initiate the transfer procedure without a RACH procedure, according to the configuration information, and transmit uplink (UL) data for the transfer procedure without a RACH procedure, according to the configuration information.

[0008] Various modalities may preferably implement the following features.

[0009] Preferably, the configuration information comprises at least one of: An indication that a RACH procedure was skipped in the transfer procedure; Timing Advance (TA) information, which indicates a target TA to be applied to the wireless communication terminal; A UL resource grant configuration for a pre-allocated UL resource for transmitting UL data; Relevant power control information for transmitting UL data; A configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure; a Scheduling Request configuration, SR; a relevant beam configuration for beam training when the UE is scheduled by dynamic grant; a physical downlink control channel (PDCCH) configuration; an uplink control channel configuration Petition 870250121348, dated 12 / 30 / 2025, page 11 / 170 4 / 64 physical (PUCCH); or a RACH configuration for early TA compensation.

[0010] Preferably, the UL grant resource configuration comprises at least one of the following: a code domain resource configuration; a time-domain resource configuration; a frequency domain resource configuration; a subcarrier spacing configuration, SCS; Antenna port information; Information indicating whether a transform pre-encoding is used; at least one time-domain resource or frequency-domain resource to transmit hybrid automatic repeat request confirmation information, HARQ; a request for channel status information, CSI; a number of HARQ process numbers used for a physical uplink shared channel transmission (PUSCH); Information indicating whether HARQ feedback is disabled; Information to determine HARQ type information; Beam information associated with a pre-allocated UL resource; A validity period for a configuration of a pre-allocated UL resource for a transmission of UL data; or a priority index associated with a pre-allocated UL resource.

[0011] Preferably, beam information comprises at least one of: Petition 870250121348, dated 12 / 30 / 2025, page 12 / 170 5 / 64 a type of beam; a beam index or a list of beam indices; a threshold for beam selection for a transmission of PUSH; a mapping relationship between a PUSCH feature and a selected beam; a survey reference signal resource indicator, SRS, for beam selection; a mapping pattern for an SRS resource; a transmission configuration status indication, TCI; Bandwidth portion (BWP) information for a UL resource pre-allocated for a transmission of UL data; or UL carrier information for a UL resource pre-allocated for a transmission of UL data.

[0012] Preferably, relevant power control information comprises at least one of: a target power level for transmitting the data of UL; a delta power level used in a transmission power calculation; a type of RACH; or an alpha value for a transmission power calculation of a UL data transmission.

[0013] Preferably, the configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure comprises a timer configuration, where the communication terminal Petition 870250121348, dated 12 / 30 / 2025, page 13 / 170 6 / 64 wireless performs at least one of the following: In response to the timer expiring, initiate a RACH procedure on a target cell; In response to the timer expiring, release a pre-allocated UL resource; In response to the timer expiring, maintain a pre-allocated UL resource; or when initiating a RACH procedure, use a temporary cellular radio network identifier, C-RNTI, to monitor physical downlink control channels, PDCCHs.

[0014] Preferably, the SR configuration comprises at least one of: An indication showing whether an SR can be initiated when no UL resource is available; or a dedicated SR configuration;

[0015] Preferably, the wireless communication terminal performs at least one of: Use a dedicated SR resource to send an SR; Randomly select from the available SR resources to send an SR; Select a more recent SR resource from among the available SR resources to send an SR; or select an SR with the highest priority when a request resource is for a Common Control Channel (CCCH) message.

[0016] Preferably, the wireless communication terminal performs at least one of: to determine a UL resource among candidate UL resources that are pre-allocated or dynamically scheduled for Petition 870250121348, dated 12 / 30 / 2025, page 14 / 170 7 / 64 transmit the UL data; or determine a beam to transmit the UL data.

[0017] Preferably, the wireless communication terminal performs at least one of: Select a beam that satisfies at least one of the conditions below as the beam to transmit the UL data; The beam is associated with a Physical Broadcast Channel Block / Synchronization Signal, SSB, with received reference signal powers, RSRP, greater than or equal to a first configured threshold; or the beam is associated with a channel status information reference signal, CSI-RS, with an RSRP greater than or equal to a second configured threshold; Select any available beam as the beam to transmit the UL data in response to no beam associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with an RSRP greater than or equal to a second configured threshold; or perform a return to a transfer procedure with a RACH procedure in response to the absence of a beam associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with RSRP greater than or equal to a second configured threshold.

[0018] Preferably, the wireless communication terminal performs at least one of the following operations to determine the UL feature: select an nth UL feature from among the UL features Petition 870250121348, dated 12 / 30 / 2025, p. 15 / 170 8 / 64 candidates in response to an initial scheduling time and a scheduling interval being configured; Select a first available UL resource as the first grant resource, CG, configured and available based on a CG configuration in response to candidate UL resources being a subset or a full set of CG resources; or monitor a PDCCH using a C-RNTI and take a UL resource scheduled by the PDCCH as the UL resource to transmit the UL data.

[0019] Preferably, the wireless communication terminal performs at least one of: Use a standard HARQ process for a HARQ process to transmit UL data; be configured with a HARQ process identifier, and use the received HARQ process identifier for a HARQ process to transmit the UL data; to be provided with a range of HARQ process identifiers, and use a HARQ process identifier within the range for a HARQ process for a transmission of UL data; or determine a HARQ process for a transmission of UL data based on a scheduling interval, a start time, and a number of configured HARQ processes.

[0020] Preferably, the wireless communication terminal performs at least one of: Perform a logical channel prioritization procedure according to a HARQ process type; receive the configuration information comprising a Petition 870250121348, dated 12 / 30 / 2025, page 16 / 170 9 / 64 bitmap indicating a HARQ process type for each HARQ process associated with pre-allocated resources; Receive configuration information that comprises a common HARQ process type for each HARQ process associated with pre-allocated resources; receive configuration information that includes a statement used to disable a HARQ process type associated with a HARQ process; Perform a logical channel prioritization procedure according to a predetermined rule; or perform a logical channel prioritization procedure according to a standard HARQ process type.

[0021] Preferably, the wireless communication terminal performs power control for UL data transmission according to an active UL BWP to transmit UL data, a carrier to transmit UL data, and a wireless communication terminal service cell.

[0022] Preferably, the wireless communication terminal transmits a capability to support a transfer procedure with a RACH procedure being skipped.

[0023] The present disclosure relates to a computer program product comprising a computer-readable program medium code stored therein, the code, when executed by a processor, causes the processor to implement a wireless communication method described in any of the preceding methods.

[0024] The exemplary modalities disclosed in this document are intended to provide resources that will become readily apparent by reference to the following description when taken in Petition 870250121348, dated 12 / 30 / 2025, page 17 / 170 10 / 64 together with the attached drawings. According to various embodiments, examples of systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not as a limitation, and it will be evident to those skilled in the art reading this disclosure that various modifications to the embodiments disclosed may be made while remaining within the scope of this disclosure.

[0025] Thus, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of the present disclosure. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly indicated otherwise.

[0026] The above aspects and others and their implementations are described in more detail in the drawings, descriptions and claims.

[0027] FIG. 1 shows a schematic diagram of a timing relationship, according to an embodiment of the present disclosure.

[0028] FIG. 2 shows a capacity transfer from the EU, according to an embodiment of this disclosure.

[0029] FIG. 3 shows an example of a schematic diagram. Petition 870250121348, dated 12 / 30 / 2025, p. 18 / 170 11 / 64 of a wireless terminal according to an embodiment of this disclosure.

[0030] FIG. 4 shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.

[0031] FIGS. 5 and 6 show method flowcharts, according to some modalities of the present disclosure.

[0032] FIG. 7 shows an example of angle information according to an embodiment of the present disclosure.

[0033] In some modes, to accommodate propagation delay in NTNs, several timing relationships can be improved by a Common Timing Advance (Common TA) and by the K_offset and k_mac scheduling shifts illustrated in FIG. 1. - A common TA is a configured offset that corresponds to the RTT (round-trip time) between the Reference Point (RP) and the NTN payload. - K_offset is a configured scheduling offset that is greater than or equal to the sum of the service link's RTT and the common TA. - k_mac is a configured offset that corresponds to the RTT between RP and gNB.

[0034] The DL (downlink) and UL (uplink) are frame-aligned at the uplink time synchronization reference point (RP) with an offset.

[0035] The k_mac offset is used to delay the application of a downlink configuration indicated by a CE (Medium Access Control Control Element) MAC command on a PDSCH (Physical Downlink Shared Channel). Petition 870250121348, dated 12 / 30 / 2025, page 19 / 170 12 / 64 and an estimate of the UE-gNB RTT. It can be provided by the network when the downlink and uplink frame timings are not aligned in gNB. k_mac is also used in the random access procedure to determine the start time of the RAR (random access response) window or the MsgB window after a transmission of Msg1 or MsgA.

[0036] For the service cell, the network broadcasts valid ephemeris information and common TA parameters. The UE may have a valid GNSS (Global Navigation Satellite System) position, as well as a common ephemeris and TA before connecting to an NTN cell. To achieve synchronization, before and during a connection to an NTN cell, the UE can calculate the RTT between the UE and the RP based on the GNSS position, ephemeris, and common TA parameters, and autonomously pre-compensate the TA for the RTT between the UE and the RP.

[0037] The UE can calculate the service link frequency Doppler shift and autonomously precompensate for it on uplink transmissions, taking into account the UE position and ephemeris. If the UE does not have a valid GNSS position and / or a valid ephemeris and a common TA, it may not transmit until both are recovered.

[0038] In a connected mode, the UE may be able to continuously update the Timing Advance and Frequency Precompensation.

[0039] The UE can be configured to report Time Advance during Random Access procedures or in connected mode. In connected mode, event-triggered reporting of Time Advance is supported.

[0040] Although the pre-compensation of the Doppler shift Petition 870250121348, dated 12 / 30 / 2025, page 20 / 170 The 13 / 64 instantaneous Doppler shift experienced on the service link should be handled by the UE; the management of the Doppler drift experienced on the feed link and the transponder frequency error is the responsibility of the network implementation.

[0041] In some modes, due to the large transmission delay and the enormous coverage in NTN (non-terrestrial networks), methods may be considered to reduce signaling delay as well as signaling overhead.

[0042] The current NTN is based on the premise that the transmission delay between the UE and the satellites can be pre-compensated by a UE (user equipment) and / or a NW (network). The NW will broadcast assistance information (e.g., satellite ephemeris, relevant common TA parameters, etc.) based on which the UE can derive the satellite location (using satellite ephemeris), and the distance between the satellite and the UL synchronization reference point (RP) (using common TA parameters). Together with the UE location information derived based on the GNSS module, the UE can perform pre-compensation of the bidirectional transmission delay between the RP and the UE. Therefore, it is possible for the UE to have a similar TA in a target cell as in the source if the pre-compensation is done correctly.Furthermore, it is possible for a UE to perform a HO without RACH (transfer (HO) without the RACH (Random Access Channel) procedure) on the NTN in this case, since no RACH is required. The RACH procedure typically has 2 to 4 steps. If the RACH procedure can be skipped, it can save at least one round-trip delay on the NTN, and thus the overall HO delay, as well as the signaling overhead, can be reduced. In some cases... Petition 870250121348, dated 12 / 30 / 2025, page 21 / 170 14 / 64 modes, to support HO without RACH in NTN deployed in NR, there may be some problems when using HO without RACH in NTN, such as: NR supports multi-beam operation where UE scheduling is done per beam. Solutions need to be considered to allocate UL resources with beam association (e.g., CSI-RS and / or SSB); It is unclear how to manage the energy used for PUSCH transmission using the pre-allocated UL resource; and it is unclear how to handle the case when the UE cannot find an available UL grant for PUSCH transmission for a given period of time.

[0043] Some forms of the present disclosure are provided in view of the above problems.

[0044] Some aspects of this disclosure are described in the context of NTN, but are not limited to this and may also be applied to other types of networks, such as TN (territorial network), ATG (air-to-ground), etc. HO (transfer) without RACH

[0045] In one embodiment, an HO without RACH indicates an HO with a RACH procedure being skipped, or an HO without a RACH procedure.

[0046] In one modality, an HO without RACH may comprise the following steps.

[0047] Step 1: In one mode, the UE receives and stores the (conditional) transfer configuration ((C)HO) (e.g., a configuration for HO without RACH) from the NW (network (e.g., a network node)), which indicates that RACH can be skipped to this HO procedure. The HO types considered can be normal HO, CHO, DAPS HO, PSCell Addition and Change. Petition 870250121348, dated 12 / 30 / 2025, page 22 / 170 15 / 64 Conditional (CPAC) or other types of HO may be supported in the communication system.

[0048] Step 2: In one mode, the UE initiates a (C)HO procedure towards the target cell, according to a stored and / or received configuration. The UE starts a T304 timer, which is used to control the HO procedure. In some examples (e.g., unconditional HO), the T304 timer starts after receiving the message containing the HO configuration (e.g., RRCReconfiguration message). In some examples, for example, for a CHO, the T304 timer starts after the CHO execution.

[0049] Step 3: In one mode, during the execution of timer T304, the UE transmits a PUSCH (e.g., containing the RRCReconfigurationComplete message) to the gNB using the UL feature configured by the NW (e.g., according to the configuration received for the HO without RACH), where the UL feature can be configured for the UE in a pre-configured way or dynamically scheduled. In one mode, the PUSCH is for the HO without RACH. In one mode, the PUSCH serves to start the HO without RACH with the gNB.

[0050] Step 4: In one mode, if the UE determines that the HO without RACH was successful (for example, it successfully received a PDCCH transmission addressed to the C-RNTI (Temporary Cellular Radio Network Identifier)), the UE interrupts the T304 timer and releases the configuration for the HO without RACH. For stage 1:

[0051] In one embodiment, the configuration for HO without RACH may include at least one of the following: - An indication that the RACH can be skipped. The indication Petition 870250121348, dated 12 / 30 / 2025, page 23 / 170 16 / 64 can be an explicit indication or an implicit indication. In one embodiment, the presence of the configuration used for the UE to skip the RACH can be considered an indication for the UE to skip the RACH procedure. - TA (timing advance) information, which is used to indicate the TA to be applied to the target cell. In one embodiment, the TA information may instruct the UE to maintain the TA associated with a TAG (timing advance group) or instruct the UE to autonomously pre-compensate the TA based on assist information (e.g., satellite ephemeris, common TA parameters, etc.) associated with the target cell. In one example, this information may be a one-bit indication, where the value 1 indicates that the UE should use the source TA on the target cell, zero means that the UE needs to recalculate the TA based on assist information (e.g., satellite ephemeris, common TA parameters, etc.), or vice versa.In another example, this information can be an indication, where the presence of this information indicates that the UE uses the source TA in the target cell, the absence of the indication indicates that the UE needs to recalculate the TA based on assistive information (e.g., satellite ephemeris, common TA parameters, etc.), or vice versa. In another modality (e.g., in the case of dual-connectivity carrier aggregation, DCCA), the TA information used to indicate the TA to be applied in the target cell can select between the TAs of different TAGs associated with MCGs or SCGs, which can be enabled by introducing a TA Information Element (IE) with a choice structure, to choose a TA to be used among the TAs of different TAGs. The TA of different TAGs can be... Petition 870250121348, dated 12 / 30 / 2025, page 24 / 170 17 / 64 identified by TAG IDs or IE names (e.g., MCG_PTAG). In this example, the absence of the TA IE can be used to indicate that the UE needs to recalculate the TA based on assistance information (e.g., satellite ephemeris, common TA parameters, etc.). In some examples, to allow for future extensions, extension fields may be included. One example could be the introduction of a new IE with a field indicating the target TA as the primary null-valued TAG, and extension tags can be used for future extensions. Meanwhile, the absence of this IE can be used as an implicit indication that the UE should calculate the TA based on NW assistance information. — A UL Grant Resource Configuration. This configuration can be optionally configured. When configured with pre-allocated UL Grant Resource based on the received UL Grant Resource Configuration, the UE can select from the pre-allocated UL resources for PUSCH transmission. In some instances, the UE will also monitor the PDCCH to receive the scheduled UL grant via dynamic grant, and will transmit the PUSCH on the oldest available scheduled grant. In some instances, when pre-allocated UL Grant Resources are not provided, the UE may also monitor the PDCCH to receive the dynamic grant for PUSCH transmission. The UE may behave differently in Step 3, which will be discussed in detail below. - Relevant power control information. - Information for the UE to perform a return to an HO using the RACH procedure. - An SR (scheduling request) configuration. Petition 870250121348, dated 12 / 30 / 2025, page 25 / 170 18 / 64 - a relevant beam configuration. The beam may include one or more beam information, as discussed below for the pre-allocated grant UL resource configuration (e.g., SRS resource information, TCI state configuration, etc.). In some examples, the relevant beam configuration here is independent of the beam information associated with the pre-allocated grant. - a physical downlink control channel (PDCCH) configuration. The configuration may include at least one of the control resource sets (CORESET), seek space information, and the associated TCI state information. - a physical uplink control channel (PUCCH) configuration. The configuration may include at least one of the following associated TCI state information, SR configuration, CSI configuration, allowed multiplexing pattern information, etc. - a setup for an early TA acquisition.

[0052] In one embodiment, the configuration can be delivered to the UE using at least one of: system information (e.g., MIB (Master Information Block) or SIB (System Information Block) (e.g., SIB1, SIB2, etc.), a dedicated RRC signaling (e.g., RRCReconfiguration message), a paging message, other common signaling that is targeted by a group of UEs (e.g., multicast or groupcast), Stratum of No Access (NAS) message, or MAC signaling (e.g., MAC CEs), or via downlink control information (DCI). UL Grant Resource Configuration

[0053] In one mode, the resource configuration of Petition 870250121348, dated 12 / 30 / 2025, page 26 / 170 19 / 64 UL grant provides the pre-allocated grant configuration for PUSCH transmission when the UE performs the transfer to a target.

[0054] In one embodiment, the UL grant resource configuration may include at least one of: - A code domain resource.

[0055] In an embodiment, the code domain feature may include at least one of a DMRS (demodulation reference signal) feature configuration, an MCS (modulation and coding scheme) configuration, or a redundancy version. In an embodiment, the MCS configuration may have one or multiple indices, where each index refers to an MCS. In an embodiment, the modulation and coding scheme may include a modulation order, a TBS (transport block size) index, and / or a redundancy version. - A time-domain resource.

[0056] In a modality, the time domain resource may include at least one of: a duration of the time resource used (e.g., number of resource blocks), a start time of the time domain resource for each grant, a time domain allocation combination (e.g., indicating a combination of a start symbol and a length and a PUSCH mapping type), a scheduling interval (e.g., indicating the periodicity of the granted resource allocated in the time domain), a scheduling start time which may indicate the start time of the granted resource, a time domain allocation type information, e.g., type 0, type 1, or dynamic switching (in a modality, it may be specified that only one allocation type is considered for Petition 870250121348, dated 12 / 30 / 2025, page 27 / 170 20 / 64 this pre-allocated concession) or a TBS configuration (e.g., indicating the target transport block size). - A frequency domain resource configuration. - A subcarrier spacing (SCS) configuration. Antenna port information, which indicates the antenna ports used for this configuration. Information on whether a transform pre-encoding is used. - The time and / or frequency domain feature for transmitting HARQ (hybrid automatic repeat request) confirmation information. - A CSI request bit, which is used to determine whether a CSI report (channel status information) can be used in push transmission. The HARQ process number used for transmission of PUSCH. [ 0057] In one modality, the process number range of The HARQ used for PUSCH transmission can be from zero to 16. If an extended HP (HARQ process) is used, the range can be from zero to 32. Other value ranges may also be feasible. - Information indicating whether HARQ feedback is disabled or not. [ 0058] In one embodiment, for information indicating whether HARQ feedback is disabled, in the case where HP is configured with feedback disabled, at least one of the following options can be used in the question of how to handle the need for feedback transmission: A) The UE follows the feedback status configured for the selected HARQ (HP) process; B) The EU always sends feedback, regardless of Petition 870250121348, dated 12 / 30 / 2025, page 28 / 170 21 / 64 feedback status configured for the selected HP; and / or C) Based on an explicit configuration, an indication is used to indicate whether the UE should send feedback to the NW. For example, i) if the explicit indication is configured, the UE prioritizes the selection of the HP that is configured with feedback enabled; ii) if the explicit indication is configured, the UE always sends an ack, regardless of the HO status; iii) if the explicit indication is not configured, the UE does not need to send feedback, regardless of the HP feedback status configured; and / or iv) if the explicit indication is not configured, the UE follows the HP feedback status to know whether to send feedback. - Information to determine HARQ type information.

[0059] In some examples, the HARQ type mentioned and discussed in this application means the uplink HARQ mode (mode A or mode B) as specified in the 3GPP standards.

[0060] In one embodiment, the information for determining the HARQ type includes at least one of: explicitly indicated information (e.g., type A or type B) or an indication that can be used to disable the UL transmission type configured for the HARQ process. - A shelf life or a timer length.

[0061] In one mode, the validity duration indicates the time during which the pre-allocated UL resource configured to transmit the PUSCH is considered valid. In one mode, a timer can be used for this duration. In one mode, during the timer's execution, the UE can Petition 870250121348, dated 12 / 30 / 2025, page 29 / 170 22 / 64 determine that the configuration for the pre-allocated UL resource to transmit the PUSCH is valid and, based on the configuration for the pre-allocated UL resource, select the resource for the PUSCH transmission. In one mode, after the timer expires, the UE may determine that the configuration for the pre-allocated UL resource is invalid and release the configuration and / or the corresponding resource.

[0062] In one embodiment, the start point of this timer may be a point in time after the first selection of the UL grant by the UE for the PUSCH transmission. In one embodiment, the start point may be at the HO execution. In one embodiment, the start point may be at the reception of the RRCReconfiguration that is not for CHO, and includes HO configuration without RACH (e.g., for cases without CHO). In one embodiment, for CHO, the start time may be determined according to the CHO configuration or at the first CHO execution or at the last CHO execution. Or, in another example, the start time of this timer may be the point in time when T304 is initiated or, in some examples, the start time is the first time T304 is initiated for this HO procedure. - A priority index associated with the resource pre-allocated for transmitting PUSCH.

[0063] In one mode, the priority index can indicate the PHY (physical) priority of the PUSCH using the pre-allocated resource. In one mode, this information can be used, at least, for collision handling in the PHY layer (physical layer). For example, the value p0 indicates low priority and the value p1 indicates high priority. In one mode, this information may not be necessary to configure a resource. Petition 870250121348, dated 12 / 30 / 2025, page 30 / 170 23 / 64 is pre-allocated, and in that case, a default priority can be adopted. - Beam information associated with the UL grant feature for transmitting the PUSCH.

[0064] In one embodiment, for beam information associated with the UL grant resource described above, if the pre-allocated resource for PUSCH transmission is configured and the beam association (SSB (Physical Broadcast Channel Block / Synchronization Signal) and / or CSI-RS (Channel Status Information Reference Signal)) is provided, when selecting from the UL grant resources pre-allocated for PUSCH transmission, the UE can first select the beam and then select the UL resource mapped to the selected beam.In one embodiment, this configuration may include at least one of: A beam type (e.g., SSB and / or CSIRS); a beam index (one or more beam indices, e.g., an SSB index, a CSI-RS index, indicating the beams for the pre-allocated UL resource to transmit the PUSCH); a subset of beams for beams (e.g., SSBs or CSIRSs) for pre-allocated PUSCH mapping within a Configured Grant configuration; in some instances, this may be indicated by a bitmap; a number indicating the number of beams (e.g., SSBs or CSI-RSs) per pre-allocated PUSCH; the number of DMRS sequences for beam (e.g., SSBs or CSI-RSs) for PUSCH mapping, the set of DMRS ports for beam (e.g., SSBs or CSI-RSs) for PUSCH mapping. One or more thresholds for the UE to select a suitable beam for PUSCH transmission, which can be configured separately for SSB and / or CSI-RS; a mapping interface. Petition 870250121348, dated 12 / 30 / 2025, page 31 / 170 24 / 64 between the PUSCH feature and the configured beam (the SSB and / or CSIRS); an SRS feature indicator (probing reference signal); a mapping pattern for the SRS feature; a TCI state configuration (Transmission Configuration Indication) (e.g., IDs to identify a TCI state (e.g., TCI-StateId)). The TCI-State associates one or two DL reference signals with a corresponding quasi-location type (QCL); BWP information; and / or UL carrier information.

[0065] In some examples, the UE may first select the beam and then select the UL grant feature associated with the selected beam for PUSCH transmission.

[0066] In one embodiment, for beam selection, at least one of the following may be applied: i) The UE selects from among the SSBs and / or CSI-RSs that have an RSRP (received reference signal power) greater than one or more configured thresholds; ii) the UE selects from among the SSBs and / or CSI-RSs that have an RSRP greater than or equal to one or more configured thresholds; iii) if there is no beam that meets the threshold requirement, the UE can select any available beam; or iv) if there is no beam that meets the threshold requirement, the UE can return to perform the HO with a RACH when a certain predetermined condition is met.

[0067] In one embodiment, the mapping relationship between the UL resource for PUSCH transmission and the configured beam (the SSB and / or CSI-RS) may conform to at least one of: the mapping relationship may follow the predefined rules for CG-SDT and / or may follow the predefined rules for the Petition 870250121348, dated 12 / 30 / 2025, page 32 / 170 25 / 64 PUSCH mapping from MsgA to the preamble.

[0068] In one embodiment, the SRS feature indicator can be used for beam selection based on the match between the DL and UL beams. If, based on the SRS measurement, a DL beam with the best quality is selected (e.g., associated with SSBx, ex is an integer), it is assumed that the same beam (e.g., SSBx in this example) will be used for UL transmission.

[0069] In one embodiment, the mapping pattern for the SRS resource indicates whether the UE can follow a cyclic mapping pattern or a sequential mapping pattern when two sets of SRS resources are configured.

[0070] In an embodiment, the TCI state setting indicates one or more activated TCI states associated with the corresponding configured RS (reference signal) resource (e.g., CSI-RS). Each TCI state setting may include at least one of the following: a TCI state ID (e.g., to identify the TCI state setting), power control information, one or two QCL information, BWP information where the RS is located, the reference signal resource associated with this TCI state, and the QCL type (e.g., type A, type B, type C, or type D). In an embodiment, if a TCI setting is provided, it may be used in conjunction with other parameters mentioned. The UE relies on the TCI state ID to locate the reference signal resources (e.g., CSI-RS) associated with the activated TCI states.In some instances, the EU may further determine whether the RSRP of the selected reference resources (e.g., CSI-RS) qualifies or not, for example, if a. Petition 870250121348, dated 12 / 30 / 2025, page 33 / 170 26 / 64 RSRP is above the threshold configured for beam selection for the pre-allocated grant resource for PUSCH transmission.

[0071] In one embodiment, the BWP information indicates the BWP configuration associated with the pre-allocated grant resource for PUSCH transmission. In one embodiment, the BWP information includes at least one of the following: the starting point of the BWP location in the frequency domain relative to absolute point A (e.g., a reference), the BWP bandwidth, the frequency location of absolute point A, and / or the SCS information (e.g., 15 kHz).

[0072] In one mode, the UL carrier information indicates whether the selected UL is a NUL (normal uplink) or a SUL (supplementary uplink). In one mode, the UL carrier information can have the value NUL or SUL. In one mode, the UL carrier information can have the format of a 1-bit indication, where 0 indicates NUL, 1 indicates SUL, or vice versa.

[0073] In one embodiment, the UL grant resource pre-allocated for the PUSCH transmission may be the entirety or a subset of grant resources configured for UE. An example is given below. Example

[0074] In a mode, the configuration includes at least one of: an initial scheduling time (in a mode, if configured, the UE uses the first available CG resource among the candidate CG resources after the start timing as the UL resource for the PUSCH transmission); a scheduling interval (in a mode, if configured, the UE searches for a Petition 870250121348, dated 12 / 30 / 2025, page 34 / 170 27 / 64 first UL resource available for PUSCH transmission based on the scheduling interval configured between candidate CG resources); or the information used to indicate the candidate CG resource that is used for PUSCH transmission in HO without RACH.In one embodiment, the information may include at least one of: configuredGrantConfigIndex, which indicates the index of the CG resource, and is used to uniquely identify the configured CG resource within a list of CG resources within the selected BWP; configuredGrantConfigIndexMAC, which indicates the index of the CG resource uniquely within a MAC entity; a subset of beams (e.g., SSBs or CSI-RSs) for pre-allocated PUSCH mapping within a Configured Grant configuration (in some instances, this may be indicated by a bitmap); a number indicating the number of beams (e.g., SSBs or CSI-RSs) per pre-allocated PUSCH; the number of DMRS sequences for beam (e.g., SSBs or CSI-RSs) for PUSCH mapping, the set of DMRS ports for beam (e.g., SSBs or CSI-RSs) for PUSCH mapping; and / or parts or a complete set of information elements included in the ConfiguredGrantConfig setting for the CG.

[0075] In one embodiment, when the UL resource is not overlapping with another UL resource (for example, for MsgA or for SR), it is considered available. Other rules may also apply.

[0076] In one embodiment, the UL grant resource pre-allocated for PUSCH transmission may be all or a subset of the grant resources configured for CGSDT (configured grant small data transmission) Petition 870250121348, dated 12 / 30 / 2025, page 35 / 170 28 / 64 configured for UEs. Relevant power control information

[0077] In one embodiment, the relevant power control information may include at least one of: — a target power level, in particular the target power level for the PUSCH transmission; - a delta power configuration, in particular the delta power level used in the transmission power calculation for PUSCH transmission; - a type of RACH to be considered; in one mode, the UE follows the power control procedure for scheduled PUSCH transmission by the random access response for the type of RACH indicated in this indication; in one mode, if only one type of RACH is configured, this setting can be omitted; - an alpha value (e.g., a factor) for the PUSCH for the pre-allocated UL grant resource; in one embodiment, a range of example values ​​could be {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}, where alpha0 indicates the value 0 and alpha04 indicates the value 4, and so on. This alpha value can be used for a power control determination; - a nominal power level, a nominal power level for PUSCH transmission for pre-allocated UL granting; and / or - a P0 value for PUSCH transmission for granting pre-allocated UL. Configuration for EU to return to transfer with RACH

[0078] In one embodiment, a return configuration for HO with RACH may include a timer. In one embodiment, Petition 870250121348, dated 12 / 30 / 2025, page 36 / 170 The 29 / 64 timer is used to trigger the UE to return to HO with RACH. In one mode, the starting point of this timer can be after the UE's first selection of the UL grant resource for PUSCH transmission. In another mode, the starting point can be during HO execution. In another mode, the starting point can be upon receiving the RRCReconfiguration that is not for CHO, and includes HO configuration without RACH (for cases without CHO). In another mode, for CHO, the start time can be during CHO configuration, or during the first CHO execution, or during the most recent CHO execution.

[0079] In one embodiment, at the end of this timer, the UE can initiate RACH on the target cell for synchronization and obtaining the UL resource for PUSCH transmission.

[0080] In one mode, when starting RACH, the UE can release the pre-allocated resource, if any.

[0081] In one mode, the UE may retain the pre-allocated resource, if any. In one mode, the UE may utilize the most recent UL resource from among pre-allocated or scheduled grants in response to random access or through dynamic scheduling.

[0082] When initiating RACH, the UE can still use C-RNTI to monitor PDCCHs (physical downlink control channels). In one mode, the UE can terminate the corresponding ongoing RACH or consider it completed upon successfully receiving the scheduled PDCCH from the C-RNTI. In another mode, if the UE receives the scheduled DL transmission from a PDCCH containing a TC-RNTI (Temporary C-RNTI), the UE can ignore the received TC-RNTI. Scheduling Request (SR) configuration Petition 870250121348, dated 12 / 30 / 2025, page 37 / 170 30 / 64

[0083] In one embodiment, the SR configuration may include at least one of: — An indication of whether SR can be initiated when no UL resource is available. In one mode, the indication can be used in combination with the timer discussed above. In one mode, after the timer expires, and if the SR configuration indicates that SR triggering is allowed, the UE can trigger SR to request the UL resource for PUSCH transmission. In one mode, SR can be canceled when the PUSCH has been successfully transmitted, or when the PDCCH scrambled by C-RNTI is successfully received. — Dedicated SR configuration. In one example, the SR configuration includes at least one SR periodicity; a priority index, which indicates whether this scheduling request resource is high or low priority in PHY multiplexing / prioritization handling; a PUCCH resource to which the UE should send the scheduling request; the ID of the PUCCH resource to which the UE should send the scheduling request; and the ID of the SchedulingRequestConfig that uses this scheduling request resource. [ 0084] In one embodiment, when SR is allowed for UE to request UL resource during HO without RACH, at least one of the following may apply for UE to select the SR resource used for SR transmission. The EU uses a dedicated SR resource to send the SR. - The EU randomly selects from the available SR resources to send the SR. The EU selects the most recent SR resource from among the available SR resources to send the SR. Petition 870250121348, dated 12 / 30 / 2025, page 38 / 170 31 / 64 — When the request resource is for a CCCH (Common Control Channel) message, the UE selects the SR resource with the highest priority for sending the SR.

[0085] In one embodiment, a configuration for advance TA acquisition. The configuration includes at least one indication indicating that it is a configuration for advance TA acquisition, a RACH configuration for the UE to perform advance TA acquisition.

[0086] In an implementation, the indication of a configuration for early TA acquisition can be indicated by the presence of the configuration.

[0087] In one implementation, the early TA RACH configuration is a cell-specific configuration. In this configuration, the configured RACH resources are shared with the CBRA triggered for another purpose, for example, initial access. In another implementation, the early TA RACH configuration is a user-specific configuration, which contains resource configuration without contention. For the RACH configuration mentioned above, at least one time-domain, code-domain, or frequency-domain resource can be configured. In another implementation, the absence of RACH configuration may imply that the UE uses another configured RACH resource, for example, the common RA resource configured in the system information. For step 3: How to select the pre-allocated grant resource to transmit the PUSCH

[0088] In one mode, the UE can select the first available UL resource among the configured resources, which Petition 870250121348, dated 12 / 30 / 2025, p. 39 / 170 32 / 64 beams can be pre-allocated or dynamically scheduled. In one mode, the UE can additionally select the beam based on the RSRP threshold, as discussed previously. In another mode, the UE selects the beam with the RSRP above the RSRP threshold configured for HO without RACH.

[0089] In one mode, at least one of the following options can be used to determine the resource for transmitting the PUSCH: Option 1: If an initial scheduling time and a scheduling interval are configured, the UE selects the resource corresponding to the Nth concession that occurred in the timing for the PUSCH transmission, for which Timing = [N * (scheduling interval) + (initial scheduling time)] module UNIT. The UNIT depends on the granularity used to configure the parameters. In one mode, the UNIT is equal to the number of granularities contained in a radio frame. In one mode, if the granularity is subframe, the UNIT is equal to the number of subframes per radio frame (e.g., 10). In one mode, if the granularity is slot, the UNIT depends on the SCS. Option 2: If the UL resource consists of subsets or complete sets of grant resources configured by the network, the UE determines the first available UL resource using the first available CG resource based on the CG configuration (e.g., periodicity and SCS). Option 3: The UE monitors the PDCCH using the C-RNTI and uses the scheduled UL resource from the received PDCCH as a resource to transmit the PUSCH.

[0090] In one modality, a combination of the above options Petition 870250121348, dated 12 / 30 / 2025, page 40 / 170 33 / 64 can be considered. In one mode, Option 1 and Option 3 can be used together. In one mode, the UE can select the resource from pre-allocated grants while monitoring the PDCCH and uses the first available UL resource for transmission. In one mode, Option 2 and Option 3 can be used together. In one mode, the UE can select resources from candidate CG grant resources while monitoring the PDCCH and uses the first available UL resource for transmission. Determining the HP used for the selected UL feature

[0091] In a modality, at least one of the options below can be used to determine the HPs used for the selected UL feature. - A standard HP is used for transmitting the HPs (e.g., HP zero). The HP ID is explicitly configured for the UE. A range of HP IDs is provided. In one mode, the UE selects the range from the lowest to the highest number. In one mode, the first available HPs can be used. - If a scheduling interval and a start time are considered, the UE can determine the HP based on the information provided, along with the number of HP configured. An example of an equation is as follows:

[0092] HARQ Process ID = [floor(CURRENT_symbol / (scheduling interval))] modulo (the number of HP configured), where CURRENT_symbol = (SFN χ numberOfSlotsPerFrame χ numberOfSymbolsPerSlot + slot number in the frame χ numberOfSymbolsPerSlot + symbol number in the slot), and Petition 870250121348, dated 12 / 30 / 2025, page 41 / 170 34 / 64 numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot.

[0093] In one embodiment, if the pre-allocated UL grant resource is a subset or complete set of configured grant resources, the equation used for HP calculation for the corresponding configured grant type can be used for HP calculation for the pre-allocated UL grant resource. Determining the type of HP and executing LCP (mapping PUSCH to HPs)

[0094] In one embodiment, HP type information (if configured) can be used in the Logical Channel Prioritization (LCP) procedure. In one embodiment, at least one of the methods below can be used to determine the HP type and use it in the LCP.

[0095] In one embodiment, the HP type can be determined based on the information received in the HO configuration without RACH, which indicates the HARQ type associated with the HP, for example, type A or type B.

[0096] In one embodiment, a bitmap can be used to indicate the HARQ type for each HP associated with the pre-allocated resources.

[0097] In one embodiment, a common HP type is configured for all HPs associated with the grant resource. For example, when the UE selects the pre-allocated resource for the PUSCH transmission and determines the HP to be used for the PUSCH transmission, the UE can use the HP type configured for the pre-allocated grant resource, regardless of the Petition 870250121348, dated 12 / 30 / 2025, page 42 / 170 35 / 64 previously configured (if any). In one mode, the UE can use the common HP type when performing LCP.

[0098] In one mode, a prompt is used to disable the HP type associated with the selected HP (if any). In one mode, when the prompt tells the UE to disable the HP type, the UE cannot use the HP type (if configured) when performing the LCP. That is, the UE cannot apply the LCP defined for the HARQ type.

[0099] In one mode, a predefined rule can be used without configuration. In one mode, the UE cannot use the HP type in the LCP when the PUSCH transmission uses the pre-allocated resource.

[00100] In one embodiment, a standard HP type is used for the HP when the PUSCH transmission utilizes pre-allocated resources (e.g., type A or type B). Power control for PUSCH transmission using pre-allocated grant resource.

[00101] In one embodiment, at least one of the closed-loop and open-loop power controls may be considered for the PUSCH transmission power control for pre-allocated concession.

[00102] For closed-loop power control, at least one of the following may be considered.

[00103] In one modality, power control follows the rules used for the scheduled PUSCH by the UL grant. In one modality, as there may be two types of RACH (e.g., 2-stage RACH or 4-stage RACH), the NW may indicate which type of RACH the power control refers to. In one modality, the UE may decide, based on the procedure, which parameters of Petition 870250121348, dated 12 / 30 / 2025, page 43 / 170 36 / 64 power can be used for a pre-allocated UL feature to transmit the PUSH.

[00104] In one mode, power control follows the rules used for scheduled PUSCH by the configured concession.

[00105] In one mode, power control follows the rules used for the scheduled PUSCH by CG-SDT.

[00106] In one embodiment, if an EU transmits a PUSCH in the UL Active BWP b of the service cell f using the parameter set configuration with index jeo power control setting of PUSCH with index l, the UE determines the transmission power of PUSCH PUSCcb,b,f((,hJ>QdiP) on the occasion of transmission of PUSCH i as PUSCH, b, fc (i, j, Qa, l) = min ,Po_puschb,fc (j) + lOlogio (2μ· M^f (i)) +ab, f, c (j) · PLb, f, c (q) + Δb, ^ (i) + f, f,c(i, l) [dBm] where, - ^CMAXl / lC(i) is the maximum output power configured by UE for the carrier f of the service cell c during PUSCH i transmission. - PqPUSCH,b, / ,c(J) is a parameter composed of the sum of a component / 'o_NOMINAL,PUSCH / ,C(j') and a component PO_UE_PUSCH,b / ,C 09where jE {0,1,..., / -1}. - -P^b^ÃQd) is an estimate of downlink path loss in dB calculated by the UE using the reference signal index (RS) dd for the active DL BWP of the service cell f carrier c. - '^-(' is the bandwidth of the PUSCH resource allocation expressed as the number of resource blocks for the Petition 870250121348, dated 12 / 30 / 2025, page 44 / 170 37 / 64 occasion of PUSCH transmission i in the active UL BWP b of the service cell carrier f ce is μ an SCS configuration - ^ / i) = 10logla((2BP“«· - 1) · βΟ^) for Ks= 1.25 and Δτρ,& / ,ε(ί) = 0 for Ks= 0 where Ks is provided by deltaMCS for each UL BWP b of each carrier f service cell c. - fb,f,c(i'O = fopcii-io'O+lm=o-1ÔpuSCH,b,f,c(^^ is the power control setting state of PUSCH l for the active UL BWP b of the carrier f of the service cell ce on the occasion of PUSCH i transmission if UE is not supplied tpc-Accumulation, or fb,f,c(i' l) = ^pusch,b,f,c(i, l) is the power control setting state of PUSCH for the active UL BWP b of the carrier f of the service cell ce on the occasion of PUSCH i transmission if UE is supplied tpcAccumulation.

[00107] The min function, as shown in the equation above, means that the EU chooses the smallest among all candidates. - If a UE uses the pre-allocated UL grant and the Alpha value is not provided: If the power control of the pre-allocated UL grant follows similar power control rules to scheduled PUSCH by random access response UL grant: ; _ AD rrp — η Ω PO NOMINAL,PUSCH, f,c(0)=PO PRE+ Δ J =0, ^O-UE-Puscmb^cl0) =0,e - ,- , where POPRE is provided by the initial configured target power and Δ is provided by a delta power configuration parameter, or Δ=0dB if the delta power configuration is not provided, for the carrier f of the service cell c. - If a UE uses the pre-allocated UL grant configured by ConfiguredGrantConfig: Petition 870250121348, dated 12 / 30 / 2025, page 45 / 170 38 / 64 j = 1, Pq NOMiNAL,pusCH,f,c(1) is provided by the nominal power value. If this nominal power value is not provided, the UE can assume Po_NOMINAL,PUSCH,f,c(1)= PO_NOMINAL,PUSCH / ,C(0) .E, POUE PUSch,vX1) θ provided by p0 obtained from the value P0 configured for pre-allocated grant. - If a UE uses the pre-allocated UL grant and receives the Alpha value: - For abfc(j) - For j = 0, - if / O··0'·-···—·f, Χθ) YprA and Alpha for pre-allocated grant are provided, ^b,y,c(0) is the value of the alpha value configured for pre-allocated grant - otherwise, ^b, / ,c(0) = 1 - For j = 1, ab, y, c(1) is provided by alpha obtained from the alpha value configured for pre-allocated grant. For advance TA purchase

[00108] A typical use case for early TA acquisition would be when configuring HO without RACH along with CHO. To ensure that the candidate CHO cells to be selected for HO without RACH can have a valid TA value. The NW can pass an early RACH command to the UE requesting the UE to acquire TA via a RACH procedure. And at least one of the options below can be considered: • In an implementation, the RACH command may be an L1 signal (e.g., DCI), which may include at least one of the following pieces of information: • Candidate Cell Group ID: To identify the group Petition 870250121348, dated 12 / 30 / 2025, page 46 / 170 39 / 64 of candidate cells to which a cell whose TA value is acquired belongs. • Candidate Cell ID: To identify the candidate cell whose TA is acquired. • SSB or CSI-RS ID: To indicate the SSB or CSI-RS to be selected for RACH feature selection when initiating early RACH. • Preamble ID: To indicate the Preamble to be selected when starting the initial RACH, if the value of this field is 0, the CBRA will be applied (i.e., the preamble and / or RO are selected by the MAC entity) • RO ID and / or RACH MASK: To indicate the RACH occasions to be selected when starting the initial RACH. • In another implementation, the anticipated RACH command could be an L2 signal (e.g., MAC CE), which could include at least one of the following pieces of information: • Candidate Cell Group ID: To identify the candidate cell group to which a cell whose TA value is acquired belongs. • Candidate Cell ID: To identify the candidate cell whose TA is acquired. • SSB or CSI-RS ID: To indicate the SSB or CSI-RS to be selected for RACH feature selection when initiating early RACH. • Preamble ID: To indicate the Preamble to be selected when starting the initial RACH, if the value of this field is 0, CBRA will be applied (i.e., the preamble selection is done by MAC entity) • RO ID and / or PRACH MASK: To indicate the occasions Petition 870250121348, dated 12 / 30 / 2025, page 47 / 170 40 / 64 of RACH to be selected when starting the initial RACH. • A logical channel index (e.g., LCID or eLCID) can be used to identify the MAC CE used to trigger the initial RACH to acquire TA. • After receiving the early RACH command, the UE can apply the initial RACH RRC configuration according to the received early RACH command. • The UE initiates the RACH procedure according to the applied RACH RRC configuration and the received anticipated RACH command.

[00109] To determine the type of RACH initiated, the UE may consider the implementation below. In an implementation, the type of RACH may include the following: 1: CFRA (Contentionless RACH): the PRACH resources used for RACH are deliberately configured for EU. 2: CBRA (Contention based on RACH): The PRACH resources used for RACH are selected by the UE MAC entity. In one implementation, if CBRA is initiated for the initial RACH, MSG.3 and MSG.4 will no longer be needed; in other words, the UE can consider the initial CBRA-based RACH to have been successfully terminated upon successfully receiving and decoding the RAR (i.e., MSG 2).

[00110] To determine the initial RACH type, at least one of the following mechanisms can be applied: • 1: If the PRACH resources (i.e., Preamble ID and / or PRACH MASK) and SSB ID / CSI-RS ID are not present, or the PRACH resources are present as 0b000000 in the anticipated PRACH command, CBRA is initiated. Otherwise, CFRA is initiated. Petition 870250121348, dated 12 / 30 / 2025, page 48 / 170 41 / 64 • 2: If the PRACH resources indicated by the advance RACH command are from dedicated UE RACH resources, CFRA is initiated. If the PRACH resources indicated by the advance RACH command are from cell-specific RACH resources, CBRA is initiated. • 3: The RACH type for the initial RACH may be in an information element configured in the RRC configuration associated with the candidate cell.

[00111] After performing the RACH for the candidate cells, the UE can notify the service cell that it has completed the acquisition of TA through the RACH procedure. And at least one of the implementations below can be considered: • In one implementation, the UE can trigger and send a SR to the service cell as soon as the UE returns to the service cell. • In one implementation, the UE can send an SRS in the service cell. • If RAR is present in an implementation, the UE can generate and send a UL MAC CE to the service cell to report the return switching. In an implementation, an SR can be triggered when there is no available PUSCH that can accommodate the triggered UL MAC CE. • If the RAR is not present, the timing occurs when the sDU receives the F1 message containing the TA information associated with the UE and the target cell. • The service cell can configure an EarlyRACHControlTimer for the UE to initiate the initial RACH procedure in the candidate cell. The timer behavior can be as follows: Petition 870250121348, dated 12 / 30 / 2025, page 49 / 170 42 / 64 • Start / Restart: may occur after receiving the advance RACH command. • Stopping: This can occur after receiving the RAR. • Expire: This can interrupt the ongoing initial RACH, if any, and switch back to the service cell immediately. If the service cell and the candidate cell are within the same DUs: • Assuming the RAR is present in the candidate cell, the RAR may include the granting of UL from the service cell. The UE may perform the UL transmission in the service cell to notify it of the return.

[00112] The UE can also share TA information acquired from candidate cells so that the understanding or TA information between the UE and the service cell is the same. And at least one of the methods below can be considered:

[00113] To introduce a UL MAC CE (e.g., UL TA synchronization MAC CE) to indicate the TA value of the candidate cell that was successfully obtained. To keep the TAT aligned between UE and NW, there is at least one of the following mechanisms for UL timing advance synchronization MAC CE: • TA synchronization is triggered and pending successful reception and decoding of the RAR in the candidate cell. • The MAC entity generates the synchronization MAC CE. UL TA is activated when PUSCH is available in the service cell that can accommodate the UL TA synchronization MAC CE; in one implementation, the service cell might be SpCell, in another implementation, the service cell might be SCell or SpCell. Petition 870250121348, dated 12 / 30 / 2025, page 50 / 170 43 / 64 • If no PUSCH resources are available to accommodate the UL TA synchronization MAC CE, an SR must be triggered and pending. • The TAT (i.e., timeAlignmentTimer) can be reset / started when the UL TA synchronization MAC CE is sent to NW.

[00114] For the UL timing advance synchronization MAC CE, it may contain at least one of the following fields: • TA Value: To indicate the TA value of the candidate cell and / or TAG for the service cell. • Candidate cell information: • TAG Information: • Left TAT length: To indicate the left TAT length of the TA value, the left TAT length is calculated based on the timing of the MAC CE timing advance synchronization transmission of the UL.

[00115] In some instances, it is optional for the UE to support early TA acquisition, and a capability bit can be used to indicate whether the UE supports this feature. A signaling procedure similar to that discussed in the capability signaling section below can be used to report the capability to the NW. In another instance, it is conditionally mandatory for the UE to support this feature, for example, if the UE supports no RACH along with CHO, it is mandatory for the UE to support early TA acquisition. For stage 1: Capacity signaling

[00116] Example 1: In one embodiment, HO support without RACH may be an optional feature for UE. In one embodiment, Petition 870250121348, dated 12 / 30 / 2025, page 51 / 170 44 / 64 this feature can be optional without signaling. In one mode, if the UE does not support this feature, it can ignore the received configuration for HO without RACH.

[00117] Example 2: In one mode, HO support without RACH can be an optional feature for the UE. In one mode, a capability is used to indicate whether the UE supports this feature. In one mode, if the UE does not support this feature, the NW may not transmit the HO configuration without RACH to the UE.

[00118] In one embodiment, the capacity bit can be transferred in the UE capacity signaling, as shown in FIG. 2.

[00119] FIG. 2 shows an example of querying UE capacity information. NW can send an initial message to query UE capacity, and UE can send UE capacity information to inform NW of its capacity. In one embodiment, NW can, based on the capacity information received, decide whether to transmit the HO configuration without RACH to UE. In one embodiment, NW can transfer the UE capacity information received between different NW nodes. In one embodiment, if UE does not support HO without RACH, UE can ignore the HO configuration without RACH.

[00120] Example 3: In a modality, HO support without RACH can be conditional / optional for the UE. Thus, HO support without RACH can depend on some pre-configured conditions. In a modality, the UE supports HO without RACH if the UE supports HO. In a modality, the UE supports HO without RACH if the UE supports NTN.

[00121] Example 4: In one mode, UE mandatorily supports HO without RACH. Petition 870250121348, dated 12 / 30 / 2025, page 52 / 170 45 / 64

[00122] In some embodiments of this disclosure, methods are discussed for configuring the pre-allocated resource for RACH without RACH in NR, which includes associating the UL resource with the beam and selecting the UL resource as part of the CG configuration.

[00123] In some embodiments of this disclosure, methods for performing PUSCH transmission power control using the pre-allocated resource are discussed.

[00124] In some embodiments of this disclosure, methods for determining the HP ID and HP type associated with PUSCH transmission using the pre-allocated resource are discussed.

[00125] In some embodiments of this disclosure, methods for performing capacity signaling for HO without RACH on NTN are discussed.

[00126] With the above settings, the transfer procedure and communication reliability can be improved, and therefore the performance of the desktop network (NW).

[00127] Another improvement that can be considered to reduce signaling overhead and improve system mobility performance is to allow the UE to reuse the same Physical Cell Identity (PCI) when service link and / or feed link switching is caused by satellite movement. This feature is also referred to as unchanged PCI in this application.

[00128] A typical use case for PCI-free service link switching is for near-terrestrial fixed cells, where cell coverage relative to a geographic area remains unchanged for a given period of time. Petition 870250121348, dated 12 / 30 / 2025, page 53 / 170 46 / 64 time. For UEs within this area, since the radio seen by the UE is similar after service link switching, it is possible to reuse the same PCI with or without the L3 mobility procedure (e.g., HO). If the L3 mobility procedure is not applied, the signaling overhead used for the L3 mobility procedure can be reduced for UEs that support this feature. To support unchanged PCI after service link and / or feed link switching due to satellite movement, the UE needs to know when to obtain DL synchronization with the new satellite and recover UL synchronization if necessary, where the UE needs to be informed about the timing of such actions. At least one of the options below can be considered for this purpose:

[00129] Opt1: Explicit indication to enable unchanged PCI after satellite switching.

[00130] Opt2: A time indication to indicate the satellite switching time.

[00131] Option 3: Relative time information to help calculate satellite switching time.

[00132] For option 1, in one example, the explicit indication is used in conjunction with the legacy t-service field, where tservice indicates the time at which the current service cell will cease providing service to the current area. Upon receiving the explicit indication that unchanged PCI is allowed, the UE will begin performing the necessary actions at the time indicated by t-service.

[00133] The necessary actions include at least one of the following: Petition 870250121348, dated 12 / 30 / 2025, page 54 / 170 47 / 64 reacquire the necessary system information (e.g., MIB, SIB1, SIB19, etc.) from the new satellite; Monitor the SSB of the new satellite to obtain downlink synchronization; To achieve uplink synchronization, for example, by initiating RACH; Consider T430 as expired; and / or consider timeAlignmentTimer as expired.

[00134] Explicit indication may be provided to the UE by at least one of the following methods: broadcast signaling, system information, CE MAC, RRC messages, paging message, NAS message or groupcast signaling.

[00135] For option 1, another example of the use of explicit indication is to indicate when the UE should perform the necessary action, as discussed above. For example, the UE begins to reacquire system information, performs DL / UL synchronization with the new satellite at the time (e.g., slot, symbol) when the indication is received. Explicit indication can be provided to the UE by at least one of the following methods: broadcast signaling, system information, CE MAC, RRC messages, paging message, NAS message, or groupcast signaling.

[00136] For option 2, an explicit indication may be provided to indicate the timing when the switching will occur. In some examples, the UE will perform at least one of the necessary actions discussed in option 1 above at the timing indicated by the timing indication discussed here. In some examples, the UE will perform at least one of the necessary actions discussed in option 1 above, at most or before the timing indicated by the timing indication discussed here. The indication of Petition 870250121348, dated 12 / 30 / 2025, page 55 / 170 48 / 64 time can be delivered to the UE based on at least one of the methods discussed here: broadcast signaling, system information, MAC CE, RRC messages, paging message, NAS message, or groupcast signaling.

[00137] In one embodiment, the t-Service-PCI-Unchanged field in SIB19 can indicate time information about when a cell provided by the NTN near-terrestrial fixed system will cease serving the area it is currently covering for unchanged PCI deployment. The field indicates a time in multiples of 10 ms after 00:00:00 of the Gregorian calendar date of January 1, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact downtime is between the time indicated by the value of this field minus 1 and the time indicated by the value of this field. For option 3, a deltatime of relative time information is provided. In one example, the relative time indicates the time difference between the expected time for the UE to perform the necessary actions, as discussed in the examples above, and the time indicated by t-service.For example, the UE determines the time to apply the necessary action by subtracting the relative time from the time indicated by the t-service; or the UE determines the time to apply the necessary action by adding the relative time to the time indicated by the t-service. In some examples, the UE will perform at least one of the necessary actions discussed in option 1 above, at most or before the time calculated by the relative time indication discussed here. The relative time indication can be delivered to the UE based on at least one of the methods discussed here: broadcast signaling, system information, MAC CE, RRC messages, paging message, NAS message, or groupcast signaling. Petition 870250121348, dated 12 / 30 / 2025, page 56 / 170 49 / 64

[00138] In some instances, for the above-mentioned examples of option 1, option 2, and option 3, one or more offset values ​​may be introduced to allow processing time on the UE side. For example, when the UE decides on a first time T and if the UE is configured with one or more offsets (offset 1, offset 2, etc.), then the UE begins to reacquire system information, performing DL / UL synchronization with the new satellite at a second time T1, considering the received offset. An example could be T1 = T + offset1 + offset2 + ... In some instances, the offset may be K-offset. The first time T may be decided according to the examples discussed above for options 1-3, for example, indicated by service t, by the receipt time of the explicit indication, indicated by the time indication discussed in option 2, or calculated based on the relative time information discussed in option 3.

[00139] During switching, as there may be a small interruption, the UE is not expected to transmit any uplink data before regaining synchronization with the target satellite. Furthermore, the UE needs to reacquire the new SIB19 from the target to obtain the necessary assistance information to perform pre-compensation. The need to perform RACH for TA fine-tuning may be relevant to the arrival of uplink data for transmission. That is, the UE triggers RACH when UL data arrives. For DL ​​data arrival, NW may use the PDCCH order to trigger the UE to perform RACH, which is a legacy behavior.

[00140] According to current specifications, the UE will stop transmitting UL and release HARQ, reacquiring Petition 870250121348, dated 12 / 30 / 2025, page 57 / 170 50 / 64 the SIB19 when the T430 expires. Furthermore, the UE may reuse the existing trigger condition to trigger the RACH, for example, when the TAT time expires but there is DL / UL data arriving. Therefore, the simplest method to capture the behaviors described in the observation above in the specifications is to assume that the T430 and the TAT timer expired at the time indicated by the NW or calculated by the UE. The detailed timing determination can use at least one of the examples discussed in options 1 to 3 above.

[00141] For the unchanged PCI feature, as discussed here, this has raised new requirements for UEs. In some instances, it is optional for the UE to support this feature; a capability bit can be introduced to indicate whether the UE supports this feature. This capability can be requested and reported to the NW via the capability query procedure, as discussed in HOs without RACH. Furthermore, different NW nodes can alter the UE capability information received via the NW interface (e.g., Xn interface). In another instance, this feature can be optionally supported without capability signaling, where if it receives such a setting, the UE simply ignores the setting. Or, in some instances, it is mandatory for the UE to support this feature. Or, in another instance, it is conditionally supported by the UE, e.g., if the UE supports NTN, the UE will support unchanged PCI, as discussed here.

[00142] Mobility management in wireless communication systems can be aided by measurements of neighboring cells, based on measurement results received from the UE. NW can adjust the criteria for cell (re)selection (e.g., adjust cell and / or frequency priorities). Petition 870250121348, dated 12 / 30 / 2025, page 58 / 170 51 / 64 and / or determine the target cells to be transferred and / or adjust the candidate target cells. However, many measurements of neighboring cells will lead to extra power consumption. A typical use case is when the UE is camped on NTN and configured to measure on TN frequencies or vice versa. Due to satellite movement, TN coverage relative to NTN coverage may appear and disappear alternately. Further improvements can be considered to relax neighboring cell measurements on TN cells when no TN coverage is available, thus reducing power consumption. To assist this behavior, information for the UE to derive TN coverage can be provided by the NW. And at least the option below can be considered to provide the UE with TN coverage information: • TN coverage can be represented by an elliptical area. This can be represented by at least one of the options below: Option 1: TN coverage information can include at least one ellipse center coordinate, a first length piece of information, a second length piece of information, and a slope piece of information (e.g., an angle piece of information). For example, the first length is half the width (or length) (a) of the major axis of an ellipse centered at the origin; the second length information is half the width (or length) (b) of the minor axis of an ellipse centered at the origin; the origin is a coordinate of the center of the ellipse associated with a geographic location. Based on these three pieces of information, an area with the shape of an ellipse can be determined. Petition 870250121348, dated 12 / 30 / 2025, page 59 / 170 52 / 64 in a unique way. An example equation is as follows, assuming the ellipse is centered at the origin:

[00143] Tilt information (e.g., angle information) can be provided to indicate the tilt of the ellipse relative to a geographic area; in some examples, tilt information may be called direction angle. For example, a reference direction can be defined, for instance, it can be indicated as south, east, north, or west. Then, angle information can be the angle between the ellipse's major axis (it can be the left or right half of the ellipse's major axis) and the reference direction. Or, in another example, angle information can be the angle between the ellipse's secondary axis (it can be the left or right half of the ellipse's major axis) and the reference direction. Angles can have a range of values ​​from zero to 360 degrees, which can be counted from 0 to 360 in a clockwise or counterclockwise method.In some examples, the angle may be present in steps of x degrees, where x can be 1, 2, 5, or another integer divisible by 360. In another example, angles may have a range of values ​​from zero to 180 degrees, which can be counted from 0 to 180 degrees clockwise or counterclockwise. In some examples, the angle may be present in steps of x degrees, where x can be 1, 2, 5, or another integer divisible by 180.

[00144] Below is an example of how this angle information is presented and used (see FIG. 7). In this example, the reference direction is north, and the angle information indicates the angle between the principal axis of the ellipse and the direction of Petition 870250121348, dated 12 / 30 / 2025, pp. 60 / 170 53 / 64 reference, which starts from 0 to 360 degrees in a time-directed method. For the two ellipses provided, the major axis is represented by ai(i=1,2), the minor axis is represented by bi(i=1,2), and the angle between the major axis of the ellipse and the reference direction is θί(ί=1,2), i is the index of each ellipse. If NW indicates that the angle information is equal to Θ1, then the coverage of TN is the geographic area presented by Ellipse1. Option 2: the ellipse can be represented by 5 points (for example, a, b, h, k, center of the ellipse), assuming the center of the ellipse as the origin, where the mathematical expression of the ellipse would be as below, assuming the ellipse centered at (h, k): (xh)2(yk)2=1a2b2

[00145] For option 2, one example is to provide the UE with the actual coordinates of the 5 points (including the center of the ellipse), another example is to provide the UE with the coordinates of the center of the ellipse and the relative distance of the remaining points to the center of the ellipse.

[00146] In some examples, the TN coverage (e.g., shown by an ellipse) may include one or more TN cells, which may even be the NW implementation.

[00147] In some examples, the TN coverage information provided is associated with frequency information. For example, for each TN coverage area, one or more frequency information items displayed by a frequency list may be provided, indicating that the frequency can be measured within the provided TN coverage area. In another example, TN coverage is provided by frequency, for example, a frequency is associated with a TN area. Or, in yet another example, the information Petition 870250121348, dated 12 / 30 / 2025, p. 61 / 170 54 / 64 frequencies associated with TN coverage can be a bitmap, where the bitmap indicates whether a list of frequencies provided in the system information (e.g., SIB3, SIB4, SIB19, or other SIBx) and / or the measurement objective is associated with TN coverage or not. With each bit, a value of zero means that the frequency is not considered associated with TN coverage, while a value of zero means that the frequency is associated with TN coverage, or vice versa. From the most significant bit (MSB) to the least significant bit (LSB), the first bit of the bitmap corresponds to the first entry in the frequency list, the second bit corresponds to the second entry in the frequency list, and so on.

[00148] In some instances, TN coverage and / or associated frequency information may be provided to the UE by at least one of the following methods: Broadcast in system information (e.g., MIB, SIB1, SIB19, other SIBs specified in the 3GPP standards, or a new SIB), NAS message, dedicated RRC signaling, common signaling for a group of UEs (e.g., groupcast, multicast).

[00149] In some examples, if provided with TN coverage, if the UE camps in the NTN cell, the UE can rely on the provided TN coverage and its own location to decide whether TN coverage is available, and the UE can decide not to perform measurements of neighboring cells at TN frequencies when there is no TN coverage.

[00150] Or in another example, if the UE determines that it is approaching an area that has TN coverage, the UE may decide to prioritize measurement at TN frequencies. In one example, a distance threshold may be introduced for the reselection of Petition 870250121348, dated 12 / 30 / 2025, p. 62 / 170 55 / 64 NTN-TN cell. If the distance between the UE and the TN coverage center (for example, it could be an ellipse or a circle or other geometric shapes) is less than the threshold, the UE prioritizes measurement at the TN frequency. Or in another example, two distance thresholds can be introduced to assist in measuring neighboring cells. For example, if the UE decides that the distance between its location and the NTN cell center is greater than a first distance threshold, and the distance between its location and the TN coverage center is less than a second distance threshold, the UE prioritizes measurement at the TN frequencies. Other measurement rules can be considered separately or in combination with the rules discussed here.

[00151] FIG. 3 refers to a schematic diagram of a wireless terminal 30, according to an embodiment of the present disclosure. The wireless terminal 30 may be a user equipment (UE), a mobile phone, a laptop, a tablet, an e-reader, or a portable computer system and is not limited to these. The wireless terminal 30 may include a processor 300, such as a microprocessor or Application-Specific Integrated Circuit (ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device that stores a program code 312, which is accessed and executed by the processor 300. Embodiments of the storage unit 312 include, but are not limited to, a subscriber identity module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage device. Petition 870250121348, dated 12 / 30 / 2025, page 63 / 170 56 / 64 communication unit 320 can be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of processor 300. In one embodiment, communication unit 320 transmits and receives signals through at least one antenna 322 shown in FIG. 3.

[00152] In one embodiment, storage unit 310 and program code 312 may be omitted and processor 300 may include a storage unit with stored program code.

[00153] Processor 300 can implement any of the steps in modes exemplified in wireless terminal 30, for example, executing program code 312.

[00154] The 320 communication unit can be a transceiver. The 320 communication unit can alternatively or additionally combine a transmit unit and a receive unit configured to transmit and receive signals to and from a wireless network node (e.g., a base station), respectively.

[00155] FIG. 4 refers to a schematic diagram of a wireless network node 40 according to an embodiment of the present disclosure. The wireless network node 40 may be a satellite, a base station (BS), a network entity, a Mobility Management Entity (MME), a Service Gateway (S-GW), a Packet Data Network Gateway (PDN) (P-GW), a radio access network (RAN) node, a next-generation RAN node (NG-RAN), a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a Radio Network Controller (RNC), and not Petition 870250121348, dated 12 / 30 / 2025, p. 64 / 170 57 / 64 is limited to this document. Furthermore, the wireless network node 40 may comprise (perform) at least one network function, such as an access and mobility management (AMF) function, a session management function (SMF), a user location function (UPF), a policy control function (PCF), an enforcement function (AF), etc. The wireless network node 40 may include a processor 400, such as a microprocessor or ASIC, a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device that stores program code 412, which is accessed and executed by the processor 400. Examples of the storage unit 412 include, but are not limited to, a SIM, ROM, flash memory, RAM, hard disk, and optical data storage device.The communication unit 420 can be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of processor 400. In one example, the communication unit 420 transmits and receives signals through at least one antenna 422 shown in FIG. 4.

[00156] In one embodiment, storage unit 410 and program code 412 may be omitted. Processor 400 may include a storage unit with stored program code.

[00157] Processor 400 can implement any steps described in exemplified modes in wireless network node 40, for example, by executing program code 412.

[00158] The 420 communication unit can be a transceiver. The 420 communication unit can alternatively or additionally combine a transmission unit and a Petition 870250121348, dated 12 / 30 / 2025, page 65 / 170 58 / 64 receiving unit configured to transmit and receive signals to and from a wireless terminal (e.g., user equipment or another wireless network node).

[00159] A wireless communication method is also provided according to an embodiment of the present disclosure. In one embodiment, the wireless communication method can be implemented using a wireless communication terminal (e.g., a UE). In one embodiment, the wireless communication terminal can be implemented using the wireless communication terminal 30 described above, but is not limited to that.

[00160] Referring to FIG. 5, in one embodiment, the wireless communication method includes: receiving, by a wireless communication terminal from a network node, configuration information for a transfer procedure without a Random Access Channel, RACH procedure; initiating, by the wireless communication terminal, the transfer procedure without a RACH procedure in accordance with the configuration information; and transmitting, by the wireless communication terminal to a wireless communication node, uplink, UL, data for the transfer procedure without a RACH procedure in accordance with the configuration information.

[00161] In some modes, the configuration information may be the configuration for HO without RACH described above.

[00162] In some modes, UL data may be PUSCH using the NW scheduled UL feature described above.

[00163] In some embodiments, UL data is transmitted in a UL resource according to the information of Petition 870250121348, dated 12 / 30 / 2025, pp. 66 / 170 59 / 64 configuration. In some modes, the UL resource comprises at least one of a pre-configured / pre-allocated UL resource described above or a dynamically scheduled resource described above.

[00164] Details in this regard can be verified with reference to the paragraphs above and will not be repeated here.

[00165] Another wireless communication method is also provided according to an embodiment of the present disclosure. In one embodiment, the wireless communication method can be implemented using a wireless communication node (e.g., a network node). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described above, but is not limited to that.

[00166] Referring to FIG. 6, in one embodiment, the wireless communication method includes transmitting, by a network node to a wireless communication terminal, configuration information for a transfer procedure without a Random Access Channel, RACH, procedure, to enable the wireless communication terminal to initiate the transfer procedure without a RACH procedure, according to the configuration information, and transmitting uplink, UL, data for the transfer procedure without a RACH procedure, according to the configuration information.

[00167] Details in this regard can be verified with reference to the paragraphs above and will not be repeated here.

[00168] Although several embodiments of the present disclosure have been described above, it should be understood that they have been presented only by way of example, and not by way of limitation. Similarly, the various diagrams may represent Petition 870250121348, dated 12 / 30 / 2025, page 67 / 170 60 / 64 an example of an architecture or configuration, which are provided to enable those skilled in the art to understand exemplary features and functions of the present disclosure. Those skilled in the art would understand, however, that the present disclosure is not restricted to the example architectures or configurations illustrated, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as would be understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[00169] It is also understood that any reference to an element in this document using a designation such as first, second, and so forth generally does not limit the quantity or order of those elements. Instead, these designations may be used here as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to the first and second elements does not mean that only two elements may be employed or that the first element must precede the second element in any way.

[00170] Furthermore, a person skilled in the art would understand that information and signals can be represented using any one of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, for instance, which can be referenced in the description above, can be represented by voltages, currents, waves Petition 870250121348, dated 12 / 30 / 2025, pp. 68 / 170 61 / 64 electromagnetic, magnetic fields or particles, optical fields or particles, or any combination thereof.

[00171] A person skilled in the art would further appreciate that any of the various illustrative logic blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., an implementation, an analog implementation or a combination of the two), firmware, various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as software or software unit) or any combination of these techniques.

[00172] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of functionality. Whether this functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the specific application and design constraints imposed on the overall system. Skilled workers may implement the described functionality in various ways for each specific application, but such implementation decisions do not cause a departure from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc., may be configured to perform one or more of the functions described herein.The term configured for or set up for, as used herein in relation to a specified operation or function, refers to a processor, device, component, circuit, structure, machine, unit, etc. that is. Petition 870250121348, dated 12 / 30 / 2025, pp. 69 / 170 62 / 64 physically constructed, programmed and / or prepared to perform the specified operation or function.

[00173] Furthermore, a person skilled in the art would understand that various logic blocks, units, devices, components, and illustrative circuits described herein may be implemented within or realized 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 additionally include antennas and / or transceivers for communicating with various components within the network or within the device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine.A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other configuration suitable for performing the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code in a computer-readable medium. Thus, the steps of a method or algorithm disclosed in this document can be implemented as software stored in a computer-readable medium.

[00174] Computer-readable media includes computer storage media and communication media, including Petition 870250121348, dated 12 / 30 / 2025, pp. 70 / 170 63 / 64 any means that can be activated to transfer a computer program or code from one location to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[00175] In this document, the term "unit," as used herein, refers to software, firmware, hardware, and any combination of these elements to perform the associated functions described herein. Furthermore, for purposes of discussion, the various units are described as discrete units; however, as would be apparent to one skilled in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of this disclosure.

[00176] In addition, memory or other storage, as well as communication components, may be employed in the embodiments of this disclosure. It will be appreciated that, for the sake of clarity, the above description describes embodiments of this disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, logical processing elements, or domains may be used without prejudice to this disclosure. For example, the functionality Petition 870250121348, dated 12 / 30 / 2025, page 71 / 170 The 64 / 64 functionality illustrated to be performed by separate logical processing elements, or controllers, can be performed by the same logical processing element or controller. Therefore, references to specific functional units are merely references to a suitable means of providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[00177] Several modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the scope of the claims. Thus, the disclosure is not intended to be limited to the implementations shown in this document, but should be given the broader scope consistent with the new features and principles disclosed herein, as set forth in the claims below. Petition 870250121348, dated 12 / 30 / 2025, page 72 / 170

Claims

1 / 16 CLAIMS 1. Wireless communication method, characterized in that it comprises: receiving, by a wireless communication terminal from a network node, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure; initiating, by the wireless communication terminal, the transfer procedure without a RACH procedure in accordance with the configuration information; and transmitting, by the wireless communication terminal to a wireless communication node, uplink (UL) data for the transfer procedure without a RACH procedure in accordance with the configuration information.

2. Wireless communication method according to claim 1, characterized in that the configuration information comprises at least one of: an indication that a RACH procedure has been skipped in the transfer procedure; Timing Advance, TA, information indicating a target TA to be applied to the wireless communication terminal; a UL resource grant configuration for a pre-allocated UL resource for the transmission of UL data; relevant power control information for the transmission of UL data; a configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure; or a Scheduling Request, SR, configuration. Petition 870250121348, 12 / 30 / 2025, p. 73 / 170 2 / 16 3. Wireless communication method according to claim 2, characterized in that the UL grant resource configuration comprises at least one of: a code domain resource configuration; a time domain resource configuration; a frequency domain resource configuration; a subcarrier spacing configuration, SCS; antenna port information; information indicating whether a transform pre-encoding is used; at least one time domain resource or frequency domain resource for transmitting Hybrid Automatic Repeat Request Confirmation, HARQ information; a channel status information request, CSI; a number of HARQ process numbers used for a Physical Uplink Shared Channel (PUSCH) transmission; information indicating whether a HARQ feedback is disabled; information for determining HARQ type information;Beam information associated with a pre-allocated UL resource; a validity period for a pre-allocated UL resource configuration for a transmission of UL data; or a priority index associated with a pre-allocated UL resource.

4. Wireless communication method according to claim 3, characterized in that the beam information comprises at least one of: Petition 870250121348, 12 / 30 / 2025, p. 74 / 170 3 / 16 a beam type; a beam index; a threshold for a beam selection for a PUSCH transmission; a mapping relationship between a PUSCH resource and a selected beam; a probe reference signal resource indicator, SRS, for a beam selection; a mapping pattern for an SRS resource; a transmission configuration state indication, TCI; bandwidth portion information, BWP, for a UL resource pre-allocated for a transmission of UL data; or UL carrier information for a UL resource pre-allocated for a transmission of UL data.

5. Wireless communication method, according to any one of claims 2 to 4, characterized in that the relevant power control information comprises at least one of: a target power level for a transmission of UL data; a delta power level used in a transmission power calculation; a type of RACH; or an alpha value for a transmission power calculation of a transmission of UL data.

6. Wireless communication method, according to any one of claims 2 to 5, characterized in that the configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure comprises a timer configuration, wherein the wireless communication terminal performs at least one of: in response to the timer's termination, initiate a RACH procedure on a target cell; in response to the timer's termination, release a pre-allocated UL resource; in response to the timer's termination, hold a pre-allocated UL resource; or upon initiating a RACH procedure, use a temporary cellular radio network identifier, C-RNTI, to monitor physical downlink control channels, PDCCHs.

7. Wireless communication method, according to any one of claims 2 to 6, characterized in that the SR configuration comprises at least one of: an indication that shows whether an SR can be initiated when no UL resource is available; or a dedicated SR configuration.

8. Wireless communication method according to claim 7, characterized in that the wireless communication terminal performs at least one of: using a dedicated SR resource to send an SR; randomly selecting from available SR resources to send an SR; selecting a more recent SR resource from available SR resources to send an SR; or selecting an SR with the highest priority when a request resource is for a Common Control Channel (CCCH) message.

9. Wireless communication method, according to any one of claims 1 to 8, characterized in that the wireless communication terminal performs at least one of: determining a UL resource among candidate UL resources that are pre-allocated or dynamically programmed to transmit UL data; or determining a beam to transmit UL data.

10. Wireless communication method according to claim 9, characterized in that the wireless communication terminal performs at least one of the following: selecting a beam that satisfies at least one of the following conditions as the beam to transmit UL data; the beam is associated with a Physical Broadcast Channel Block / Synchronization Signal, SSB, with received reference signal powers, RSRP, greater than or equal to a first configured threshold; or the beam is associated with a channel status information reference signal, CSI-RS, with an RSRP greater than or equal to a second configured threshold; selecting any available beam as the beam to transmit UL data in response to no beam associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with an RSRP greater than or equal to a second configured threshold;or perform a return to a transfer procedure with a RACH procedure in response to the absence of a beam. Petition 870250121348, dated 12 / 30 / 2025, page 77 / 170 6 / 16 associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with RSRP greater than or equal to a second configured threshold.

11. Wireless communication method according to claim 9 or 10, characterized in that the wireless communication terminal performs at least one of the following operations to determine the UL resource: selecting an nth UL resource from among the candidate UL resources in response to an initial scheduling time and a scheduling interval being configured; selecting a first available UL resource as the first available grant resource, CG, configured based on a CG configuration in response to the candidate UL resources being a subset or a complete set of CG resources; or monitoring a PDCCH using a C-RNTI and taking a UL resource scheduled by the PDCCH as the UL resource to transmit the UL data.

12. Wireless communication method, according to any one of claims 1 to 11, characterized in that the wireless communication terminal performs at least one of: using a standard HARQ process for a HARQ process for a transmission of UL data; being configured with a HARQ process identifier, and using the received HARQ process identifier for a HARQ process for a transmission of UL data; being provided with a HARQ process identifier range, and using a HARQ process identifier within the range for a HARQ process for a transmission of UL data; or determining a HARQ process for a transmission of UL data based on a scheduling interval, a start time, and a number of configured HARQ processes.

13. Wireless communication method, according to any one of claims 1 to 12, characterized in that the wireless communication terminal performs at least one of: performing a logical channel prioritization procedure according to a HARQ process type; receiving configuration information comprising a bitmap indicating a HARQ process type for each HARQ process associated with pre-allocated resources; receiving configuration information comprising a common HARQ process type for each HARQ process associated with pre-allocated resources; receiving configuration information comprising an indication used to disable a HARQ process type associated with a HARQ process; performing a logical channel prioritization procedure according to a predetermined rule; or performing a logical channel prioritization procedure according to a standard HARQ process type.

14. Wireless communication method, according to any one of claims 1 to 13, characterized in that the wireless communication terminal performs power control for the transmission of UL data according to an active UL BWP to transmit the UL data, a carrier to transmit the UL data, and a wireless communication terminal service cell. Petition 870250121348, dated 12 / 30 / 2025, page 79 / 170 8 / 16.

15. Wireless communication method, according to any one of claims 1 to 14, characterized in that the wireless communication terminal transmits a capability to support a transfer procedure with a RACH procedure being skipped.

16. Wireless communication method, characterized in that it comprises: transmitting, by a network node to a wireless communication terminal, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure, to enable the wireless communication terminal to initiate the transfer procedure without a RACH procedure, in accordance with the configuration information, and transmitting uplink (UL) data for the transfer procedure without a RACH procedure, in accordance with the configuration information.

17. Wireless communication method according to claim 16, characterized in that the configuration information comprises at least one of: an indication that a RACH procedure was skipped in the transfer procedure; Timing Advance, TA, information indicating a target TA to be applied to the wireless communication terminal; a UL resource grant configuration for a pre-allocated UL resource for the transmission of UL data; relevant power control information for the transmission of UL data; a configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure; or a Scheduling Request, SR, configuration.

18. Wireless communication method according to claim 17, characterized in that the UL grant resource configuration comprises at least one of: a code domain resource configuration; a time domain resource configuration; a frequency domain resource configuration; a subcarrier spacing configuration, SCS; antenna port information; information indicating whether a transform pre-encoding is used; at least one time domain resource or frequency domain resource for transmitting Hybrid Automatic Repeat Request Confirmation, HARQ, information; a channel status information request, CSI; a number of HARQ process numbers used for a Physical Uplink Shared Channel (PUSCH) transmission; information indicating whether a HARQ feedback is disabled; information for determining HARQ type information;Beam information associated with a pre-allocated UL resource; a validity period for a pre-allocated UL resource configuration for a transmission of UL data; or a priority index associated with a pre-allocated UL resource. Petition 870250121348, dated 12 / 30 / 2025, p. 81 / 170 10 / 16; 19. Wireless communication method according to claim 18, characterized in that the beam information comprises at least one of: a beam type; a beam index; a threshold for a beam selection for a PUSCH transmission; a mapping relationship between a PUSCH resource and a selected beam; a probe reference signal resource indicator, SRS, for a beam selection; a mapping pattern for an SRS resource; a transmission configuration state indication, TCI; bandwidth portion information, BWP, for a UL resource pre-allocated for a transmission of UL data; or UL carrier information for a UL resource pre-allocated for a transmission of UL data.

20. Wireless communication method, according to any one of claims 17 to 19, characterized in that the relevant power control information comprises at least one of: a target power level for a transmission of UL data; a delta power level used in a transmission power calculation; a type of RACH; or an alpha value for a transmission power calculation of a transmission of UL data.

21. Wireless communication method, according to any one of claims 17 to 20, characterized in that the configuration for the wireless communication terminal to perform a return to a transfer procedure with a RACH procedure comprises a timer configuration, wherein the wireless communication terminal performs at least one of: in response to the timer's termination, initiate a RACH procedure on a target cell; in response to the timer's termination, release a pre-allocated UL resource; in response to the timer's termination, maintain a pre-allocated UL resource; or upon initiating a RACH procedure, use a temporary cellular radio network identifier, C-RNTI, to monitor physical downlink control channels, PDCCHs.

22. Wireless communication method, according to any one of claims 17 to 21, characterized in that the SR configuration comprises at least one of: an indication that shows whether an SR can be initiated when no UL resource is available; or a dedicated SR configuration.

23. Wireless communication method according to claim 22, characterized in that the wireless communication terminal performs at least one of: using a dedicated SR resource to send an SR; randomly selecting from among the available SR resources to send an SR; selecting a more recent SR resource from among the available SR resources to send an SR; or selecting an SR with the highest priority when a request resource is for a common control channel (CCCH) message.

24. Wireless communication method, according to any one of claims 16 to 23, characterized in that the wireless communication terminal performs at least one of: determining a UL resource among candidate UL resources that are pre-allocated or dynamically programmed to transmit UL data; or determining a beam to transmit UL data.

25. Wireless communication method according to claim 24, characterized in that the wireless communication terminal performs at least one of the following: selecting a beam that satisfies at least one of the following conditions as the beam to transmit UL data; the beam is associated with a Physical Broadcast Channel Block / Synchronization Signal, SSB, with received reference signal powers, RSRP, greater than or equal to a first configured threshold; or the beam is associated with a channel status information reference signal, CSI-RS, with an RSRP greater than or equal to a second configured threshold; selecting any available beam as the beam to transmit UL data in response to no beam associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with an RSRP greater than or equal to a second threshold. Petition 870250121348, dated 12 / 30 / 2025, p.84 / 170 13 / 16 configured; or perform a return to a transfer procedure with a RACH procedure in response to the absence of a beam associated with an SSB with received reference signal powers, RSRP, greater than or equal to a first configured threshold or associated with a CSI-RS with RSRP greater than or equal to a second configured threshold.

26. Wireless communication method according to claim 24 or 25, characterized in that the wireless communication terminal performs at least one of the following operations to determine the UL resource: selecting an nth UL resource from among the candidate UL resources in response to an initial scheduling time and a scheduling interval being configured; selecting a first available UL resource as the first available grant resource, CG, configured based on a CG configuration in response to the candidate UL resources being a subset or a complete set of CG resources; or monitoring a PDCCH using a C-RNTI and taking a UL resource scheduled by the PDCCH as the UL resource to transmit the UL data.

27. Wireless communication method, according to any one of claims 16 to 26, characterized in that the wireless communication terminal performs at least one of: using a standard HARQ process for a HARQ process for a transmission of UL data; being configured with a HARQ process identifier, and using the received HARQ process identifier for a HARQ process for a transmission of UL data; being provided with a range of HARQ process identifiers, and using a HARQ process identifier within the range for a HARQ process for a transmission of UL data; or determining a HARQ process for a transmission of UL data based on a scheduling interval, a start time, and a number of configured HARQ processes.

28. Wireless communication method, according to any one of claims 16 to 27, characterized in that the wireless communication terminal performs at least one of: performing a logical channel prioritization procedure according to a HARQ process type; receiving configuration information comprising a bitmap indicating a HARQ process type for each HARQ process associated with pre-allocated resources; receiving configuration information comprising a common HARQ process type for each HARQ process associated with pre-allocated resources; receiving configuration information comprising an indication used to disable a HARQ process type associated with a HARQ process; performing a logical channel prioritization procedure according to a predetermined rule; or performing a logical channel prioritization procedure according to a standard HARQ process type.

29. Wireless communication method, according to any one of claims 16 to 28, characterized in that the wireless communication terminal performs power control Petition 870250121348, dated 12 / 30 / 2025, page 86 / 170 15 / 16 for a transmission of UL data according to an active UL BWP to transmit the UL data, a carrier to transmit the UL data, and a service cell of the wireless communication terminal.

30. Wireless communication method, according to any one of claims 16 to 29, characterized in that the wireless communication terminal transmits a capability to support a transfer procedure with a RACH procedure being skipped.

31. Wireless communication terminal, characterized in that it comprises: a communication unit; and a processor configured to: receive, through the communication unit from a network node, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure; initiate the transfer procedure without a RACH procedure, according to the configuration information; and transmit, through the communication unit to a wireless communication node, uplink (UL) data for the transfer procedure without a RACH procedure, according to the configuration information.

32. Wireless communication terminal according to claim 31, characterized in that the processor is additionally configured to perform the wireless communication method as defined in any one of claims 2 to 15.

33. Wireless communication node, characterized in that it comprises: Petition 870250121348, dated 12 / 30 / 2025, page 87 / 170 16 / 16 a communication unit; and a processor configured to: transmit, through the communication unit, to a wireless communication terminal, configuration information for a transfer procedure without a Random Access Channel (RACH) procedure, to enable the wireless communication terminal to initiate the transfer procedure without a RACH procedure, according to the configuration information, and transmit uplink (UL) data for the transfer procedure without a RACH procedure, according to the configuration information.

34. Wireless communication node, according to claim 33, characterized in that the processor is additionally configured to perform the wireless communication method as defined in any one of claims 17 to 30.

35. A computer-readable medium, characterized in that it comprises instructions stored therein, the instructions, when executed by a processor, causing the processor to implement a wireless communication method as defined in any one of claims 1 to 30. Petition 870250121348, dated 12 / 30 / 2025, pp. 88 / 170

Images