Methods, devices, and computer program products for wireless communication

Abstract

A method of wireless communication is disclosed. The method includes transmitting, by a wireless communication terminal, a random access (RA) report to a wireless communication node, the RA report including small data transmission (SDT) related information for random access channel (RACH) optimization.

Description

Technical Field

[0001] This document generally relates to wireless communication, and in particular to the 5th th Generation (5) th generation, 5G) communication or the 6th generation th generation (6) th generation, 6G) communications. Background Technology

[0002] Small Data Transmission (SDT) is a process that allows data and / or signaling transmission while the device remains in an inactive Radio Resource Control (RRC) state without transitioning to an RRC connected state. However, the application of SDT remains a topic for discussion. Summary of the Invention

[0003] This document relates to methods, systems, and computer program products used for wireless communication.

[0004] One aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal sending a random access (RA) report to a wireless communication node, the RA report including small data transmission (SDT) related information for random access channel (RACH) optimization.

[0005] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receiving a random access report (RA) from a wireless communication terminal, the RA report including small data transmission time distribution (SDT) related information for random access channel (RACH) optimization.

[0006] Various embodiments can preferably achieve the following features: Preferably, the SDT-related information includes at least one of the following: An indicator used to indicate whether the downlink (DL) reference signal received power (RSRP) is higher than the configured SDT RSRP threshold; Configured SDT RSRP threshold and current DL RSRP; An indication of whether the current amount of data to be transmitted meets the configured data volume threshold; or Configured data volume threshold and current data volume to be transmitted.

[0007] Preferably, the configured SDT RSRP threshold includes at least one of the following: sdt-RSRP-Threshold (sdt-RSRP-threshold) or sdt-RSRP-ThresholdMT (sdt-RSRP-thresholdMT), and / or the configured data volume threshold includes sdt-DataVolumeThreshold (sdt-data volume threshold).

[0008] Preferably, the SDT-related information includes Configuration Grant-SDT (CG-SDT) related information, and the CG-SDT related information includes at least one of the following: One or more storage CG-SDT configurations; Information used to determine time alignment (TA) verification; or Time-related information.

[0009] Preferably, the CG-SDT configuration of the one or more storage facilities includes at least one of the following: cg-SDT-RSRP-ThresholdSSB (cg-SDT-RSRP-ThresholdSSB) cg-SDT-MaxDurationToNextCG-Occasion (cg-SDT-MaxDurationToNextCG-Occasion) cg-MT-SDT-MaxDurationToNextCG-Occasion (cg-MT-SDT-MaxDurationToNextCG-Occasion) cg-SDT-RSRP-ChangeThreshold (cg-SDT-RSRP - Change Threshold), or CG-SDT-Configuration.

[0010] Preferably, the information used to determine the TA verification includes at least one of the following: DL RSRP for storage used for TA verification The current DL RSRP is checked when TA verification for CG-SDT is performed or when an SDT or CG-SDT procedure is initiated. A TA verification failure indication used to indicate that the TA verification has failed, or An indicator used to show whether the SDT dedicated time alignment timer is running.

[0011] Preferably, the time-related information includes at least one of the following: An indication of the time elapsed since the CG-SDT configuration was received. An indication of the time interval between the initiation of the SDT procedure and the first available CG opportunity for initializing the CG-SDT transmission, or An indication that the time interval between the initiation of the SDT process and the first available CG opportunity in time is not less than the configured maximum time interval.

[0012] Preferably, the CG-SDT related information corresponds to the RA attempt for SDT, allowing the wireless communication node to adjust at least one of the following: CG resources or RACH resources.

[0013] Preferably, the SDT-related information includes: Indication used to indicate RA purpose for Mobile Terminated (MT-SDT) devices.

[0014] Preferably, the SDT-related information includes: Indication used to indicate MT-SDT failure.

[0015] Preferably, the wireless communication node determines at least one of the following: In response to the presence of an indication in the RA report indicating the purpose of the RA for MT-SDT, and the absence of an indication in the RA report indicating MT-SDT failure, the RA initiated for the MT-SDT is successfully completed; or In response to the presence of both an indication for the purpose of an RA for MT-SDT and an indication for the failure of MT-SDT in the RA report, the RA initiated for MT-SDT fails.

[0016] Preferably, in response to the failure of the wireless communication terminal to initiate the SDT process, the RA report includes SDT-related information.

[0017] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a first wireless communication node sending an identifier of a second UE to a second wireless communication node in a request message for a first user equipment (UE), the identifier of the second UE corresponding to a PC5 Radio Link Control (RLC) channel for sidelink (SL) communication.

[0018] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a second wireless communication node receiving, in a request message for a first user equipment (UE), an identifier of a second UE from the first wireless communication node, the identifier of the second UE corresponding to a PC5 radio link control (RLC) channel for sidelink (SL) communication.

[0019] Various embodiments can preferably achieve the following features: Preferably, the identifier of the second UE includes a destination index for identifying the second UE.

[0020] Preferably, the destination index satisfies at least one of the following: The destination index is 5 bits long; The destination index value is indexed sequentially from 0 according to the same ascending order of the SL destination identifiers in the resource request list in the sidelink UE information; or The value of the destination index is indexed sequentially across the multiple resource request lists in the same order presented in the sidelink UE information.

[0021] Preferably, the first wireless communication node receives a response message from the second wireless communication node, the response message including an identifier of the second UE for the PC5 RLC channel.

[0022] Preferably, the identifier of the second UE corresponding to the PC5 RLC channel is sent via at least one of the following: UE context establishment request message; or UE context modification request message.

[0023] Preferably, the second wireless communication node sends a response message to the first wireless communication node, the response message including an identifier of the second UE for the PC5 RLC channel.

[0024] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a first wireless communication terminal transmitting an RLC mode indication of a PC5 radio link control (RLC) channel configured by a second wireless communication terminal to a wireless communication node.

[0025] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receiving an RLC mode indication of a PC5 wireless link control RLC channel configured by a second wireless communication terminal from a first wireless communication terminal.

[0026] Various embodiments can preferably achieve the following features: Preferably, the RLC mode indication includes an RLC acknowledged AM mode indication or an RLC unacknowledged UM mode indication.

[0027] Preferably, the RLC mode indication of the PC5 RLC channel is associated with an end-to-end (E2E) sidelink radio bearer (SLRB).

[0028] Preferably, the E2E SLRB is indicated by at least one of the source user equipment (UE) identifier, the destination UE identifier, or the E2E SLRB identifier.

[0029] Preferably, the RLC mode indication is carried in the Quality of Service (QoS) information at each SLRB level of the second hop of the E2E SLRB.

[0030] Another aspect of this 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 send a Random Access RA report to a wireless communication node via the communication unit, the RA report including Small Data Transmission Techniques (SDT) related information for Random Access Channel (RACH) optimization.

[0031] Another aspect of this 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 receive, via the communication unit, a random access report (RA) from a wireless communication terminal, the RA report including small data transmission time distribution (SDT) related information for random access channel (RACH) optimization.

[0032] Another aspect of this disclosure relates to a first wireless communication node. In one embodiment, the first wireless communication node includes a communication unit and a processor. The processor is configured to: transmit, via the communication unit, in a request message for a first user equipment (UE), an identifier of a second UE corresponding to a PC5 radio link control (RLC) channel for sidelink (SL) communication to a second wireless communication node.

[0033] Another aspect of this disclosure relates to a second wireless communication node. In one embodiment, the second wireless communication node includes a communication unit and a processor. The processor is configured to receive, via the communication unit, an identifier of a second UE from the first wireless communication node in a request message for a first user equipment (UE), the identifier of the second UE corresponding to a PC5 radio link control (RLC) channel for sidelink (SL) communication.

[0034] Another aspect of this disclosure relates to a relay wireless communication terminal. In one embodiment, the relay wireless communication terminal includes a communication unit and a processor. The processor is configured to transmit, via the communication unit, an RLC mode indication of a PC5 Radio Link Control (RLC) channel configured by a second wireless communication terminal to a wireless communication node.

[0035] Another aspect of this 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 receive, via the communication unit, an RLC mode indication of a PC5 Radio Link Control (RLC) channel configured by a second wireless communication terminal from a first wireless communication terminal.

[0036] This disclosure relates to a computer program product comprising a computer-readable program medium on which code is stored, the code, when executed by a processor, causes the processor to implement a wireless communication method according to any of the foregoing methods.

[0037] The exemplary embodiments disclosed herein are intended to provide features that will become readily apparent when taken in conjunction with the accompanying drawings and by referring to the following description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

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

[0039] The above and other aspects and their implementations are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

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

[0041] Figure 2 An example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure is shown.

[0042] Figures 3 to 8 A flowchart of a wireless communication method according to some embodiments of the present disclosure is shown. Detailed Implementation

[0043] In some embodiments, the SDT process can be initiated via transmission over a Random Access Channel (RACH) configured with system information. RACH configuration has a critical impact on user experience and overall network performance. RACH optimization for SDT can be considered for self-optimizing networks. Specifically, SDT-related information can be included in the Random Access (RA) report used for RACH optimization.

[0044] Self-organizing networks (SONs) are an automation technology designed to simplify and accelerate the planning, configuration, management, optimization, and repair of mobile radio access networks. SON functions and behaviors are defined and specified in generally accepted mobile industry recommendations developed by organizations such as 3GPP (3rd Generation Partnership Project) and NGMN (Next Generation Mobile Network). SON functions are typically divided into three main sub-functional groups (self-configuration, self-optimization, and self-repair), each containing numerous decomposed use cases. In some embodiments, RA optimization can be used for the self-optimization function.

[0045] In some embodiments, RACH configuration affects user experience and overall network performance. RACH collision probability, and consequently access establishment delay, data recovery delay from uplink (UL) asynchronous states, handover delay, transition delay from RRC_INACTIVE (RRC inactive), and beam failure recovery delay are all affected by RACH settings.

[0046] In some embodiments, performing RACH on the most suitable downlink beam is also important and can avoid unnecessary power spikes and failed RACH attempts. This is beneficial to both the network and the attempting device; it avoids unnecessary interference in the network and reduces experienced latency and UE power consumption. In some embodiments, automatic RACH parameter setting can be achieved by collecting RACH reports from the UE and exchanging PRACH parameters between gNodeBs (gNBs). RACH optimization is achieved by the UE providing RACH-related information reports to NG-RAN nodes and by exchanging PRACH configurations of normal UL carriers and supplementary uplink (SUL) carriers between Next-Generation Radio Access Network (NG-RAN) nodes.

[0047] Some aspects of this disclosure are provided in the following paragraphs, but this disclosure is not limited thereto.

[0048] Aspect 1: In SDT, data volume thresholds (e.g., sdt-DataVolumeThreshold (sdt - data volume threshold) ) and / or the reference signal received power (RSRP) threshold (e.g., sdt-RSRP-Threshold (sdt--RSRP-threshold) , sdt-RSRP- ThresholdMT (sdt-RSRP-thresholdMT) At least one of the following can be configured to the UE for determining whether to perform an SDT procedure initiated for Mobile Originated (MO)-SDT or Mobile Terminated (MT)-SDT. In some embodiments, the UE may initiate an MO-SDT procedure if the UL data to be transmitted is less than or equal to a data volume threshold, the DLRSRP is higher than a configured SDT RSRP threshold, and / or valid SDT resources are available. In some embodiments, upon receiving an MT-SDT indication in a paging message, the UE initiates an MT-SDT if the DL RSRP is higher than (only higher than) a configured threshold. Otherwise, a conventional random access procedure is initiated. An SDT procedure initiated for MO-SDT can be performed using a 2-step RA type or a 4-step RA type random access procedure (e.g., RA-SDT, RACH resources configured via system information) or by configuring grant type 1 (e.g., Configured Grant (CG)-SDT, CG resources configured via system information). RRCRelease (RRC release) put) It is executed using the dedicated signaling configuration in the system.

[0049] In some embodiments, configured data volume thresholds and / or RSRP thresholds can impact user experience and network performance, such as the allocation of SDT resources (including RACH and CG resources configured for SDT) and public RACH resources. In some embodiments, if one or both of the thresholds are set too strictly, only a few UEs may be able to initiate SDT procedures and use SDT resources. In some embodiments, a small number of UEs initiating SDT procedures may lead to a waste of resources reserved for SDT and a poor user experience. In some embodiments, a poor user experience indicates that the threshold for performing SDT is not expected to be met. On the other hand, if one or both of the thresholds are set too leniently, too many UEs (some with low DLRSRP) may initiate SDT procedures, thus potentially causing SDT resource congestion / resource contention, which may degrade SDT performance and / or RA performance. Therefore, when a UE fails to initiate an SDT procedure and / or actually initiates conventional RA, it is beneficial to report SDT-related information in the RA report to help the network (NW) fine-tune the thresholds used by the UE to determine whether to initiate an SDT procedure and / or for RACH optimization.

[0050] In some embodiments, each RACH may attempt to include (e.g., in the RA report) in the RA report. UEInformationResponse The message includes an indication that the DL RSRP (when the UE intends to initiate SDT transmission via RACH) is higher or lower than the configured SDT RSRP threshold (e.g., sdt-RSRP- Threshold or sdt-RSRP-ThresholdMT In some embodiments, the configured SDT RSRP threshold and the actual / current DL RSRP (when the SDT procedure is initiated) are reported in the RA report. Additionally, the RA report may include an indication that indicates whether the actual / current amount of data to be transferred meets the data volume threshold. In some embodiments, the configured data volume threshold and the actual / current amount of data to be transferred are included in the RA report.

[0051] In some embodiments, the actual / current amount of data to be transmitted may indicate the amount of data to be transmitted at a specific moment when the UE wants to initiate an SDT procedure, when the UE checks the conditions for initiating an SDT, and / or when the UE fails to initiate an SDT procedure and initiates a conventional RA procedure.

[0052] Similarly, in some embodiments, the actual / current DL RSRP may indicate the DLRSRP when the UE wants to initiate an SDT procedure, when the UE checks the conditions for initiating an SDT, and / or when the UE fails to initiate an SDT procedure and initiates a conventional RA procedure.

[0053] In some embodiments, if RA-SDT or Mobile Termination (MT)-SDT completes successfully, the DL RSRP may be higher than a threshold. However, if SDT fails, there may be various reasons, such as the SDT RSRP threshold or data volume threshold not being met, or one or more corresponding timers (e.g., T319a) expiring. In some embodiments, this indication can help the gNB determine or rule out RSRP as a cause of failure when SDT fails. The gNB can then fine-tune the SDT RSRP threshold or other SDT configurations to reduce / avoid SDT failures or invalid SDT transmissions. This can further benefit RACH optimization for SDT.

[0054] In some embodiments, as shown in the following example, the UE may attempt to message (e.g., ) every RACH. UEInformationResponse message The RA report within the RA includes instructions (e.g., dlRSRPAboveThreshold- SDT (dlRSRP above threshold - SDT) This indicates whether the DL RSRP is higher or lower than the configured SDT RSRP threshold, and this indication can be included in the RA report.

[0055] Aspect 2: In some embodiments, if the conditions for the data volume and DL RSRP for MO-SDT are met (e.g., the SDT data volume to be transmitted is less than or equal to a configured data volume threshold, and the DL RSRP is higher than a configured RSRP threshold), or the DL RSRP condition for MT-SDT is met (e.g., the DL RSRP is higher than a configured RSRP threshold), the UE can initiate an SDT procedure and first check whether there are valid CG resources available for SDT. If valid CG resources are available for SDT, the SDT procedure is initiated using the CG resources; otherwise, the SDT procedure is initiated using RACH resources.

[0056] In some embodiments, if the conditions for CG-SDT are not met, a RA is initiated for SDT transmission. In some embodiments, CG-SDT-related information (also referred to as info) is included in the RA report for the RA attempt for SDT so that the gNB knows why CG-SDT was not met. In some embodiments, the gNB may appropriately adjust / configure the thresholds / limits for SDT to utilize CG resources and comprehensively adjust / coordinate CG resources and RACH resources for SDT.

[0057] In some embodiments, the SDT process via CG resources can only be initiated if there is a valid UL timing alignment (TA) and the time interval between the initiation of the SDT process and the first available CG timing is less than a time threshold.

[0058] In some embodiments, the TA of the initial CG-SDT transmission is considered valid when at least one of the following conditions is met: 1) Compared to the stored downlink path loss reference RSRP value used for TA verification, the increase / decrease in the current RSRP value of the downlink path loss reference does not exceed a threshold (e.g., cg-SDT-RSRP-ChangeThreshold ); and / or 2) Timer (e.g., cg-SDT-TimeAlignmentTimer It is running (e.g., an SDT dedicated time alignment timer configured by the network via dedicated signaling).

[0059] In some embodiments, at least one of the following CG-SDT-related information may be included in the RA report: 1) The storage CG-SDT configuration (configured by the network) includes at least one of the following: cg-SDT-RSRP-ThresholdSSB; cg-SDT-MaxDurationToNextCG-Occasion; cg-MT-SDT-MaxDurationToNextCG-Occasion; cg-SDT-RSRP-ChangeThreshold; and / or CG-SDT-Configuration. 2) Information used to check / determine TA verification, including at least one of the following: - DL RSRP for storage used for TA verification; - When checking the TA verification for CG-SDT / when initiating the (CG-)SDT procedure, the current DL RSRP is checked; -TA verification failure indicator is used to indicate TA verification failure; and / or - Used to indicate the SDT dedicated time alignment timer (e.g., cg-SDT-TimeAlignmentTimer An indication of whether it is running (e.g., when checking TA verification for CG-SDT).

[0060] 3) Time-related information, including at least one of the following: - An indication of the time elapsed since the CG-SDT configuration was received (until the time for checking the TA verification for CG-SDT or initiating the SDT procedure) (e.g., timeSinceCG-SDTConfig (Time since CG-SDT configuration) ); - An indication of the time interval between the initiation of the SDT procedure and the first available CG opportunity for the initial CG-SDT transmission (e.g., timeGapTowardsFirstCGOccasion (Time interval from the first CGO event) ); and / or - Used to indicate time interval failure (e.g., the time interval between the initiation of the SDT procedure and the first available CG timing is not less than the configured maximum time interval (e.g., cg-SDT-MaxDurationToNextCG-Occasion or cg-MT- SDT-MaxDurationToNextCG-Occasion Instructions (e.g.) timeGap-Failed ).

[0061] Aspect 3: In the RA report, information related to the success of each RA attempt or information related to the failure of each RA attempt can be reported to the network for RACH optimization.

[0062] In some embodiments, the RACH resources used for MO-SDT (RA-SDT) are configured by RACH (e.g., RACH- ConfigCommon / RACH-ConfigCommonTwoStepRA (RACH Common Configuration) / Two-step RARACH public Configuration) The feature combination preamble within (e.g., Feature Combination Preambles The combination of features in ) (e.g., feature Combination (For example, smallData , redCap (reduces ability) , nsag , msg3-Repetitions , msg1-Repetitions , eRedCap (at least one of the following) to indicate.

[0063] In some embodiments, the network associates all possible preambles for the appended RACH configuration with one or more features or combinations of one or more features. In some embodiments, if SDT and / or other features are applicable to the RA procedure, the UE can set the feature combination (e.g., triggeredFeatureCombination This indicates all features in the RA report entry that triggered the random access procedure. In some embodiments, the UE can set feature combinations (e.g., usedFeatureCombination ) to indicate the combination of features associated with the random access resources (RACH resources) used in the random access procedure (e.g., Feature Combination One or more characteristics of ).

[0064] In addition, if a random access procedure is initiated for SDT and the SDT transmission fails, the UE may include an sdt-Failed indication in the RA report.

[0065] In some embodiments, if the RA report only reports a combination of features including SDT features (e.g., triggeredFeatureCombination)(No sdt-Failed If the instruction is received, the gNB can determine that the RA was initiated for MO-SDT and that the SDT transmission was successful.

[0066] In some embodiments, if the RA report reports a combination of features including SDT features (e.g., triggeredFeatureCombination )and sdt-Failed By indicating both, the gNB can determine that the RA was initiated for MO-SDT and that the SDT transmission failed.

[0067] In some embodiments, if the MT-SDT procedure is initiated on the RACH, the UE can only use RACH resources that are not configured for SDT. In some embodiments, public RACH resources are used for MT-SDT on the RACH. In some embodiments, sdt-Failed The indication can be reused to indicate MT-SDT failure.

[0068] In some embodiments, if the RA report only reports sdt-Failed Indicates, but does not include combinations of features (e.g., triggeredFeatureCombination (including SDT features) and / or combinations of features (e.g., usedFeatureCombination If ), it means that a public RACH resource is being used (e.g., the RACH resource for SDT not being used as indicated by the feature combination) and the RA initiated for MT-SDT has failed.

[0069] In some embodiments, if the RA is initiated for MT-SDT (e.g., using a public RACH resource / a combination of features without SDT) and the RA succeeds, the gNB may not be aware that the purpose of the RA is for MT-SDT transmission. To inform the gNB that the RA was initiated / triggered for MT-SDT transmission, information can be added to the RA report. raPurpose (ra purpose) This includes indications for MT-SDT (e.g., mt-SDT An example is shown below.

[0070] In some embodiments, if the instruction (e.g., mt-SDT ) was introduced to indicate raPurpose The purpose of RA used for MT-SDT transmission: -If the RA report includes the aforementioned instructions (e.g., mt-SDT ),and sdt-Failed If the instruction is not included, the gNB determines that the RA initiated by MT-SDT was successfully completed.

[0071] -If the RA report includes the aforementioned instructions (e.g., mt-SDT )and sdt-FailedIf both are indicated, gNB determines that the RA initiated by MT-SDT has failed.

[0072] Aspect 4: In some embodiments, Layer 2 (L2) UE-to-UE (U2U) relay is expected to be supported in a gNB Centralized Unit (CU) – Distributed Unit (DU) separation architecture. Signaling exchange between the CU and DU can be considered to establish / modify / release PC5 Radio Link Control (RLC) channels for U2U relay UEs / remote UEs.

[0073] In some embodiments, for each PC5 RLC channel in the list of PC5 RLC channels to be established / modified in the F1 UE context establishment / modification request message, a peer UE ID may be included, which indicates the peer UE to which the particular PC5 RLC channel is directed (i.e., the PC5 RLC channel will be established between the UE and the peer UE). In some embodiments, for the configuration of a U2U remote UE, the peer UE is a U2U relay UE.

[0074] In some embodiments, for the configuration of a U2U relay UE, the peer UE is either a source remote UE or a destination remote UE. The peer UE ID can be the peer UE's UE F1AP ID or UE L2 ID, or a destination index that identifies the destination / peer UE.

[0075] In some embodiments, the destination index is 5 bits long. In some embodiments, this value is set as an index that corresponds to a message (e.g., SidelinkUEInformationNR Messages (e.g., sl-TxResourceReqList (sl-Tx resource request list), sl-TxResourceReqListDisc (sl-Tx resource...) Request list discovery), sl-TxResourceReqListCommRelay (sl-Tx resource request list communication relay) and sl- TxResourceReqListL2-U2U (sl-Tx resource request list L2-U2U) If present, the SL (sidelink) destination identifier associated with the same destination reported in the report.

[0076] In some embodiments, this value is based on sidelink UE information (e.g., SidelinkUEInformationNR Messages (e.g., sl-TxResourceReqList, sl-TxResourceReqListDisc, sl- TxResourceReqListCommRelay and sl-TxResourceReqListL2-U2U The SL destination identifiers in the resource request list are indexed in the same ascending order, starting from 0.

[0077] In some embodiments, when multiple lists are reported, this value is based on sidelink UE information (e.g., SidelinkUEInformaitonNRThe destination index is indexed sequentially across all lists in the same order presented in the message. In some embodiments, when multiple lists are reported, the destination index value is indexed sequentially across multiple resource request lists in the same order presented in the sidelink UE information.

[0078] In some embodiments, in the response message (e.g., F1 UE context establishment / modification response), the DU may identify the PC5 RLC channel to be established / modified / released or the PC5 RLC channel that failed to be established / modified. For each PC5 RLC channel in the response message, the peer UE ID may also be included.

[0079] In some embodiments, the DU can initiate the modification / release of PC5 RLC channels during the F1 UE context modification request process. For each PC5 RLC channel in the UE context modification request / confirmation message, the peer UE ID can also be included.

[0080] Aspect 5: In some embodiments, the Rx (receiving party) UE reports sl-RLC-ModeIndication This indicates the RLC mode of the bidirectional SL-DRB associated with the RLC bearer configured with the Tx (sender) UE, thereby allowing the serving gNB to avoid configuration conflicts for the bidirectional SL-DRB (Data Radio Bearer). For example, it prevents situations where the RLC AM (acknowledged mode) mode for the bidirectional SL-DRB is configured by the Tx UE, while the RLC UM (unacknowledged mode) mode for the bidirectional SL-DRB is configured by the serving gNB of the Rx UE. sl-RLC-ModeIndication The report states that QFI (QoS flow identity) is included to indicate the association between RLC mode and bidirectional SL-DRB.

[0081] In some embodiments, for L2 (layer 2) U2U (UE to UE) relay, there is no bidirectional SL-DRB between the relay UE and the remote UE. When performing SUI (… sidelinkUEInformation When reporting, the relay UE needs to report to its serving gNB the RLC mode (RLC AM mode or RLC UM mode) of the established PC5 relay RLC channel configured by the source remote UE, so that the serving gNB can configure the same RLC mode for that PC5 relay RLC channel (to avoid configuration conflicts). In some embodiments, the issue of how to indicate the association between the RLC mode and the PC5 relay RLC channel is addressed.

[0082] In some embodiments, by receiving a data packet from a PC5 relay RLC channel originating from a source remote UE, including an SRAP (Sidelink Relay Adaptation Protocol) header (containing the source UE ID, destination UE ID, and E2E (end-to-end) SL bearer ID), the relay UE can identify the mapping from the E2E SLRB (Sidelink Radiobearer) to the PC5 relay RLC channel. Therefore, in some embodiments, the relay UE can report the RLC mode of the PC5 relay RLC channel associated with the E2E SLRB. In some embodiments, the E2E SLRB can be indicated by at least one of the source UE ID, destination UE ID, and / or E2E SLRB ID. In some embodiments, the E2E SLRB can be indicated by an E2E SLRB index identifying the E2E SLRB ID. The E2E SLRB index is sequentially indexed starting from 0 in the same ascending order of the E2ESLRB identifier within the source-destination UE pair, and the E2E SLRBs are also sequentially indexed across multiple UE pairs in the same order presented by the UE pairs. Multiple E2E SLRBs may be mapped to a single PC5 trunk RLC channel on the first hop (in the direction from the source remote UE to the relay UE). The relay UE can report the RLC mode of the PC5 trunk RLC channel associated only with one of the multiple mapped E2E SLRBs.

[0083] In some embodiments, in order to request the second-hop configuration for L2 U2U relay from the gNB, the relay UE may report per-SLRB level QoS information of the second hop of the E2E SLRB in the SUI (e.g., reporting the destination / target UE ID, source UE ID, and per-SLRB QoS configuration information of the E2E SLRB). SL-PerSLRB-QoS-Info (SL-PerSLRB-QoSxinxi) In the example of RLC mode indication for the PC5 relay RLC channel (on the first hop), the RLC mode indication can be included in the per SLRB level QoS information of the second hop of the E2ESLRB (e.g., SL-PerSLRB-QoS-Info In ), with E2E SLRB ( sl- RemoteUE-SLRB-Identity (SL-RemoteUE-SLRB-Identity) (related to)

[0084] In some embodiments, when receiving PC5 RLC channel configuration from a relay UE, a remote UE may send an RLC mode indication of the PC5 RLC channel configured by the relay UE to the NW. In some embodiments, the remote UE may report the RLC mode of the PC5 relay RLC channel associated with the E2E SLRB. In some embodiments, the E2E SLRB may be indicated by at least one of the source UE ID, the destination / target UE ID, and / or the E2E SLRB ID. In some embodiments, the E2E SLRB may be indicated by an E2E SLRB index that identifies the E2E SLRB ID.

[0085] The following provides an example of RLC mode indication.

[0086] In some embodiments of this disclosure, for SDTs on RACH (e.g., MO RA-SDT or MT-SDT), an indication may be included in the RA report to indicate whether the DL RSRP (when the UE intends to initiate an SDT transmission on RACH) is higher or lower than a configured SDT RSRP threshold.

[0087] In some embodiments of this disclosure, CG-SDT related information may be considered for inclusion in the RA report so that the gNB can appropriately adjust / configure thresholds / limits for SDT using CG resources and comprehensively adjust / harmonize CG resources and RACH resources used for SDT.

[0088] In some embodiments of this disclosure, instructions are given mt-SDT Instructions can be included in the RA report. raPurpose In this way, the gNB knows that the RA is initiated / triggered for MT-SDT transmission.

[0089] Figure 1The diagram relates to a wireless communication terminal 30 according to an embodiment of the present disclosure. The wireless communication terminal 30 may be a tag, mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless communication terminal 30 can be used to implement the UE described in this disclosure. The wireless communication 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 storing program code 312 accessed and executed by the processor 300. Embodiments of the storage unit 310 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 devices. The communication unit 320 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) based on the processing results of the processor 300. In one embodiment, the communication unit 320 sends and receives signals via at least one antenna 322 or via wiring.

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

[0091] The processor 300 can implement any of the steps or operations in the exemplary embodiments on the wireless communication terminal 30, for example by executing program code 312.

[0092] The communication unit 320 may be a transceiver. Alternatively or additionally, the communication unit 320 may combine a transmitting unit and a receiving unit, which are configured to transmit signals to and receive signals from the wireless communication node, respectively.

[0093] In some embodiments, the wireless communication terminal 30 can be used to perform the operations of the UE described in this disclosure. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the operations described in this disclosure. For example, the processor 300 performs operations and sends or receives signals, messages and / or information through the communication unit 320.

[0094] Figure 2The diagram relates to a wireless communication node 40 according to an embodiment of the present disclosure. The wireless communication node 40 may be a satellite, base station (BS), gNB, network, network entity, Domain Name System (DNS) server, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), radio access network (RAN), next-generation RAN (NG-RAN), data network, core network, a communication node in the core network, or Radio Network Controller (RNC), and is not limited thereto. Furthermore, the wireless communication node 40 may include (perform) at least one network function, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Application Function (AF), etc. The wireless communication node 40 may be used to implement the gNB or NW of the present disclosure. The wireless communication 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 storing program code 412 accessed and executed by the processor 400. Examples of storage units 410 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disks, and optical data storage devices. The communication unit 420 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) based on the processing results of the processor 400. In one embodiment, the communication unit 420 sends and receives signals via at least one antenna 422 or via wiring.

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

[0096] The processor 400 can implement any of the steps or operations described in the exemplary embodiments on the wireless communication node 40, for example, by executing program code 412.

[0097] As an alternative or additional solution, the communication unit 420 may combine a transmitting unit and a receiving unit, which are configured to transmit signals, messages or information to a wireless communication node or wireless communication terminal and to receive signals, messages or information from a wireless communication node or wireless communication terminal, respectively.

[0098] In some embodiments, the wireless communication node 40 can be used to perform the gNB or NW described in this disclosure. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described in this disclosure. For example, the processor 400 performs operations and transmits or receives signals through the communication unit 420.

[0099] According to embodiments of this disclosure, a wireless communication method is also provided. In one embodiment, the wireless communication method can be performed 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 in this disclosure, but is not limited thereto.

[0100] Reference Figure 3 In one embodiment, the wireless communication method includes: a wireless communication terminal sending a random access report (RA) to a wireless communication node, the RA report including small data transmission distance (SDT) related information for random access channel (RACH) optimization.

[0101] In some embodiments, the wireless communication terminal used in this disclosure may indicate the UE described in aspects 1 to 3 above.

[0102] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB or NW described in aspects 1 to 3 above.

[0103] The details in this regard can be found in the paragraphs above, and will not be repeated here.

[0104] Another wireless communication method is also provided according to embodiments of this disclosure. In one embodiment, the wireless communication method can be performed using a wireless communication node (e.g., a gNB or NW). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0105] Reference Figure 4 In one embodiment, the wireless communication method includes: receiving a random access report (RA) from a wireless communication terminal by a wireless communication node, the RA report including small data transmission distance (SDT) related information for random access channel (RACH) optimization.

[0106] In some embodiments, the wireless communication terminal used in this disclosure may indicate the UE described in aspects 1 to 3 above.

[0107] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB or NW described in aspects 1 to 3 above.

[0108] The details in this regard can be found in the paragraphs above, and will not be repeated here.

[0109] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a first wireless communication node (e.g., gNB-CU). In one embodiment, the first wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0110] Reference Figure 5 In one embodiment, the wireless communication method includes: a first wireless communication node sending an identifier of a second user equipment UE to a second wireless communication node in a request message for a first user equipment UE, the identifier of the second UE corresponding to a PC5 radio link control RLC channel for sidelink SL communication.

[0111] In some embodiments, the first wireless communication node used in this disclosure may refer to the gNB-CU described in aspect 4 above.

[0112] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB-DU described in aspect 4 above.

[0113] In some embodiments, the request message used in this disclosure may refer to the F1 UE context establishment / modification request message described in aspect 4 above.

[0114] In some embodiments, the first wireless communication node receives a response message from the second wireless communication node, the response message including an identifier for the second UE for the PC5 RLC channel, and the request message used in this disclosure may indicate the F1 UE context establishment / modification response message described in aspect 4 above.

[0115] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0116] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be implemented using a second wireless communication node (e.g., gNB-DU). In one embodiment, the second wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0117] Reference Figure 6 In one embodiment, the wireless communication method includes: receiving, in a request message for a first user equipment (UE), an identifier of a second UE from the first wireless communication node, the identifier of the second UE corresponding to a PC5 radio link control (RLC) channel for sidelink (SL) communication.

[0118] In some embodiments, the first wireless communication node used in this disclosure may refer to the gNB-CU described in aspect 4 above.

[0119] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB-DU described in aspect 4 above.

[0120] In some embodiments, the request message used in this disclosure may refer to the F1 UE context establishment / modification request message described in aspect 4 above.

[0121] In some embodiments, the second wireless communication node sends a response message to the first wireless communication node, the response message including an identifier of the second UE for the PC5 RLC channel, and the request message used in this disclosure may indicate the F1 UE context establishment / modification response message described in aspect 4 above.

[0122] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0123] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a relay wireless communication terminal (e.g., a relay UE). In one embodiment, the relay wireless communication terminal can be implemented using the wireless communication terminal 30 described in this disclosure, but is not limited thereto.

[0124] Reference Figure 7 In one embodiment, the wireless communication method includes: a first wireless communication terminal sending a radio link control (RLC) mode indication of a PC5 RLC channel configured by a second wireless communication terminal to a wireless communication node.

[0125] In some embodiments, the first wireless communication terminal used in this disclosure may indicate the relay UE described in aspect 5 above.

[0126] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB or NW described in aspect 5 above.

[0127] In some embodiments, the second wireless communication terminal used in this disclosure may indicate the remote UE described in aspect 5 above.

[0128] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0129] Another wireless communication method is also provided according to embodiments of this disclosure. In one embodiment, the wireless communication method can be performed using a wireless communication node (e.g., a gNB or NW). In one embodiment, the second wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0130] Reference Figure 8 In one embodiment, the wireless communication method includes: receiving, by a wireless communication node, a radio link control (RLC) mode indication of a PC5 RLC channel configured by a second wireless communication terminal from a first wireless communication terminal.

[0131] In some embodiments, the first wireless communication terminal used in this disclosure may indicate the relay UE described in aspect 5 above.

[0132] In some embodiments, the wireless communication node used in this disclosure may refer to the gNB or NW described in aspect 5 above.

[0133] In some embodiments, the second wireless communication terminal used in this disclosure may indicate the remote UE described in aspect 5 above.

[0134] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0135] In some embodiments, the side-link UE information used in this disclosure may indicate the information described in aspect 5 above. SidelinkUEInformaitonNR .

[0136] While various embodiments of the present disclosure have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functionality of the present disclosure. However, those skilled in the art will understand that the present disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment herein may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited to any of the exemplary embodiments described above.

[0137] It should be understood that in this disclosure, the term "and / or" or the symbol " / " can include any and all combinations of one or more of the associated listed items. For example, A and / or B and / or C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A and B and C. Similarly, A / B / C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A and B and C.

[0138] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing two or more elements, or multiple instances of a single element. Therefore, references to the first and second elements do not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0139] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0140] Those skilled in the art will also understand that any of the various illustrative logic blocks, units, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination thereof), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit"), or any combination of these technologies.

[0141] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, operations, and steps have been generally described above according to their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more of the functions described herein. As used herein with respect to a specified operation or function, the terms "configured to" or "configured for" refer to processors, devices, components, circuits, structures, machines, units, etc., being physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0142] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, units, devices, components, and circuits described herein can be implemented within or executed 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 devices, or any combination thereof. Logic blocks, units, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If these functions are implemented in software, they may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps or operations of the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium.

[0143] Computer-readable media include both computer storage media and communication media, with the latter including any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium that is accessible to a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc 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 is accessible to a computer.

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

[0145] Furthermore, memory or other storage devices and communication components may be used in embodiments of this disclosure. It should be understood that, for clarity, the above description refers to embodiments of this disclosure with reference to different functional units and processors. However, it will be apparent that any suitable allocation of functionality can be used among different functional units, processing logic elements, or domains without diminishing the scope of this disclosure. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable methods for providing said functionality and do not indicate a strict logical or physical structure or organization.

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

Claims

1. A wireless communication method, comprising: The wireless communication terminal sends a random access report (RA) to the wireless communication node. The RA report includes information related to small data transmission technique (SDT) for RACH optimization.

2. The wireless communication method according to claim 1, wherein, The SDT-related information includes at least one of the following: An indicator used to indicate whether the downlink DL reference signal received power RSRP is higher than the configured SDT RSRP threshold; Configured SDT RSRP threshold and current DL RSRP; An indication of whether the current amount of data to be transmitted meets the configured data volume threshold; or Configured data volume threshold and current data volume to be transmitted.

3. The wireless communication method according to claim 2, wherein, The configured SDT RSRP threshold includes at least one of the following: sdt-RSRP-Threshold or sdt-RSRP-ThresholdMT And / or the configured data volume threshold includes sdt-DataVolumeThreshold .

4. The wireless communication method according to any one of claims 1 to 3, wherein, The SDT-related information includes configuration authorization-SDT CG-SDT-related information, and the CG-SDT-related information includes at least one of the following: One or more storage CG-SDT configurations; Information used to determine time alignment (TA) verification; or Time-related information.

5. The wireless communication method according to claim 4, wherein, The CG-SDT configuration of the one or more storage systems includes at least one of the following: cg-SDT-RSRP-ThresholdSSB, cg-SDT-MaxDurationToNextCG-Occasion, cg-MT-SDT-MaxDurationToNextCG-Occasion, cg-SDT-RSRP-ChangeThreshold ,or CG-SDT-Configuration 。 6. The wireless communication method according to claim 5, wherein, The information used to determine the TA verification includes at least one of the following: DL RSRP for storage used for TA verification The current DL RSRP is checked when TA verification for CG-SDT is performed or when an SDT procedure or CG-SDT procedure is initiated. A TA verification failure indication used to indicate that the TA verification has failed, or An indicator used to show whether the SDT dedicated time alignment timer is running.

7. The wireless communication method according to claim 5 or 6, wherein, The time-related information includes at least one of the following: An indicator used to indicate the time elapsed since the CG-SDT configuration was received. An indication of the time interval between the initiation of the SDT process and the first available CG opportunity for initializing the CG-SDT transmission, or An indication used to indicate that the time interval between the initiation of the SDT process and the first available CG opportunity in time is not less than the configured maximum time interval.

8. The wireless communication method according to any one of claims 4 to 7, wherein, The CG-SDT related information corresponds to the RA attempt for SDT, allowing the wireless communication node to adjust at least one of the following: CG resources or RACH resources.

9. The wireless communication method according to any one of claims 1 to 8, wherein, The SDT-related information includes: Indication used to indicate the RA purpose for mobile terminal SDT MT-SDT.

10. The wireless communication method according to any one of claims 1 to 9, wherein, The SDT-related information includes: Indication used to indicate MT-SDT failure.

11. The wireless communication method according to any one of claims 1 to 3, wherein, In response to the failure of the wireless communication terminal to initiate the SDT process, the RA report includes SDT-related information.

12. A wireless communication method, comprising: The wireless communication node receives a random access report (RA) from the wireless communication terminal. The RA report includes small data transmission (SDT) related information for RACH optimization of the random access channel.

13. The wireless communication method according to claim 12, wherein, The SDT-related information includes at least one of the following: An indicator used to indicate whether the downlink DL reference signal received power RSRP is higher than the configured SDT RSRP threshold; Configured SDT RSRP threshold and current DL RSRP; An indicator used to indicate whether the current amount of data to be transmitted meets the configured data volume threshold; or Configured data volume threshold and current data volume to be transmitted.

14. The wireless communication method according to claim 13, wherein, The configured SDT RSRP threshold includes at least one of the following: sdt-RSRP-Threshold or sdt-RSRP-ThresholdMT And / or the configured data volume threshold includes sdt-DataVolumeThreshold .

15. The wireless communication method according to any one of claims 12 to 14, wherein, The SDT-related information includes configuration authorization-SDT CG-SDT-related information, and the CG-SDT-related information includes at least one of the following: One or more storage CG-SDT configurations; Information used to determine time alignment (TA) verification; or Time-related information.

16. The wireless communication method according to claim 15, wherein, The CG-SDT configuration of the one or more storage systems includes at least one of the following: cg-SDT-RSRP-ThresholdSSB, cg-SDT-MaxDurationToNextCG-Occasion, cg-MT-SDT-MaxDurationToNextCG-Occasion, cg-SDT-RSRP-ChangeThreshold ,or CG-SDT-Configuration 。 17. The wireless communication method according to claim 16, wherein, The information used to determine the TA verification includes at least one of the following: DL RSRP for storage used for TA verification The current DL RSRP is checked when TA verification for CG-SDT is performed or when an SDT procedure or CG-SDT procedure is initiated. A TA verification failure indication used to indicate that the TA verification has failed, or An indicator used to show whether the SDT dedicated time alignment timer is running.

18. The wireless communication method according to claim 16 or 17, wherein, The time-related information includes at least one of the following: An indication of the time elapsed since the CG-SDT configuration was received. An indication of the time interval between the initiation of the SDT procedure and the first available CG opportunity for initializing the CG-SDT transmission, or An indication that the time interval between the initiation of the SDT process and the first available CG opportunity in time is not less than the configured maximum time interval.

19. The wireless communication method according to any one of claims 15 to 18, wherein, The CG-SDT related information corresponds to the RA attempt for SDT, allowing the wireless communication node to adjust at least one of the following: CG resources or RACH resources.

20. The wireless communication method according to any one of claims 12 to 19, wherein, The SDT-related information includes: Indication used to indicate the RA purpose for mobile terminal SDT MT-SDT.

21. The wireless communication method according to any one of claims 12 to 20, wherein, The SDT-related information includes: Indication used to indicate MT-SDT failure.

22. The wireless communication method according to any one of claims 12 to 21, wherein, The wireless communication node determines at least one of the following: In response to the presence of an indication in the RA report for the purpose of the RA for the MT-SDT, and the absence of an indication in the RA report for the failure of the MT-SDT, the RA initiated for the MT-SDT is successfully completed; or In response to the presence of both an indication for the purpose of an RA for MT-SDT and an indication for the failure of MT-SDT in the RA report, the RA initiated for MT-SDT fails.

23. The wireless communication method according to any one of claims 12 to 14, wherein, In response to the failure of the wireless communication terminal to initiate the SDT process, the RA report includes SDT-related information.

24. A wireless communication method, comprising: In a request message for a first user equipment (UE), the first wireless communication node sends the identifier of the second UE to the second wireless communication node. The identifier of the second UE corresponds to the PC5 radio link control (RLC) channel used for sidelink SL communication.

25. The wireless communication method according to claim 24, wherein, The identifier of the second UE includes a destination index used to identify the second UE.

26. The wireless communication method according to claim 25, wherein, The destination index satisfies at least one of the following: The destination index is 5 bits long; The value of the destination index is indexed sequentially from 0 in the same ascending order as the SL destination identifier in the resource request list in the sidelink UE information; or The value of the destination index is indexed sequentially across the multiple resource request lists in the same order presented in the sidelink UE information.

27. The wireless communication method according to any one of claims 24 to 26, wherein, The first wireless communication node receives a response message from the second wireless communication node, the response message including an identifier of the second UE for the PC5 RLC channel.

28. The wireless communication method according to any one of claims 24 to 27, wherein, The identifier of the second UE corresponding to the PC5 RLC channel is sent via at least one of the following: UE context establishment request message; or UE context modification request message.

29. A wireless communication method, comprising: The second wireless communication node receives the identifier of the second UE from the first wireless communication node in a request message for the first user equipment (UE). The identifier of the second UE corresponds to the PC5 radio link control (RLC) channel used for sidelink SL communication.

30. The wireless communication method according to claim 29, wherein, The identifier of the second UE includes a destination index used to identify the second UE.

31. The wireless communication method according to claim 30, wherein, The destination index satisfies at least one of the following: The destination index is 5 bits long; The value of the destination index is indexed sequentially from 0 in the same ascending order of the SL destination identifiers in the resource request list in the sidelink UE information; or The value of the destination index is indexed sequentially across the multiple resource request lists in the same order presented in the sidelink UE information.

32. The wireless communication method according to any one of claims 29 to 31, wherein, The second wireless communication node sends a response message to the first wireless communication node, the response message including an identifier for the second UE on the PC5 RLC channel.

33. The wireless communication method according to any one of claims 29 to 32, wherein, The identifier of the second UE corresponding to the PC5 RLC channel is sent via at least one of the following: UE context establishment request message; or UE context modification request message.

34. A wireless communication method, comprising: The first wireless communication terminal sends an RLC mode indication of the PC5 wireless link control RLC channel configured by the second wireless communication terminal to the wireless communication node.

35. The wireless communication method according to claim 34, wherein, The RLC mode indication includes RLC acknowledged AM mode indication or RLC unacknowledged UM mode indication.

36. The wireless communication method according to claim 34 or 35, wherein, The RLC mode indication of the PC5 RLC channel is associated with the end-to-end E2E sidelink radio bearer SLRB.

37. The wireless communication method according to claim 36, wherein, The E2E SLRB is indicated by at least one of the source user equipment (UE) identifier, the destination UE identifier, or the E2E SLRB identifier.

38. The wireless communication method according to any one of claims 34 to 37, wherein, The RLC mode indication is carried in the Quality of Service (QoS) information at each SLRB level for the second hop of the E2E SLRB.

39. A wireless communication method, comprising: The wireless communication node receives the RLC mode indication of the PC5 wireless link control RLC channel configured by the second wireless communication terminal from the first wireless communication terminal.

40. The wireless communication method according to claim 39, wherein, The RLC mode indication includes RLC acknowledged AM mode indication or RLC unacknowledged UM mode indication.

41. The wireless communication method according to claim 39 or 40, wherein, The RLC mode indication of the PC5 RLC channel is associated with the end-to-end E2E sidelink radio bearer SLRB.

42. The wireless communication method according to claim 41, wherein, The E2E SLRB is indicated by at least one of the source user equipment (UE) identifier, the destination UE identifier, or the E2E SLRB identifier.

43. The wireless communication method according to any one of claims 39 to 42, wherein, The RLC mode indication is carried in the Quality of Service (QoS) information at each SLRB level for the second hop of the E2E SLRB.

44. A wireless communication terminal, comprising: Communication unit; as well as The processor is configured to send a random access report (RA) to a wireless communication node via the communication unit, the RA report including small data transmission distance (SDT) related information for random access channel (RACH) optimization.

45. The wireless communication terminal according to claim 44, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 2 to 11.

46. ​​A wireless communication node, comprising: Communication unit; as well as The processor is configured to receive a random access report (RA) from a wireless communication terminal via the communication unit, the RA report including small data transmission distance (SDT) related information for random access channel (RACH) optimization.

47. The wireless communication node according to claim 46, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 13 to 23.

48. A first wireless communication node, comprising: Communication unit; as well as The processor is configured to send an identifier of a second UE to a second wireless communication node via the communication unit in a request message for a first user equipment (UE), the identifier of the second UE corresponding to a PC5 radio link control (RLC) channel for sidelink SL communication.

49. The first wireless communication node according to claim 48, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 25 to 28.

50. A second wireless communication node, comprising: Communication unit; as well as The processor is configured to receive, via the communication unit, an identifier of a second UE from a first wireless communication node in a request message for a first user equipment (UE), the identifier of the second UE corresponding to a PC5 radio link control (RLC) channel for sidelink (SL) communication.

51. The second wireless communication node according to claim 50, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 30 to 33.

52. A first wireless communication terminal, comprising: Communication unit; as well as The processor is configured to transmit, via the communication unit, an RLC mode indication of the PC5 wireless link control RLC channel configured by the second wireless communication terminal to the wireless communication node.

53. The first wireless communication terminal according to claim 52, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 35 to 38.

54. A wireless communication node, comprising: Communication unit; as well as The processor is configured to receive, via the communication unit, an RLC mode indication of the PC5 wireless link control RLC channel configured by the second wireless communication terminal from the first wireless communication terminal.

55. The wireless communication node according to claim 54, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 40 to 43.

56. A computer program product comprising a computer-readable program medium on which code is stored, the code, when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1 to 43.

Images