[go: up one dir, main page]

WO2025166597A1 - Systèmes et procédés d'accès aléatoire à signalisation réduite - Google Patents

Systèmes et procédés d'accès aléatoire à signalisation réduite

Info

Publication number
WO2025166597A1
WO2025166597A1 PCT/CN2024/076480 CN2024076480W WO2025166597A1 WO 2025166597 A1 WO2025166597 A1 WO 2025166597A1 CN 2024076480 W CN2024076480 W CN 2024076480W WO 2025166597 A1 WO2025166597 A1 WO 2025166597A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink transmission
wireless communication
information
response
resource
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/076480
Other languages
English (en)
Inventor
Fangyu CUI
Nan Zhang
Wei Cao
Ziyang Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2024/076480 priority Critical patent/WO2025166597A1/fr
Publication of WO2025166597A1 publication Critical patent/WO2025166597A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the disclosure relates generally to wireless communications, including but not limited to systems and methods for random access with reduced signaling.
  • the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
  • the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
  • 5G-AN 5G Access Network
  • 5GC 5G Core Network
  • UE User Equipment
  • the elements of the 5GC also called Network Functions
  • Communication via satellite is one of the typical scenarios of the non-terrestrial networks in 3GPP standardization.
  • example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
  • a wireless communication device may send an uplink transmission to access a network to a network node.
  • the uplink transmission is physical uplink shared channel (PUSCH) transmission.
  • send an uplink transmission to access a network means a wireless communication device send a PUSCH as a first step in random access procedure.
  • the wireless communication device may receive a response to the uplink transmission from the network node.
  • the wireless communication device may receive at least one configuration for the uplink transmission from the network node.
  • the configuration can be received in at least one of: a master information block (MIB) broadcast, a system information block (SIB) broadcast, a multicast, a dedicated radio resource control (RRC) signaling, a media access control control element (MAC CE) signaling, or a downlink control information (DCI) signaling.
  • MIB master information block
  • SIB system information block
  • RRC dedicated radio resource control
  • MAC CE media access control control element
  • DCI downlink control information
  • the configuration for the uplink transmission may comprise at least one of: grant information of the uplink transmission; response configuration to the uplink transmission; time information of at least one resource of the uplink transmission; frequency information of at least one resource of the uplink transmission; contention-related information of the uplink transmission; condition information for performing the uplink transmission; a mapping relationship between the at least one resource for the uplink transmission and a synchronization signal; or a mapping relationship between the at least one resource for the uplink transmission and a random access channel (RACH) occasion.
  • RACH random access channel
  • the grant information may comprise at least one of a Modulation and Coding Scheme (MCS) , a Transport Block Size (TBS) , a maximum TBS, whether a TBS less than the indicated TBS is allowed, whether a subset of potential TBSs is allowed, a time-domain resource, a frequency-domain resource, a number of repetitions, power allocation, hopping configuration, Demodulation Reference Signal (DMRS) parameter, or carrier configuration.
  • MCS Modulation and Coding Scheme
  • TBS Transport Block Size
  • a maximum TBS whether a TBS less than the indicated TBS is allowed, whether a subset of potential TBSs is allowed, a time-domain resource, a frequency-domain resource, a number of repetitions, power allocation, hopping configuration, Demodulation Reference Signal (DMRS) parameter, or carrier configuration.
  • MCS Modulation and Coding Scheme
  • TBS Transport Block Size
  • DMRS Demodulation Reference Signal
  • the response configuration may comprise at least one of a timer or time window, a contention resolution timer, a number of repetitions, search space, frequency hopping, frequency-domain resource, a Transport Block Size (TBS) , a maximum TBS, resource offset of feedback of the response, or repetition factor of the feedback.
  • the time information may comprise at least one of a periodicity, start time, offset, time interval between two uplink resources of the at least one uplink resource, number of the at least one uplink resources in a time domain per unit of the at least one time resource.
  • the frequency information may comprise at least one of a start frequency, offset, frequency interval between two uplink resources of the at least one uplink resource, number of the at least one uplink resources in a frequency domain.
  • the contention-related information may comprise at least one of: a number of Demodulation Reference Signal (DMRS) sequences, parameters, or ports; a list of DMRS sequences, parameters, or port; a number of code sequences or parameters; a length of a code sequence or a parameter; or a list of code sequences or parameters.
  • DMRS Demodulation Reference Signal
  • condition information may comprise at least one of an enabling indication, signal strength threshold, time duration, start time.
  • the uplink transmission can be sent in response to at least one of: a signal quality at the wireless communication device is greater than or equal to a threshold; a parameter for uplink pre-compensation is valid; a Timing Advance (TA) is currently valid; time at which the uplink transmission is sent is within a duration configured by the network node; receiving from the network node an enabling indication.
  • a signal quality at the wireless communication device is greater than or equal to a threshold
  • a parameter for uplink pre-compensation is valid
  • a Timing Advance (TA) is currently valid
  • time at which the uplink transmission is sent is within a duration configured by the network node
  • receiving from the network node an enabling indication a signal quality at the wireless communication device is greater than or equal to a threshold.
  • TA Timing Advance
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • code sequences e.g., OCC (Orthogonal covering code)
  • OCC Orthogonal covering code
  • UEs using different code sequences within same time-frequency resource can be distinguished by the BS by de-multiplexing.
  • the UE may not need msg1 (e.g., PRACH preamble) /msg2 (e.g., RAR and/or scheduling PDCCH) for initial access to achieve synchronization.
  • msg1 e.g., PRACH preamble
  • msg2 e.g., RAR and/or scheduling PDCCH
  • the UE may be able to directly perform PUSCH transmission (e.g., transmit msg3) in random access procedure to reduce the delay and signaling overhead as shown in FIG. 4.
  • FIG. 4 illustrates an example direct physical uplink shared channel (PUSCH) transmission based random access channel (RACH) , in accordance with some embodiments of the present disclosure.
  • PUSCH direct physical uplink shared channel
  • RACH random access channel
  • direct PUSCH transmission refers to sending a PUSCH without msg1 or msg2 in random access. In some embodiments, direct PUSCH transmission refers to sending a PUSCH in the first step in random access. In some embodiments, direct PUSCH transmission refers to sending a PUSCH without sending a PRACH preamble previously.
  • broadcast/multicast based configuration of PUSCH occasion/resource can be supported especially considering initial access case.
  • At least one of following information may be configured by the BS via broadcast/multicast, e.g., system information block (SIB) or master information block (MIB) .
  • SIB system information block
  • MIB master information block
  • the BS may configure at least one of: modulation and coding scheme (MCS) , transport block size (TBS) , maximum TBS, time resource (e.g., number of resource unit) , frequency resource (e.g., carrier, physical resource block (PRB) , subPRB or subcarrier configuration/allocation) , number of repetitions, power allocation (e.g., parameters of initial power or ramping rate) , hopping configuration (hopping pattern or interval) , demodulation reference signals (DMRS) parameter (e.g., cyclic shift, scrambling ID, port number, length, etc. ) , carrier configuration.
  • MCS modulation and coding scheme
  • TBS transport block size
  • maximum TBS time resource (e.g., number of resource unit) , frequency resource (e.g., carrier, physical resource block (PRB) , subPRB or subcarrier configuration/allocation) , number of repetitions, power allocation (e.g., parameters of initial power or ramping rate) , hopping
  • parameters on the flexibility of PUSCH transmission may be configured. For example, whether smaller TBS than the indicated TBS is allowed (means the indicated TBS is maximum TBS) , or whether a subset of potential TBS is allowed. And different parameters (e.g., TBS) may be configured for different PUSCH occasion/resource or different coverage levels.
  • the BS may configure at least one of: timer/time window for response (e.g., length of timer/time window and/or start time of timer/time window) , contention resolution timer (e.g., length of timer) , number of repetitions of PDCCH, search space for PDCCH (e.g., starting time and offset of search space) , frequency hopping of PDCCH/PDSCH, frequency resource of PDCCH/PDSCH (e.g., carrier, PRB, subPRB or subcarrier configuration/allocation) , TBS or maximum TBS of PDSCH. And resource offset or repetition factor for PUCCH/PUSCH carrying ACK/NACK information.
  • timer/time window for response e.g., length of timer/time window and/or start time of timer/time window
  • contention resolution timer e.g., length of timer
  • number of repetitions of PDCCH e.g., search space for PDCCH (e.g., starting time and offset of search space)
  • the BS may configure at least one of: periodicity, start time, offset of the PUSCH occasion/resource, time interval between PUSCH occasions/resources, or number of PUSCH occasion/resource in time domain per unit of time resource.
  • the BS may configure at least one of: start frequency and/or offset of the PUSCH occasion/resource, frequency interval between PUSCH occasion/resource, or number of PUSCH occasion/resource in frequency domain.
  • the BS may configure at least one of: number of DMRS sequence/parameter/port, or list of DMRS sequence/parameter/port, or number of code sequence/parameter, or length of code sequence/parameter, or list of code sequence/parameter.
  • the parameter may comprise cyclic shift value/number/interval.
  • the grouping related information may be indicated, e.g., criteria, result, or allocation between group and resource/parameter. For another example, which set of resource (time, frequency, code, etc. ) are for contention based PUSCH and which set of resource are for contention free PUSCH may be indicated. For another example, the contention resolution timer information, e.g., length, may be indicated.
  • Condition information for application of direct PUSCH transmission may configure at least one of: an enabling indication, a reference signal received power (RSRP) threshold, a time duration or start time.
  • Direct PUSCH transmission may be performed when certain condition is satisfied, e.g., UE RSRP is larger than/equal to a threshold.
  • the time to access network transmit msg3/msg1 is within a time duration indicated by network (expressed by a time duration after a start time) .
  • UE specific signaling e.g., dedicated RRC or MAC CE.
  • random access may be performed in a connected mode, e.g., handover.
  • the network may configure at least one parameter, while at least one other parameter may be determined according to the at least one parameter configured by network as well as a predefined table or selection of UE.
  • network may configure the maximum TBS and MCS index.
  • the actual TBS may be selected by UE, e.g., in a table according to maximum TBS as shown in Table 1 assuming X ⁇ Y ⁇ Z.
  • the resource unit may be determined by the MCS index configured by network and TBS selected by UE via a predefined table, e.g., as shown in Table 2.
  • multiple different configurations may be indicated by the BS.
  • two set of PUSCH occasions/resources may be configured with different TBS, e.g., as shown in FIG. 5 (time multiplexed in this example) .
  • the UE may use different PUSCH occasions/resources based on BS configuration or UE selection. For example, when the UE transmits data or NAS layer information in the PUSCH, the UE may select the PUSCH occasion configured with larger TBS. When the UE aims to access the network, the UE may select the PUSCH occasion with small TBS.
  • the RACH occasion can be mapped to a synchronization signal block (SSB) .
  • SSB synchronization signal block
  • the network may be able to identify the beam for the UE.
  • the mapping between PUSCH occasion and synchronization signal may be performed. Following examples may be considered.
  • a BS may broadcast the mapping relationship between PUSCH occasion and synchronization signal (e.g., number of PUSCH occasions per SSB, or number of SSBs per PUSCH occasion) .
  • a BS may broadcast the mapping relationship between PUSCH occasion and RACH occasion (e.g., number of PUSCH occasions per RACH occasion, or number of RACH occasions per PUSCH occasion, frequency offset between PUSCH occasion/resource and RACH occasion, time offset between PUSCH occasion/resource and RACH occasion) .
  • RACH occasion e.g., number of PUSCH occasions per RACH occasion, or number of RACH occasions per PUSCH occasion, frequency offset between PUSCH occasion/resource and RACH occasion, time offset between PUSCH occasion/resource and RACH occasion
  • a BS may configure related RACH occasion and PUSCH occasion/resource via legacy configurations (e.g., 2-step RACH configurations) .
  • a UE may omit the transmission of PRACH (in RACH occasion) and directly transmit PUSCH (in PUSCH occasion) .
  • the first PUSCH transmission (e, g., msg3) can correspond to TC-RNTI indicated in msg2 from the BS. While in direct PUSCH transmission, due to absence of msg2, the UE may not be able to obtain TC-RNTI in msg2 before sending PUSCH. Therefore, the RNTI used during random access may need to be updated.
  • New RNTI introduced for direct PUSCH transmission may be used when UE sending the PUSCH.
  • the RNTI may be calculated based on at least one of the time information (e.g., frame/subframe/slot index) of the PUSCH occasion/resource, frequency information (e.g., PRB/subcarrier/carrier index) of the PUSCH occasion/resource, and code information (e.g., code index/sequence/parameter) .
  • the code information may comprise the covering code of PUSCH or the cyclic shift of DMRS.
  • the new RNTI may be used to scramble at least one of: the PUSCH transmission in the PUSCH occasion/resource, the retransmission of the PUSCH, the PDCCH scheduling retransmission of the PUSCH, and/or the PDCCH response to direct PUSCH transmission.
  • the BS may indicate C-RNTI in response to PUSCH (e.g., in response PDSCH) .
  • the UE may monitor PDCCH response to PUSCH using the new RNTI introduced in above bullet (1) .
  • C-RNTI when C-RNTI is reported in PUSCH (e.g., C-RNTI MAC CE) , it may be directly used as C-RNTI.
  • BS may not indicate C-RNTI in response to PUSCH.
  • UE may monitor PDCCH response to PUSCH using the C-RNTI. This case may happen in RRC connected mode or when RRC connection suspended.
  • RRCConnectionRelease When RRCConnectionRelease is indicated, the UE may drop C-RNTI.
  • UE may report UE ID in next direct PUSCH transmission.
  • response to PUSCH may comprise the response PDCCH and/or the response PDSCH.
  • the response PDCCH may carry the response information itself or schedule a response PDSCH carrying the response information.
  • multiple UEs may select same PUSCH occasion/resource for direct PUSCH transmission.
  • the PUSCH occasion/resource can be shared via contention based or contention free solutions.
  • the BS may configure multiple DMRS parameters/ports (PUSCH cyclic shift) , e.g., in SIB.
  • BS may distinguish different transmissions via detected DMRS sequence or cyclic shift.
  • code e.g., OCC
  • the BS may configure code with length of N, e.g., via SIB/MIB broadcast.
  • UE may randomly select one code sequence and apply on the PUSCH transmission (e.g., across symbols, slots, or repetitions) .
  • the code sequence may be associated with DMRS parameters, e.g., each code sequence is associated with one PUSCH cyclic shift for direct PUSCH transmission.
  • the BS may distinguish different transmissions via detected DMRS sequence or code sequence.
  • the DMRS sequence/parameter/port or code sequence/parameter may be indicated in the response to the PUSCH transmission. Contention resolution may be thought successful if the indicated DMRS sequence/parameter/port or code sequence/parameter matches that used by the UE.
  • the more code sequences or DMRS parameters/ports the more UEs can be multiplexed in same PUSCH occasion/resource. Since different cyclic shifts of DMRS can be used to distinguish different UEs, more cyclic shifts are expected. However, more cyclic shifts means smaller interval between different cyclic shift. And interval between different cyclic shift should be large enough to handle the channel delay/Doppler spread. Therefore, multiple DMRS parameter/port configurations may be indicated for different PUSCH occasion/resource. UEs with low mobility can use the PUSCH occasion/resource configured with larger number of DMRS cyclic shifts or smaller cyclic shift interval. While UEs with high mobility can use the PUSCH occasion/resource configured with smaller number of DMRS cyclic shifts or larger cyclic shift interval.
  • the UE may randomly select one PUSCH occasion/resource (may include time, frequency, code, DMRS, etc. ) for PUSCH transmission. Since multiple UEs may select same resource, the PUSCH transmission may be contention based and BS may need to resolve the contention.
  • PUSCH occasion/resource may include time, frequency, code, DMRS, etc.
  • the contention resolution timer may start or restart when the PUSCH transmission or retransmission is performed.
  • the contention resolution timer is stopped when contention resolution is successful or failed (e.g., as illustrated in part below) .
  • contention resolution timer is expired, the contention resolution may be thought failed.
  • Different contention resolution timer length may be configured for different PUSCH occasion/resource configuration (e.g., longer timer length for PUSCH with larger TBS) .
  • the BS may configure multiple PUSCH occasions/resources, where part of them are for contention based PUSCH transmission while the other part are for contention free PUSCH transmission. For example, there are totally N orthogonal code sequences, where M are allocated for contention based PUSCH, while other N-M are allocated for contention free PUSCH, e.g., as shown in FIG. 6.
  • the contention free resource can be used by UE only if the direct PUSCH transmission is triggered by an indication by BS, e.g., PDCCH order. While the contention based resource can be selected by UE when contention based transmission is performed, e.g., direct PUSCH transmission is triggered by MAC/RRC sublayer (of UE) , etc.
  • the direct PUSCH transmission can be applied only if the TA is accurate enough. Moreover, since contention based PUSCH transmission may be performed, the channel may need to be good enough to make it possible to decode PUSCH when collision happens. Therefore, the conditions to use direct PUSCH transmission may need to be defined. For example, at least one of followings may be considered.
  • RSRP can be larger than/equal to a threshold.
  • the RSRP may be DL RSRP measured by UE.
  • the threshold may be configured by the BS.
  • multiple RSRP thresholds may be defined for different types of PUSCH occasion/resource.
  • Parameters for UL pre-compensation can be valid (or within the validity duration of the parameters need for UL pre-compensation) .
  • the parameters needed for UL synchronization may comprise at least one of: ephemeris, common TA parameters, or GNSS position.
  • (3) UE may have valid TA. For example, random access is performed when timing alignment timer is running.
  • the timing alignment timer for direct PUSCH transmission may be different from that for connected mode.
  • the timing alignment timer is start/restart when TA command is received or TA is updated.
  • the BS may indicate a time duration (e.g., the time when BS know the channel well) during which direct PUSCH transmission can be performed.
  • the BS may indicate the duration length.
  • the BS may indicate the reference time, e.g., start time, of the time duration.
  • the BS may indicates that direct PUSCH transmission is applicable.
  • a higher layer parameter is defined to control the enabling/disabling of direct PUSCH transmission.
  • direct PUSCH transmission is applicable.
  • the parameter is configured as disabled or not present, direct PUSCH transmission is not applicable.
  • the BS may indicate a flag on the applicability. When the flag is present, the UE can perform the direct PUSCH transmission. Otherwise, UE cannot perform the direct PUSCH transmission.
  • above information may be broadcast via SIB/MIB, e.g., RSRP threshold, time duration, etc.
  • the information may configured through dedicated RRC signaling or MAC CE, e.g., time alignment timer length, etc.
  • the above solutions may be implemented per PUSCH occasion/resource configuration.
  • multiple RSRP thresholds may be indicated.
  • the BS may have respective indication on whether direct PUSCH transmission is applicable for each PUSCH occasion/resource configuration.
  • the msg3 in a random access procedure may be carried in such PUSCH transmission, for example, RRC connection request (RRCConnectionRequest/RRCSetupRequest) , RRC resume request (RRCResumeRequest/RRCR esumeR equest1) , RRC reestablishment request (RRCReestablishmentRequest) , system information request (RRCSystemInfoRequest) , RRC reconfiguration complete indication (RRCReconfigurationComplete) , early data request (RRCEarlyDataRequest) .
  • RRC connection request RRCConnectionRequest/RRCSetupRequest
  • RRC resume request RRCResumeRequest/RRCR esumeR equest1
  • RRC reestablishment request RRCReestablishmentRequest
  • system information request RRCSystemInfoRequest
  • RRC reconfiguration Complete indication RRCReconfigurationComplete
  • early data request RRCEarlyDataRequest
  • the msg3 may carry common control channel (CCCH) SDU which may include at least one of the UE ID (e.g., UE contention resolution identity, may be obtained by N bits of temporary mobile subscriber identity (TMSI) , or N bits of random value) , cell RNTI (C-RNTI) MAC CE, DL channel quality information, scheduling request, or establishment cause.
  • CCCH common control channel
  • UE ID e.g., UE contention resolution identity, may be obtained by N bits of temporary mobile subscriber identity (TMSI) , or N bits of random value
  • C-RNTI cell RNTI
  • data or NAS layer information may also be carried in the PUSCH transmission.
  • the content to be carried in direct PUSCH may be different for different configuration of PUSCH occasion/resource.
  • the PUSCH may only contain the information for access (e.g., CCCH SDU, C-RNTI MAC CE, etc) for certain configurations of direct PUSCH transmission, e.g., when MCS/TBS is within certain range or smaller than/equal to a threshold or TBS is not configured.
  • the PUSCH may further contain data or NAS layer information for other configurations of direct PUSCH transmission, e.g., when MCS/TBS is out of the range above or larger than/equal to the threshold or TBS is configured.
  • the UE may apply different PUSCH occasion/resource configuration in different scenarios when multiple configurations are indicated.
  • One of followings can be applied.
  • RSRP thresholds are configured. Different configuration of PUSCH occasion/resource can be used according to RSRP. For example, when RSRP is larger than the largest threshold, the PUSCH occasion/resource configuration with highest MCS/TBS can be used (as well as the PUSCH occasion/resource with lower MCS/TBS) . When RSRP is larger than the second largest threshold but smaller than the largest threshold, the PUSCH occasion/resource configuration with second highest MCS/TBS can be used (as well as the PUSCH occasion/resource with lower MCS/TBS) , and so on. When RSRP is smaller than the lowest threshold, direct PUSCH transmission may not be allowed and UE may fallback to a RACH.
  • the UE may select PUSCH occasion/resource with TBS equal to or larger than the PUSCH/payload size.
  • a buffer e.g., msg3 buffer
  • the UE may select PUSCH occasion/resource with TBS equal to or larger than buffer size or MAC PDU size in the buffer.
  • the contention is resolved after transmission of msg3.
  • the BS may send msg4 to UE.
  • the msg4 may refer to the message/PDSCH carrying UE ID MAC CE and/or PDCCH addressed to temporary C-RNTI (TC-RNTI) scheduling the message/PDSCH.
  • the UE may determine the contention resolution successful when the received UE ID matches the reported UE ID.
  • the temporary C-RNTI (TC-RNTI) can be updated as C-RNTI.
  • the UE may determine the contention resolution successful when (1) the Random Access procedure was initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant for a new transmission; or (2) the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is addressed to the C-RNTI.
  • the response to PUSCH may contain the information about contention resolution, e.g., a UE ID.
  • contention resolution e.g., a UE ID.
  • the UE cannot directly update TC-RNTI to C-RNTI after contention resolution.
  • the information to be carried in response may be different. Following examples can be considered for response to PUSCH.
  • the contention resolution may be considered successful when UE receive a PDCCH transmission addressed to the C-RNTI.
  • the PDCCH may schedule a PDSCH.
  • the PDSCH may contain NAS layer information or early data complete indication.
  • the PDCCH may not schedule a PDSCH.
  • the PDCCH may contain a L1 ACK information.
  • the L1 ACK may indicate the complete of direct PUSCH transmission procedure.
  • the contention resolution may be considered successful when the UE receive a PDCCH transmission addressed to the C-RNTI and/or the PDCCH contains an UL grant for new transmission.
  • the PDCCH may schedule a PDSCH.
  • the PDSCH may contain NAS layer information or early data complete indication.
  • the PDCCH may not schedule a PDSCH.
  • the PDCCH may contain a L1 ACK information. The L1 ACK may indicate the complete of direct PUSCH transmission procedure.
  • the contention resolution may be considered successful when UE ID matches with that indicated in response PDCCH/PDSCH/message. Or contention resolution may be thought successful if DMRS sequence/parameter/port or code sequence/parameter matches with that indicated in response PDCCH/PDSCH/message.
  • the PDCCH can be addressed to the new RNTI used for PUSCH transmission.
  • the PDCCH may schedule a PDSCH.
  • the PDSCH may include at least one of: UE ID (may be reported in PUSCH) , C-RNTI, DMRS index/sequence/parameter/port, or code index/sequence/parameter.
  • the PDSCH may contain NAS layer information or early data complete indication.
  • the PDCCH may not schedule a PDSCH.
  • the PDCCH may contain a L1 ACK information.
  • the L1 ACK may indicate the complete of direct PUSCH transmission procedure.
  • the L1 ACK may indicate at least one of: the UE ID, a C-RNTI, a DMRS parameter, a code parameter.
  • the C-RNTI indicated in response PDCCH/PDSCH/message can be used as C-RNTI for following communication.
  • RRC connection setup may be carried in the PDSCH scheduled by PDCCH response to PUSCH.
  • the PDSCH may include non-access stratum (NAS) layer information or early data complete indication when early data request is sent in the PUSCH, or when the PUSCH carry NAS layer information, or when MCS/TBS is larger than a threshold, or TBS is configured for PUSCH.
  • Early data complete indication may indicate extended wait time for delay tolerant service.
  • the response information may be carried in group based indication.
  • the new RNTI mentioned in implementation example-2 may be group based on RNTI, for example.
  • the new RNTI can be calculated based on time information only.
  • the UEs using PUSCH occasions with same time information can share same RNTI (even if the frequency information, code information are different) .
  • the new RNTI is calculated based on time information and code information.
  • the UEs using PUSCH occasions with same time and code information can share same RNTI (even if the frequency information are different) .
  • the new RNTI can be calculated based on time information and frequency information.
  • the response PDCCH addressed to the new RNTI may be a group PDCCH.
  • the PDCCH may indicate layer one (L1) ACK common to all UEs with the new RNTI, or respective L1 ACK for each UE with the new RNTI.
  • the respective L1 ACK may be indicated in certain order, example, with increasing order of code sequence and/or frequency.
  • the PDCCH may schedule PDSCH.
  • the PDSCH may include respective response information for each UE, e.g., a UE ID (may be reported in PUSCH) , a C-RNTI, a DMRS index/sequence/parameter/port, a code index/sequence/parameter, or NAS layer information.
  • FIG. 7 illustrates a flow diagram of a method 700 for random access with reduced signaling.
  • the method 700 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGS. 1 to 6.
  • the method 700 may be performed by a UE, in some embodiments. Additional, fewer, or different operations may be performed in the method 700 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.
  • a wireless communication device may send an uplink transmission to access a network to a network node.
  • the uplink transmission is physical uplink shared channel (PUSCH) transmission.
  • send an uplink transmission to access a network means a wireless communication device send a PUSCH as a first step in random access procedure.
  • the wireless communication device may receive a response to the uplink transmission from the network node.
  • the wireless communication device may receive at least one configuration for the uplink transmission from the network node.
  • the configuration can be received in at least one of: a master information block (MIB) broadcast, a system information block (SIB) broadcast, a multicast, a dedicated radio resource control (RRC) signaling, a media access control control element (MAC CE) signaling, or a downlink control information (DCI) signaling.
  • MIB master information block
  • SIB system information block
  • RRC dedicated radio resource control
  • MAC CE media access control control element
  • DCI downlink control information
  • the configuration for the uplink transmission may comprise at least one of: grant information of the uplink transmission; response configuration to the uplink transmission; time information of at least one resource of the uplink transmission; frequency information of at least one resource of the uplink transmission; contention-related information of the uplink transmission; condition information for performing the uplink transmission; a mapping relationship between the at least one resource for the uplink transmission and a synchronization signal; or a mapping relationship between the at least one resource for the uplink transmission and a random access channel (RACH) occasion.
  • the time-domain resource comprise the start subframe/slot/symbol and/or length of time resource, e.g., number of consecutive subrames/slots/symbols.
  • the frequency-domain resource comprise the start subcarrier/physical resource block (PRB) and/or width of frequency band, e.g., number of consecutive subcarriers/PRBs.
  • the DMRS parameter may comprise a DMRS type, additional DMRS configuration, or a cyclic shift.
  • the grant information may comprise at least one of a Modulation and Coding Scheme (MCS) , a Transport Block Size (TBS) , a maximum TBS, whether a TBS less than the indicated TBS is allowed, whether a subset of potential TBSs is allowed, a time-domain resource, a frequency-domain resource, a number of repetitions, power allocation, hopping configuration, Demodulation Reference Signal (DMRS) parameter, or carrier configuration.
  • MCS Modulation and Coding Scheme
  • TBS Transport Block Size
  • a maximum TBS whether a TBS less than the indicated TBS is allowed, whether a subset of potential TBSs is allowed, a time-domain resource, a frequency-domain resource, a number of repetitions, power allocation, hopping configuration, Demodulation Reference Signal (DMRS) parameter, or carrier configuration.
  • MCS Modulation and Coding Scheme
  • TBS Transport Block Size
  • DMRS Demodulation Reference Signal
  • the response configuration may comprise at least one of a timer or time window, a contention resolution timer, a number of repetitions, search space, frequency hopping, frequency-domain resource, a Transport Block Size (TBS) , a maximum TBS, resource offset of feedback of the response, or repetition factor of the feedback.
  • the time information may comprise at least one of a periodicity, start time, offset, time interval between two uplink resources of the at least one uplink resource, number of the at least one uplink resources in a time domain per unit of the at least one time resource.
  • the frequency information may comprise at least one of a start frequency, offset, frequency interval between two uplink resources of the at least one uplink resource, number of the at least one uplink resources in a frequency domain.
  • the contention-related information may comprise at least one of: a number of Demodulation Reference Signal (DMRS) sequences, parameters, or ports; a list of DMRS sequences, parameters, or port; a number of code sequences or parameters; a length of a code sequence or a parameter; or a list of code sequences or parameters.
  • DMRS Demodulation Reference Signal
  • condition information may comprise at least one of an enabling indication, signal strength threshold, time duration, start time.
  • a Radio Network Temporary Identifier (RNTI) for the uplink transmission can be determined according to at least one of time information of the uplink transmission, frequency information of the uplink transmission, or code information of the uplink transmission.
  • the RNTI of the uplink transmission can be used to scramble at least one of the uplink transmission, a retransmission of the uplink transmission, a downlink control channel scheduling the retransmission of the uplink transmission, and a downlink control channel response of the uplink transmission.
  • a resource of the UL transmission can be used by a plurality of wireless communication devices.
  • the contention resolution timer may start or restart in response to performing the uplink transmission. Different lengths of contention resolution timer can be configured for different uplink transmission configurations.
  • the wireless communication device may receive an order to send the uplink transmission from the network node.
  • the order may comprise at least one of: a Demodulation Reference Signal (DMRS) sequence, parameter, or port; or a code sequence or parameter.
  • DMRS Demodulation Reference Signal
  • the wireless communication device may use the at least one of the DMRS sequence, parameter or port, or the code sequence or parameter in the uplink transmission.
  • the network node may configure a plurality of resources for uplink transmissions of a plurality of wireless communication devices.
  • the plurality of resources may comprise contention-based resources and contention-free resources.
  • the wireless communication device may use one of the contention-free resources to transmit the uplink transmission in response to receiving an indication from the network node; and the wireless communication device may use one of the contention-based resources to transmit the uplink transmission, wherein transmission of the uplink transmission is in response to receiving an indication trigger by a Media Access Control (MAC) or Radio Resource Control (RRC) sublayer from the network node.
  • MAC Media Access Control
  • RRC Radio Resource Control
  • the contention-based resources or the contention-free resources can be resources with different set of code sequences, time resources, or frequency resources.
  • the uplink transmission can be sent in response to at least one of: a signal quality at the wireless communication device is greater than or equal to a threshold; a parameter for uplink pre-compensation is valid; a Timing Advance (TA) is currently valid; time at which the uplink transmission is sent is within a duration configured by the network node; receiving from the network node an enabling indication.
  • a signal quality at the wireless communication device is greater than or equal to a threshold
  • a parameter for uplink pre-compensation is valid
  • a Timing Advance (TA) is currently valid
  • time at which the uplink transmission is sent is within a duration configured by the network node
  • receiving from the network node an enabling indication a signal quality at the wireless communication device is greater than or equal to a threshold.
  • TA Timing Advance
  • the uplink transmission may carry msg3 for the RACH process.
  • the uplink transmission may include at least one of a Radio Resource Control (RRC) connection request, an RRC resume request, an RRC reestablishment request, a system information request, an RRC reconfiguration complete indication, an early data request, a Common Control Channel (CCCH) Service Data Unit (SDU) , a MAC CE, or Non-Access Stratum (NAS) layer information.
  • RRC Radio Resource Control
  • the wireless communication device may apply a first configuration of a set of configurations for the uplink transmission based on signal quality (e.g., reference signal received power (RSRP) ) .
  • the wireless communication device may apply a second configuration of the set of configurations for the uplink transmission based on a size of the uplink transmission.
  • RSRP reference signal received power
  • the response is received via at least one of a PDCCH or a PDSCH.
  • the response may comprise at least one of a Radio Resource Control (RRC) connection setup request, Non-Access Stratum (NAS) layer information, early data complete indication, a cell RNTI (C-RNTI) , an identifier (ID) of the wireless communication device, a Demodulation Reference Signal (DMRS) parameter, or a code parameter.
  • RRC Radio Resource Control
  • NAS Non-Access Stratum
  • ID cell RNTI
  • ID identifier
  • DMRS Demodulation Reference Signal
  • the wireless communication device may consider that contention resolution successful in response to at least one of: the response comprising the ID of the wireless communication device; the DMRS parameter in the response is same as that in the uplink transmission; or the code parameter in the response is same as that in the uplink transmission.
  • the response can be in a group-based indication based on a Radio Network Temporary Identifier (RNTI) .
  • the RNTI can be determined based on time information.
  • the RNTI can be determined based on time information and code information.
  • the RNTI can be determined based on time information and frequency information.
  • the RNTI can be determined based on time information and code information.
  • the response may comprise a group downlink control channel sent to a plurality of wireless communication devices comprising the wireless communication device.
  • the group downlink control channel may indicate an Acknowledgement (ACK) common to the plurality of wireless communication devices having a same Radio Network Temporary Identifier (RNTI) ; the group downlink control channel schedules a downlink transmission, the downlink transmission comprises response information for each of the plurality of wireless communication devices.
  • ACK Acknowledgement
  • RNTI Radio Network Temporary Identifier
  • a network node may receive an uplink transmission to access a network from a wireless communication device.
  • the network node may send a response to the uplink transmission to the wireless communication device.
  • the network node may send at least one configuration for the uplink transmission to the wireless communication device.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
  • firmware e.g., a digital implementation, an analog implementation, or a combination of the two
  • firmware various forms of program or design code incorporating instructions
  • software or a “software module”
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can 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.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés d'accès aléatoire à signalisation réduite. Un dispositif de communication sans fil peut envoyer une transmission en liaison montante pour accéder à un réseau à un nœud de réseau.
PCT/CN2024/076480 2024-02-06 2024-02-06 Systèmes et procédés d'accès aléatoire à signalisation réduite Pending WO2025166597A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076480 WO2025166597A1 (fr) 2024-02-06 2024-02-06 Systèmes et procédés d'accès aléatoire à signalisation réduite

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076480 WO2025166597A1 (fr) 2024-02-06 2024-02-06 Systèmes et procédés d'accès aléatoire à signalisation réduite

Publications (1)

Publication Number Publication Date
WO2025166597A1 true WO2025166597A1 (fr) 2025-08-14

Family

ID=96698719

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/076480 Pending WO2025166597A1 (fr) 2024-02-06 2024-02-06 Systèmes et procédés d'accès aléatoire à signalisation réduite

Country Status (1)

Country Link
WO (1) WO2025166597A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200083928A (ko) * 2018-12-29 2020-07-09 삼성전자주식회사 무선 통신 시스템에서 신호를 전송하는 방법 및 장치
US20200351931A1 (en) * 2019-05-02 2020-11-05 Alireza Babaei Resource Conflict
CN113303021A (zh) * 2019-01-04 2021-08-24 欧芬诺有限责任公司 未经许可频带中的两步随机接入程序
CN114208380A (zh) * 2019-08-16 2022-03-18 高通股份有限公司 用于两步rach中rach响应消息的harq过程

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200083928A (ko) * 2018-12-29 2020-07-09 삼성전자주식회사 무선 통신 시스템에서 신호를 전송하는 방법 및 장치
CN113303021A (zh) * 2019-01-04 2021-08-24 欧芬诺有限责任公司 未经许可频带中的两步随机接入程序
US20200351931A1 (en) * 2019-05-02 2020-11-05 Alireza Babaei Resource Conflict
CN114208380A (zh) * 2019-08-16 2022-03-18 高通股份有限公司 用于两步rach中rach响应消息的harq过程

Similar Documents

Publication Publication Date Title
US11596001B2 (en) Method and apparatus for performing multiple RACH procedures
JP7262034B2 (ja) リソース取得手順
US20230018487A1 (en) Random access procedure for latency reduction
US10425973B2 (en) Random access channel signaling on a shared communication medium
CN107810616B (zh) 发送上行链路信道的方法和nb-iot设备
CN102271418B (zh) 一种随机接入的方法及装置
KR20200120535A (ko) 사이드링크 harq 피드백 제어하는 방법 및 그 장치
CN119997254A (zh) 用于支持大随机接入响应（rar）窗口大小的随机接入过程的方法
CN112335323A (zh) 上行控制数据传输涉及的用户设备和基站
CN111226473A (zh) 新无线电非授权频谱中随机接入信道的对话前监听和信道接入优先级等级
KR20130083708A (ko) 무선 통신 시스템에서 랜덤 액세스의 수행장치 및 방법
US12075371B2 (en) Method and apparatus for data transmission on common resources
WO2025166597A1 (fr) Systèmes et procédés d'accès aléatoire à signalisation réduite
US20250038892A1 (en) Systems and methods for coverage enhancement in non terrestrial network
CN118542063B (zh) 用于无线通信的方法、终端设备及网络设备
US12452887B2 (en) Random access channel (RACH) coverage enhancement
US20240357659A1 (en) Systems and methods for enhanced random access procedure
US20240397552A1 (en) Systems and methods for enhanced random access procedure

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24922840

Country of ref document: EP

Kind code of ref document: A1