WO2022083705A1 - Équipement utilisateur et procédé de gestion de synchronisation de transmission - Google Patents

Équipement utilisateur et procédé de gestion de synchronisation de transmission Download PDF

Info

Publication number
WO2022083705A1
WO2022083705A1 PCT/CN2021/125417 CN2021125417W WO2022083705A1 WO 2022083705 A1 WO2022083705 A1 WO 2022083705A1 CN 2021125417 W CN2021125417 W CN 2021125417W WO 2022083705 A1 WO2022083705 A1 WO 2022083705A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
offset
timing
value
prach
Prior art date
Application number
PCT/CN2021/125417
Other languages
English (en)
Inventor
Chienchun CHENG
Chiahao YU
Hungchen CHEN
Hsinhsi TSAI
Original Assignee
FG Innovation Company Limited
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 FG Innovation Company Limited filed Critical FG Innovation Company Limited
Publication of WO2022083705A1 publication Critical patent/WO2022083705A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18563—Arrangements for interconnecting multiple systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • 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 present disclosure is related to wireless communication, and specifically, to a method for handling transmission timing in cellular wireless communication networks.
  • E-UTRA Evolved Universal Terrestrial Radio Access (Network)
  • SIB1 System Information Block Type One
  • the 5G NR system is designed to provide flexibility and configurability to optimize the network services and types, accommodating various use cases, such as eMBB, mMTC, and URLLC.
  • eMBB evolved mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable and low-latency communications
  • the present disclosure is related to a method for handling transmission timing performed by a UE.
  • a method for handling transmission timing performed by a UE includes receiving, from a BS, a first timing offset used in NTN; receiving, from the BS, a response message in an RA procedure; obtaining, according to the first timing offset, a first scheduling offset between the reception of the response message and a transmission of an HARQ-ACK feedback in response to the response message; and transmitting, to the BS, the HARQ-ACK feedback according to the first scheduling offset.
  • the response message comprises a success RAR indicating a second timing offset for the HARQ-ACK feedback used in TN; and the first scheduling offset depends on a sum of the second timing offset, a processing time for a PUSCH transmission, and the first timing offset.
  • the response message is an MsgB of a 2-step RA procedure.
  • the method further includes receiving, from the BS, DCI indicating a third timing offset for the HARQ-ACK feedback used in TN, wherein the first scheduling offset depends on a sum of the third timing offset and the first timing offset.
  • the response message is an Msg4 of a 4-step RA procedure.
  • the method further includes starting an MsgB-RAR window according to a second scheduling offset; receiving, from the BS, a fallback RAR within the MsgB-RAR window, the fallback RAR indicating a value for a TA correction; obtaining, according to the first timing offset, a third scheduling offset between the reception of the fallback RAR and a transmission of an Msg3 in response to the fallback RAR; and transmitting, to the BS, the Msg3 according to the third scheduling offset.
  • the method further includes obtaining a fourth scheduling offset between the transmission of the Msg3 and a start of an RA-CR window by adding the value with the second scheduling offset; and starting the RA-CR window according to the fourth scheduling offset, wherein the DCI and the response message are received within the RA-CR window.
  • the first timing offset is received via SI.
  • the first timing offset is received via RRC signaling.
  • the first timing offset is in terms of slots.
  • the first timing offset is a cell specific value.
  • the first timing offset is a UE specific value.
  • a UE for handling transmission timing includes a processor; and a memory coupled to the processor, wherein the memory stores a computer-executable program that when executed by the processor, causes the UE to receive, from a BS, a first timing offset used in NTN; receive, from the BS, a response message in an RA procedure; obtain, according to the first timing offset, a first scheduling offset between the reception of the response message and a transmission of an HARQ-ACK feedback in response to the response message; and transmit, to the BS, the HARQ-ACK feedback according to the first scheduling offset.
  • FIG. 1 illustrates an NTN network with an LEO satellite of transparent payload according to an example implementation of the present disclosure.
  • FIG. 2 illustrates a timing diagram when a minimum RTT and a maximum differential RTT are applied in NTN according to an example implementation of the present disclosure.
  • FIG. 3 illustrates a timing diagram regarding a start point of a RAR window when an initial TA is applied for PRACH transmission in NTN according to an example implementation of the present disclosure.
  • FIG. 4 illustrates a timing diagram regarding PRACH retransmission when an initial TA is applied in NTN according to an example implementation of the present disclosure.
  • FIG. 5 illustrates a timing diagram when a start point of an MsgB-RAR window is based on a PO according to an example implementation of the present disclosure.
  • FIG. 6 illustrates a timing diagram when a start point of an MsgB-RAR window is based on a RO according to an example implementation of the present disclosure.
  • FIG. 7 illustrates a timing diagram when a fallbackRAR is received within an MsgB-RAR window according to an example implementation of the present disclosure.
  • FIG. 8 illustrates a timing diagram when a successRAR is received within an MsgB-RAR window according to an example implementation of the present disclosure.
  • FIG. 9 illustrates a timing diagram when MsgA includes a C-RNTI MAC CE according to an example implementation of the present disclosure.
  • FIG. 10 illustrates a timing diagram regarding MsgA retransmission with PRACH retransmission and PUSCH retransmission according to an example implementation of the present disclosure.
  • FIG. 11 illustrates a timing diagram regarding a TA and UE processing time requirement according to an example implementation of the present disclosure.
  • FIG. 12 illustrates a timing diagram regarding UL and DL timing alignment at a satellite according to an example implementation of the present disclosure.
  • FIG. 13 illustrates a timing diagram regarding a start of an RAR window according to an example implementation of the present disclosure.
  • FIG. 14 illustrates a timing diagram regarding a start of an MsgB-RAR window according to an example implementation of the present disclosure.
  • FIG. 15 illustrates a timing diagram regarding HARQ-ACK transmission when a fallbackRAR is received within an RA-CR window according to an example implementation of the present disclosure.
  • FIG. 16 illustrates a timing diagram regarding HARQ-ACK transmission when a successRAR is received within an MsgB-RAR window according to an example implementation of the present disclosure.
  • FIG. 17 illustrates a schematic diagram regarding uncertainty of UE autonomous TA estimation according to an example implementation of the present disclosure.
  • FIG. 18 illustrates a schematic diagram regarding a TA margin based on standard deviation for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • FIG. 19 illustrates a schematic diagram regarding a TA margin based on CP for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • FIG. 20 illustrates a schematic diagram regarding a TA margin based on a maximum TA for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • FIG. 21 illustrates a method for handling transmission timing performed by a UE according to an example implementation of the present disclosure.
  • FIG. 22 is a block diagram illustrating a node for wireless communication according to an example implementation of the present disclosure.
  • the phrases “in one implementation, ” or “in some implementations, ” may each refer to one or more of the same or different implementations.
  • the term “coupled” is defined as connected whether directly or indirectly via intervening components and is not necessarily limited to physical connections.
  • the term “comprising” means “including, but not necessarily limited to” and specifically indicates open-ended inclusion or membership in the disclosed combination, group, series or equivalent.
  • the expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C. ”
  • system and “network” may be used interchangeably.
  • the term “and/or” is only an association relationship for disclosing associated objects and represents that three relationships may exist such that A and/or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. “A and/or B and/or C” may represent that at least one of A, B, and C exists.
  • the character “/” generally represents that the associated objects are in an “or” relationship.
  • any disclosed network function (s) or algorithm (s) may be implemented by hardware, software or a combination of software and hardware.
  • Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.
  • a software implementation may include computer-executable instructions stored on a computer-readable medium such as memory or other types of storage devices.
  • a computer-readable medium such as memory or other types of storage devices.
  • One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding executable instructions and perform the disclosed network function (s) or algorithm (s) .
  • the microprocessors or general-purpose computers may include Applications Specific Integrated Circuitry (ASIC) , programmable logic arrays, and/or using one or more Digital Signal Processors (DSPs) .
  • ASIC Applications Specific Integrated Circuitry
  • DSP Digital Signal Processors
  • the computer-readable medium may include, but is not limited to, Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM) , Electrically Erasable Programmable Read-Only Memory (EEPROM) , flash memory, Compact Disc Read-Only Memory (CD-ROM) , magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • magnetic cassettes magnetic tape
  • magnetic disk storage or any other equivalent medium capable of storing computer-readable instructions.
  • a radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) may typically include at least one Base Station (BS) , at least one UE, and one or more optional network elements that provide connection within a network.
  • the UE may communicate with the network such as a Core Network (CN) , an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , a Next-Generation Core (NGC) , a 5G Core (5GC) , or an internet via a RAN established by one or more BSs.
  • CN Core Network
  • EPC Evolved Packet Core
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NGC Next-Generation Core
  • 5GC 5G Core
  • a UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal.
  • the UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability.
  • PDA Personal Digital Assistant
  • the UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN.
  • the BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX) , Global System for Mobile communications (GSM that is often referred to as 2G) , GSM Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN) , General Packet Radio Service (GPRS) , Universal Mobile Telecommunication System (UMTS that is often referred to as 3G) based on basic Wideband-Code Division Multiple Access (W-CDMA) , High-Speed Packet Access (HSPA) , LTE, LTE-A, evolved/enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G) , and/or LTE-A Pro.
  • RAT Radio Access Technology
  • WiMAX Worldwide Interoperability for Microwave Access
  • GSM Global System for Mobile communications
  • EDGE GSM Enhanced Data rates for GSM Evolution
  • GERAN GSM Enhanced Data
  • the BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in the GSM/GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G RAN (or in the 5G Access Network (5G-AN) ) , or any other apparatus capable of controlling radio communication and managing radio resources within a cell.
  • the BS may serve one or more UEs via a radio interface.
  • the BS may be operable to provide radio coverage to a specific geographical area using a plurality of cells included in the RAN.
  • the BS may support the operations of the cells.
  • Each cell may be operable to provide services to at least one UE within its radio coverage.
  • Each cell may provide services to serve one or more UEs within its radio coverage such that each cell schedules the downlink (DL) and optionally UL resources to at least one UE within its radio coverage for DL and optionally UL packet transmissions.
  • the BS may communicate with one or more UEs in the radio communication system via the plurality of cells.
  • a cell may allocate Sidelink (SL) resources for supporting Proximity Service (ProSe) , LTE SL services, and/or LTE/NR Vehicle-to-Everything (V2X) service. Each cell may have overlapped coverage areas with other cells.
  • SL Sidelink
  • Proximity Service Proximity Service
  • LTE SL services LTE SL services
  • V2X Vehicle-to-Everything
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • SpCell Special Cell
  • a Primary Cell may refer to the SpCell of an MCG.
  • a Primary SCG Cell (PSCell) may refer to the SpCell of an SCG.
  • MCG may refer to a group of serving cells associated with the Master Node (MN) , comprising of the SpCell and optionally one or more Secondary Cells (SCells) .
  • SCG may refer to a group of serving cells associated with the Secondary Node (SN) , comprising of the SpCell and optionally one or more SCells.
  • the frame structure for NR supports flexible configurations for accommodating various next generation (e.g., 5G) communication requirements such as eMBB, mMTC, and URLLC, while fulfilling high reliability, high data rate and low latency requirements.
  • the OFDM technology in the 3GPP may serve as a baseline for an NR waveform.
  • the scalable OFDM numerology such as adaptive sub-carrier spacing, channel bandwidth, and CP may also be used.
  • Two coding schemes are considered for NR, specifically LDPC code and Polar Code.
  • the coding scheme adaption may be configured based on channel conditions and/or service applications.
  • At least DL transmission data, a guard period, and an UL transmission data should be included in a transmission time interval (TTI) of a single NR frame.
  • TTI transmission time interval
  • the respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR.
  • Sidelink resources may also be provided in an NR frame to support ProSe services, V2X services (e.g., E-UTRA V2X sidelink communication services) or sidelink services (e.g., NR sidelink communication services) .
  • sidelink resources may also be provided in an E-UTRA frame to support ProSe services, V2X services (e.g., E-UTRA V2X sidelink communication services) or sidelink services (e.g., NR sidelink communication services) .
  • V2X services e.g., E-UTRA V2X sidelink communication services
  • sidelink services e.g., NR sidelink communication services
  • a cell may be a radio network object that can be uniquely identified by a UE from a (cell) identification that is broadcast over a geographical area from one UTRAN Access Point.
  • the Cell may be either FDD or TDD mode.
  • serving cell For a UE in RRC_CONNECTED not configured with CA or DC, there may be only one serving cell, which may be referred to as a PCell.
  • serving cells For a UE in RRC_CONNECTED configured with CA or DC, the term “serving cells” may be used to denote a set of cells comprising SpCell (s) and all SCells.
  • the serving cell may be a PCell, a PSCell, or an SCell described in the 3GPP TS 38.331.
  • HARQ may be a functionality that ensures delivery between peer entities at Layer 1 (i.e., Physical Layer) .
  • a single HARQ process supports one TB when the physical layer is not configured for DL/UL spatial multiplexing, and a single HARQ process supports one or multiple TBs when the physical layer is configured for DL/UL spatial multiplexing.
  • HARQ information for DL-SCH or for UL-SCH transmissions may include NDI, TBS, RV, and HARQ process ID.
  • a HARQ-ACK information bit value of 0 may represent an NACK while a HARQ-ACK information bit value of 1 may represent a positive ACK.
  • NTN may refer to networks, or segments of networks, using a spaceborne vehicle for transmission, such as at least one of LEO satellites, GNSS satellites and GEO satellites.
  • a spaceborne vehicle for transmission such as at least one of LEO satellites, GNSS satellites and GEO satellites.
  • transparent payload-based LEO scenario addresses at least 3GPP class 3 UE with GNSS capability.
  • a transparent payload-based LEO network may refer to a relay-based NTN.
  • the LEO satellites may simply perform amplify-and-forward in space, and the BS (e.g., gNB) is located on the ground connected to the core network.
  • the orbit of 600 km has been considered in the WI.
  • FIG. 1 illustrates an NTN network 100 with an LEO satellite 130 of transparent payload according to an example implementation of the present disclosure.
  • the NTN network 100 includes a UE 110, a BS 120, the LEO satellite 130 and the earth 140.
  • the LEO satellite 130 may be on an orbit 150 of 600km above the surface of the earth 140.
  • the LEO satellite 130 may act as a relay between the UE 110 and the BS 120.
  • a radio link between the LEO satellite 130 and the BS may be referred to as a feeder link.
  • a radio link between the satellite 130 and the UE 110 may be referred to as a service link.
  • a beam generated by an antenna onboard a satellite may be referred to as a satellite beam.
  • a diameter of the satellite beam may be with a range from 50 km to 1000 km, making impacts on maximum differential delay among UE (s) in service.
  • the satellite beam may be an EMB or an EFB.
  • the structure of the NTN 100 is not limited herein.
  • the NTN network 100 may additionally include a GNSS satellite on an orbit of 20200km above the surface of the earth 140.
  • a 3GPP class 3 UE may refer to Power Class UE 3.
  • the definition is used for the UL TX power level set to be 23dBm with a range of plus and minus 2dB. This setting was mainly driven to ensure backward compatibility with prior technologies (e.g., Rel-15 NR/GSM/UMTS) so that network deployment topologies remain similar.
  • a GNSS may refer to the standard generic term for satellite navigation systems that provide autonomous geo-spatial positioning with global coverage.
  • the GNSS may include, for example, the GPS, GLONASS, Galileo, Beidou, and other regional systems.
  • the GNSS may be operated on an orbit of 20200 km.
  • a K0 value may refer to a timing offset between a DL slot in which a PDCCH for DL scheduling is received and a DL slot in which PDSCH data is scheduled.
  • a K1 value may refer to a timing offset between a DL slot in which data is scheduled on PDSCH and a UL slot in which an ACK/NACK feedback for the scheduled PDSCH data needs to be transmitted.
  • a K2 value may refer to a timing offset between a DL slot in which a PDCCH for UL scheduling is received and a UL slot in which UL data needs to be transmitted on a PUSCH.
  • a TA may refer to a timing offset between UL and DL frames.
  • the UL frames may be transmitted in advance based on the TA value, which may be indicated by the network.
  • the TA may be used to guarantee that UL signals from different UEs may be received at the network side on time without interfering each other.
  • the typical TA value may be set to two times the propagation delay.
  • the TA value matters because the network needs this information to perform UL time scheduling (e.g., UL grants and UL slot offsets) , ensure L1 synchronization (e.g., TAG-specific timer defined in Rel-15 NR) , and enhance mobility (e.g., SMTC measurement gap and conditional HO) .
  • UL time scheduling e.g., UL grants and UL slot offsets
  • L1 synchronization e.g., TAG-specific timer defined in Rel-15 NR
  • enhance mobility e.g., SMTC measurement gap and conditional HO
  • NW, RAN, cell, camped cell, serving cell, base station, gNB, eNB and ng-eNB may be used interchangeably in the present disclosure. In some implementations, some of these terms may refer to the same network entity.
  • SI may refer to MIB, SIB1, and other SI (s) .
  • Minimum SI may include MIB and SIB1.
  • Other SI (s) may refer to SIB3, SIB4, SIB5, and other SIB (s) (e.g., SNPN-specific SIB, PNI-NPN-specific SIB) .
  • An ATG network may be included in the NTN framework and may refer to in-flight connectivity technique, using ground-based cell towers that send signals up to an aircraft’s antenna (s) of onboard ATG terminal. As a plane travels into different sections of airspace, the onboard ATG terminal may be automatically connected to the cell with the strongest received signal power, like a mobile phone on the ground.
  • ATG BS e.g., gNB
  • deployed on the ground and antennas pointing upward may form an aerial cell, while aircraft may perform as a special UE.
  • ATG air interface may refer to the connection between the ATG BS and the aircraft, while the connection between the aircraft and passengers may be based on Wi-Fi technology.
  • the ATG may handle extremely large cell coverage range (e.g., up to 300 km) and high speed (e.g., up to 1200km/h) .
  • RO may be an occasion for an RA preamble transmission provided by, e.g., an RACH-ConfigCommon IE.
  • RACH-ConfigCommon An RACH-ConfigCommon IE may be used to specify cell specific 4-step RA type parameters.
  • the RACH-ConfigCommon IE may include at least one of the following parameters:
  • An rach-ConfigGeneric may be a RACH parameter for regular RA and BFR.
  • An rsrp-ThresholdSSB may be a RSRP threshold for SSBs.
  • the UE may select an SS block and corresponding PRACH resource for path-loss estimation and (re) transmission based on SS blocks that satisfy the rsrp-ThresholdSSB.
  • a ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include a CHOICE field and an ENUMERATED field.
  • the CHOICE field may convey information about a total number of SSBs per RACH occasion. For example, value oneEighth may correspond to one SSB associated with 8 RACH occasions, and value oneFourth may correspond to one SSB associated with 4 RACH occasions.
  • the ENUMERATED field may indicate a total number of Contention Based preambles per SSB. For example, value n4 may correspond to 4 Contention Based preambles per SSB, and value n8 may correspond to 8 Contention Based preambles per SSB.
  • RACH-ConfigGeneric An RACH-ConfigGeneric IE may be used to specify 4-step RA type parameters for regular RA as well as for BFR. This IE may include at least one of the following parameters:
  • An Msg1-FDM may be a total number of PRACH transmission occasions FDMed in one-time instance.
  • a prach-ConfigurationIndex may be a PRACH configuration index and have a value selected from INTEGER (0 . .. 255) .
  • An ra-ResponseWindow may be a time window used to monitor an Msg2 (e.g., RAR) .
  • the ra-ResponseWindow may be in terms of slots.
  • the ra-ResponseWindow may be configured by the network.
  • the ra-ResponseWindow may have a value lower than or equal to 10 ms when the Msg2 is transmitted in licensed spectrum.
  • the ra-ResponseWindow may have a value lower than or equal to 40 ms when the Msg2 is transmitted with shared spectrum channel access.
  • the UE may ignore the ra-ResponseWindow (without suffix) .
  • the UE may ignore the ra-ResponseWindow field if the ra-ResponseWindow field and the ra-ResponseWindow-v1610 are included in SCellConfig.
  • the network may include two LSB bits of an SFN corresponding to a PRACH occasion where a preamble is received in a DCI scheduling MSG2.
  • prach-ConfigurationIndex Table 1 illustrates example RA configurations for FR1 and paired spectrum/supplementary uplink.
  • RA preambles may only be transmitted in the time resources obtained from Table 1 indicated by the prach-ConfigurationIndex.
  • n SFN may stand for a system frame number (e.g., radio frame of the time resources at which PRACH (re) transmission occurs) .
  • x may stand for a PRACH configuration period.
  • y may stand for a system frame number within the PRACH configuration period.
  • RAPID field may identify a transmitted RA preamble.
  • the size of the RAPID field may be 6 bits. If an RAR includes a MAC subPDU with the RAPID only, the UE may consider an RA procedure including the RAR successfully completed.
  • DCI format 1_0 A DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI may transmit at least one of the following information:
  • - LSBs of SFN 2 bits for the DCI format 1_0 with CRC scrambled by MsgB-RNTI or 2 bits for the DCI format 1_0 with CRC scrambled by RA-RNTI for operation in a cell with shared spectrum channel access; 0 bit otherwise.
  • RA-RNTI An RA-RNTI associated with a PRACH occasion in which an RA Preamble is transmitted.
  • the RA-RNTI is computed based on time and frequency indexes of the PRACH occasion determined by the UE.
  • Type1-PDCCH CSS set may be a PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by an RA-RNTI, a MsgB-RNTI, or a TC-RNTI on a primary cell.
  • An ra-SearchSpace field may be an ID of a search space for an RA procedure. If this field is absent, the UE may not receive an RAR in a BWP.
  • a SearchSpace IE may define how and where to search for PDCCH candidates. Each search space may be associated with one CORESET.
  • the SearchSpace IE may include at least one of the following parameters:
  • controlResourceSetId may be used to identify a CORESET applicable for this SearchSpace.
  • a value 0 may identify a common CORESET#0 configured in MIB and in ServingCellConfigCommon. Other values may identify CORESETs configured via SI or dedicated signaling.
  • This IE may have values: sl1 NULL, sl2 INTEGER (0 ... 1) , ..., sl2560 INTEGER (0 ... 2559) used to indicate slots for PDCCH monitoring configured as periodicity and offset.
  • a ControlResourceSet IE may be used to configure a time/frequency CORESET in which to search for DCI.
  • the CORESET may include resource blocks in a frequency domain and ⁇ ⁇ 1, 2, 3 ⁇ symbols in a time domain, given by frequencyDomainResources and duration, respectively.
  • a PREAMBLE_BACKOFF IE may provide a range of backoff time for preamble retransmission.
  • Table 2 illustrates example of backoff parameter values.
  • a PDSCH processing time for PDSCH processing capability 1 may be required PDSCH processing time based on a UE capability category 1. If a scheduled PDSCH has insufficient processing time, the UE may not provide a valid HARQ-ACK corresponding to the scheduled PDSCH.
  • Table 3 illustrates example PDSCH processing time N 1 for PDSCH processing capability 1.
  • ⁇ may stand for an SCS configuration or an SCS index.
  • dmrs-AdditionalPosition may indicate position for additional dmrs in DL.
  • An MsgB-RNTI may be a sum of an offset (e.g., 14 ⁇ 80 ⁇ 8 ⁇ 2) and an RA-RNTI, where the offset may be used to separate a space for the MsgB-RNTI and the RA-RNTI.
  • the offset value may be a max value calculated from an original RA-RNTI formula for a 4-step RACH.
  • An msgB-ResponseWindow may be a time window used to monitor RAR (s) for a 2-step RA type (e.g., SpCell only) .
  • the msgB-ResponseWindow may be in terms of slots.
  • the msgB-ResponseWindow may be configured by the network and have a value lower than or equal to 40ms.
  • a validation of a PUSCH occasion may be based on the type of the spectrum (e.g., paired spectrum and unpaired spectrum) .
  • the PUSCH occasion may be valid if it does not overlap in time and frequency with any PRACH occasion associated with either a Type-1 RA procedure or a Type-2 RA procedure.
  • the PUSCH occasion may be valid if the PUSCH occasion does not precede a SS/PBCH block in a PUSCH slot and the PUSCH occasion starts at least N gap symbols after the last SS/PBCH block symbol.
  • the PUSCH occasion may be valid if the PUSCH occasion is within UL symbols. If the UE is provided with the tdd-UL-DL-ConfigurationCommon, the PUSCH occasion may be valid if the PUSCH occasion does not precede a SS/PBCH block in a PUSCH slot and the PUSCH occasion starts at least N gap symbols after the last DL symbol and at least N gap symbols after the last SS/PBCH block symbol that does not overlap with a set of consecutive symbols before a start of a next channel occupancy time in which the UE does not transmit.
  • guardPeriodMSGA-PUSCH may be a guard period between PUSCH occasions in units of symbols and have a value selected from INTEGER (0 ...3) .
  • An MSGA-PUSCH-TimeDomainOffset may be a single time offset with respect to a start of each PRACH slot (with at least one valid RO) , count as the number of slots (based on a numerology of active UL BWP) .
  • the MSGA-PUSCH-TimeDomainOffset may have a value selected from INTEGER (1 . .. 32) .
  • Type0A-PDCCH CSS set may be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by an SI-RNTI on a primary cell of an MCG.
  • SI-RNTI An SI-RNTI may be used for broadcast of System Information and have an RNTI value of FFFF.
  • a fallbackRAR may be of a fixed size and include at least one of the following fields:
  • An R field may refer to a reserved bit, which may be set to “0” .
  • Timing Advance Command field may indicate an index value TA used to control an amount of timing adjustment that a MAC entity has to apply.
  • the size of the Timing Advance Command field may be 12 bits.
  • a UL Grant field may indicate resources (to be) used on an uplink.
  • the size of the UL Grant field may be 27 bits.
  • a Temporary C-RNTI field may indicate a temporary identity that is used by a MAC entity during Random Access.
  • the size of the Temporary C-RNTI field may be 16 bits.
  • a successRAR may be of a fixed size and include at least one of the following fields:
  • a UE Contention Resolution Identity field may contain a UL CCCH SDU. If the UL CCCH SDU is longer than 48 bits, this field may contain the first 48 bits of the UL CCCH SDU.
  • An R field may refer to a reserved bit, which may be set to “0” .
  • a ChannelAccess-CPext field may indicate channel access type and CP extension for a PUCCH resource containing HARQ feedback for an MsgB (referred to as MsgB HARQ feedback in the present disclosure) in shared spectrum channel access. This field may be present when the HARQ feedback for the MSGB is (to be) transmitted with the shared spectrum channel access. Otherwise, this field may not be present and R bits may be present instead.
  • the size of the ChannelAccess-CPext field may be 2 bits.
  • a TPC field may be referred to as a TPC command field for a PUCCH resource containing HARQ feedback for a MSGB.
  • the size of the TPC field may be 2 bits.
  • a HARQ Feedback Timing Indicator field may also be referred to as a PDSCH-to-HARQ Feedback Timing Indicator field for MSGB HARQ feedback.
  • the size of the HARQ Feedback Timing Indicator field may be 3 bits.
  • a PUCCH Resource Indicator field may be for HARQ feedback for a MSGB.
  • the size of the PUCCH resource Indicator field may be 4 bits.
  • Timing Advance Command field may indicate an index value TA used to control an amount of timing adjustment that a MAC entity has to apply.
  • the size of the Timing Advance Command field may be 12 bits.
  • a C-RNTI field may indicate an identity that is used by a MAC entity upon completion of Random Access.
  • the size of the C-RNTI field may be 16 bits.
  • a C-RNTI MAC CE may have a fixed size and include a (e.g., single) field defined as follows:
  • An ra-ContentionResolutionTimer may be a Contention Resolution Timer and have a value selected from ENUMERATED ⁇ sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64 ⁇ .
  • a value sf8 may correspond to 8 subframes
  • a value sf16 may correspond to 16 subframes.
  • An MAC PDU may include one or more MAC subPDUs and optionally padding.
  • Each of the MAC subPDUs may include one of the following:
  • K_offset in some implementations, a K_offset (referred to as N offset ) may be used to enhance at least one of the following timing relationships:
  • TA value may be an RTT on a service link between a satellite to the UE or a link between a BS to the UE.
  • RRT prediction may be a prediction for an RTT on a service link or a link between a BS to the UE.
  • TA compensation may be compensation based on the “TA value” or the “RRT prediction” .
  • Type-1 RA 4-step RA type with an Msg1
  • Type-2 RA 2-step RA type with an MsgA
  • Both types of RA procedures support CBRA and CFRA.
  • the Msg1 of the 4-step RA type may include a preamble on a PRACH.
  • a UE may monitor a first response (such as an Msg2 (e.g., RAR) ) from the network within a configured window.
  • a first response such as an Msg2 (e.g., RAR)
  • the (dedicated) preamble for the Msg1 transmission may be assigned by the network.
  • the UE may end the 4-step RA procedure.
  • the UE may send an Msg3 using a UL grant scheduled in the first response, and monitor a second response (such as an Msg4 (e.g., contention resolution) ) .
  • a second response such as an Msg4 (e.g., contention resolution)
  • the UE may perform (e.g., go back to) the Msg1 transmission.
  • the MsgA of the 2-step RA type may include a preamble on a PRACH and a payload on a PUSCH.
  • the UE may monitor a response (such as an MsgB (e.g., first contention resolution) ) from the network within a configured window.
  • a response such as an MsgB (e.g., first contention resolution)
  • the (dedicated) preamble and PUSCH resource may be configured for the MsgA transmission.
  • the UE may end the 2-step RA procedure.
  • the UE may end the 2-step RA procedure. If a fallback indication is received in the MsgB, the UE may perform Msg3 transmission using a UL grant scheduled in the fallback indication, and monitor second contention resolution.
  • the UE may perform (e.g., go back to) the MsgA transmission.
  • the UE may monitor the response from the network within the configured window after the Msg1 or MsgA transmission. However, if the configured window is configured without considering an RTT required in NTN, the UE may not find the response within the configured window.
  • An RAR window (e.g., ra-ResponseWindow) may be a time window used to monitor RAR (s) .
  • the RAR window may be in terms of slots.
  • the RAR window may be configured in RACH-ConfigCommon.
  • the RAR window may start at a first PDCCH occasion from an end of RA preamble transmission, unless for CFRA for BFR. Note that if a contention-free Random Access Preamble for BFR request was transmitted by an MAC entity, a UE may start the RAR window configured in BeamFailureRecoveryConfig at the first PDCCH occasion (e.g., as specified in TS 38.213) from the end of the RA preamble transmission.
  • the soonest possible reception time may be 2 times a minimum one-way delay.
  • FIG. 2 illustrates a timing diagram 200 when a minimum RTT and a maximum differential RTT are (respectively) applied in NTN according to an example implementation of the present disclosure.
  • the 1 st RAR window 206 starts at the 1 st PDCCH occasion 204 from the end of the 1 st preamble transmission 202.
  • the UE may fail to find/receive an Msg2/RAR within the configured duration (e.g., 1 st RAR window 206) and attempt to perform multiple preamble transmissions (e.g., 2 nd preamble transmission 208) .
  • applying the minimum RTT in the NTN may lead to unnecessary UL preamble transmission and increments to a preamble transmission counter, and may even lead to RACH failure.
  • the processing time may be used for performing increment preamble transmission, applying random back-off, and performing RAR selection.
  • the maximum differential RTT may be defined as 2 times a maximum differential delay.
  • the maximum differential delay may be defined as a maximum one-way delay minus the minimum one-way delay within an NTN cell.
  • a UE may attempt to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during the RAR window (e.g., controlled by the network) .
  • the RAR window may start at the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for Type1-PDCCH CSS set.
  • the first symbol of the earliest CORESET is at least one symbol after the last symbol of a PRACH occasion corresponding to the PRACH transmission.
  • a symbol duration may correspond to an SCS for Type1-PDCCH CSS set.
  • a length of the RAR window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by an ra-ResponseWindow IE by the network.
  • FIG. 3 illustrates a timing diagram 300 regarding a start point of a RAR window 312 when an initial TA is applied for PRACH transmission 308 in NTN according to an example implementation of the present disclosure.
  • the UE DL 302 stands for a UE DL timeline.
  • the UE UL 304 stands for a UE UL timeline.
  • the UE transmits the PRACH 308 at (the timing) t1.
  • the RAR window 312 starts at t2/the CORESET 310 (e.g., the earliest CORESET in which the UE is configured to receive a PDCCH) .
  • the RAR window 312 expires at t3.
  • the periodicity of RO 306 is 5 ms.
  • the duration of the RAR window 312 is 10 ms.
  • the TA value is 16.25 ms.
  • the RTT is 16.25 ms.
  • a timing offset between two consecutive CSSs may be 5ms.
  • An SCS may be 15 kHZ.
  • An SS Periodicity and Offset may be sl5 INTEGER (0) .
  • a PRACH configuration index may be 19. It should be noted that the parameters are exemplary rather than limiting.
  • the UE When the initial TA is applied for the PRACH transmission 308 in the NTN, the UE (e.g., in Rel-15 and/or Rel-16) may start the RAR reception/the RAR window 312 (right) after the PRACH transmission 308 (e.g., the CORESET 310 right after the PRACH transmission 308) . Since an RA-RNTI is calculated based on the time and frequency indices of the selected RO 314, the UE may miss the corresponding RAR in the (configured) RAR window 312.
  • a reasonable starting point for a RAR reception may be after the selected RO 314 that is the timing after the PRACH transmission 308 with a delay of the TA.
  • the TA value may not be the RTT value.
  • the TA value may only include the service link delay and therefore the UE may need (additional) NW assistance information (e.g., the feeder link delay) to derive the RTT.
  • NW assistance information e.g., the feeder link delay
  • a UE may consider that an RAR reception is not successful.
  • the UE detects the DCI format 1_0 with the corresponding RA-RNTI within the window and LSBs of an SFN field in the DCI format 1_0, if included and applicable, are not the same as corresponding LSBs of the SFN in which the UE transmitted PRACH.
  • an MAC entity (of the UE) may perform at least one of the following operations:
  • a preamble transmission counter by 1. If the preamble transmission counter reaches a maximum value, the UE may indicate an RA problem to higher layers (e.g., if the RA preamble is transmitted on an SpCell) . If the preamble transmission counter reaches the maximum value, the UE may not indicate the RA problem to higher layers, if the preamble is transmitted on an SCell.
  • the UE may initiate an RA procedure.
  • the UE may (be expected to) transmit a PRACH no later than N T, 1 +0.75 msec after the last symbol of the window, or the last symbol of a PDSCH reception.
  • FIG. 4 illustrates a timing diagram 400 regarding PRACH retransmission when an initial TA is applied in NTN according to an example implementation of the present disclosure.
  • the UE DL 402 stands for a UE DL timeline.
  • the UE UL 404 stands for a UE UL timeline.
  • the UE transmits the 1 st PRACH 406 at t1 and transmits the 2 nd PRACH 414 at t4.
  • the 1 st RAR window 410 starts at the CORESET 408/t2.
  • the 1 st RAR window 410 expires at t3.
  • the periodicity of RO 412 is 5 ms.
  • the duration of the 1 st RAR window 410 is 10 ms.
  • the TA value is 16.25 ms.
  • the RTT is 16.25 ms.
  • the UE may perform RACH retransmission (e.g., 2 nd PRACH 414) within the processing time (e.g., 2 ms) after t3. That is, t4 is prior to t5.
  • the processing time may be based on 0.75 ms and 14 (OFDM) symbols, where 0.75 ms may be used for the MAC layer processing, and duration of 14 symbols may be used for decoding possible PDSCH reception.
  • a timing offset between two consecutive CSSs may be 5ms.
  • An SCS may be 15 kHZ.
  • a backoff time may be 0 ms. It should be noted that the parameters are exemplary rather than limiting.
  • the processing time (e.g., 2 ms) is for extreme scheduling.
  • the periodicity of RO 412 may be set to 5 ms and the backoff time may be set to 0 ms.
  • the real PRACH transmission timing may be based on actual scheduling.
  • the backoff time may be set to 20 ms.
  • the UE may transmit a PRACH preamble after the end of the backoff time after the RAR window.
  • additional processing time may be considered. This additional processing time may be used to recalculate a new autonomous TA value based on the same information used for the previous PRACH transmission or based on the latest information about UE GNSS and satellite ephemeris from a GNSS receiver at the UE and SI provided by the network.
  • a UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI and/or C-RNTI during the MsgB-RAR window (e.g., controlled by the network) .
  • PO stands for PUSCH occasion.
  • the MsgB-RAR window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set.
  • the first symbol of the earliest CORESET is at least one symbol after the last symbol of the following start points corresponding to the PRACH transmission:
  • a symbol duration may correspond to an SCS for Type1-PDCCH CSS set.
  • a length of the MsgB-RAR window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by an msgB-ResponseWindow IE.
  • the PO may be valid if it does not overlap in time and frequency with any RO associated with either a Type-1 RA procedure or a Type-2 RA procedure. However, at least one of the following reasons may cause the UE to transmit the PRACH only without the PUSCH even having the valid PO:
  • the UE may transmit a PRACH preamble on a valid RO if the PRACH preamble is not mapped to the valid PO. Therefore, there may be multiple possible start points of the MsgB-RAR window.
  • FIG. 5 illustrates a timing diagram 500 when a start point of an MsgB-RAR window 516 is based on a PO 514 according to an example implementation of the present disclosure.
  • the UE DL 502 stands for a UE DL timeline.
  • the UE UL 504 stands for a UE UL timeline.
  • the UE transmits the PRACH 508 at t1 and transmits the PUSCH 510 at t2.
  • the MsgB-RAR window 516 starts at the CORESET 512 (e.g., the earliest CORESET in which the UE is configured to receive PDCCH) /t3.
  • the periodicity of RO 506 is 5 ms.
  • the periodicity of PO 514 is 5 ms.
  • the duration of the MsgB-RAR window 516 is 10 ms.
  • the TA value is 16.25 ms.
  • the RTT is 16.25 ms.
  • FIG. 5 illustrates the case 1 that the MsgA is transmitted completely (i.e., both the PRACH 510 and the PUSCH 512 are transmitted) , and the start of the MsgB-RAR window 516 is after the last symbol of the PO 514 (or the last symbol of PUSCH transmission 512 of the MsgA) . It should be noted that the start of the MsgB-RAR window 516 may also be used for the case 2 (i.e., transmission of only the PRACH if the PRACH preamble is mapped to the valid PO) .
  • a timing offset between two consecutive CSSs may be 5ms.
  • An SCS may be 15 kHZ.
  • An SS Periodicity and Offset may be sl5 INTEGER (0) .
  • a PRACH configuration index may be 19.
  • An msgA-PUSCH-TimeDomainOffset may be 1 slot. It should be noted that the parameters are exemplary rather than limiting.
  • the UE may start the MsgB-RAR window 516 at the first symbol of the CORESET 512.
  • the MsgB-RAR window 516 may be configured up to 40 ms and it may cover a need of a maximum absolute RTT and differential RTT in an NTN serving cell provided by an LEO satellite (e.g., the LEO satellite on an orbit of 600 km) .
  • the MsgB-RAR window (e.g., window duration) may not be properly configured due to a lack of UE-specific RTT for the network to obtain the UE autonomous TA. In this case, the UE may fail to receive the possible RAR within the MsgB-RAR window.
  • the RTT may be changed up to 1.28 ⁇ s in this time offset period due to satellite movement.
  • MsgA-PUSCH-TimeDomainOffset e.g., the maximum offset value of 32 slots between PRACH and PUSCH
  • the RTT may be changed up to 1.28 ⁇ s in this time offset period due to satellite movement.
  • the UE only needs one TA value for both the PRACH and PUSCH transmission, it is unclear which TA value to be used by the UE since two TA values may be different. For example, it is unclear whether the TA value used by the UE is based on the TA of the PRACH transmission or the PUSCH transmission.
  • the NW assistance information may be provided via other SIBs (e.g., SIB9 or NTN SIBs) which may be scheduled by a different search space and RNTI (e.g., Type0A-PDCCH CSS set with CRC scrambled by an SI-RNTI) , and the UE may skip the NW assistance information by sending MsgA before the SIB9 or the NTN SIBs reception.
  • SIB9 or NTN SIBs e.g., SIB9 or NTN SIBs
  • RNTI e.g., Type0A-PDCCH CSS set with CRC scrambled by an SI-RNTI
  • FIG. 6 illustrates a timing diagram 600 when a start point of an MsgB-RAR window 614 is based on a RO 612 according to an example implementation of the present disclosure.
  • the UE DL 602 stands for a UE DL timeline.
  • the UE UL 604 stands for a UE UL timeline.
  • the UE transmits the PRACH 608 at t1.
  • the MsgB-RAR window 614 starts at the CORESET 610 (e.g., the earliest CORESET in which the UE is configured to receive PDCCH) /t2.
  • the periodicity of RO 612 is 5 ms.
  • the periodicity of PO 606 is 5 ms.
  • the duration of the MsgB-RAR window 614 is 10 ms.
  • the TA value is 16.25 ms.
  • the RTT is 16.25 ms.
  • FIG. 6. illustrates the case 3 that transmission of only the PRACH 608 if the PRACH preamble is not mapped to a valid PO.
  • the network and the UE may know that the selected RO 616 has an invalid PO given in an RACH configuration.
  • the MsgB-RAR window 614 may be moved forward in time followed by the PRACH transmission 608 and start after the last symbol of the RO 612 (or the last symbol of the PRACH transmission 608 of the MsgA) .
  • a timing offset between two consecutive CSSs may be 5ms.
  • An SCS may be 15 kHZ.
  • An SS Periodicity and Offset may be sl5 INTEGER (0) .
  • a PRACH configuration index may be 19.
  • An msgA-PUSCH-TimeDomainOffset may be 1 slot. It should be noted that the parameters are exemplary rather than limiting.
  • the UE may start the MsgB-RAR window 614 at the first symbol of the CORESET 610.
  • the MsgB-RAR window 614 may not be properly configured, and the UE may fail to receive the possible RAR within the MsgB-RAR window 614.
  • the UE may detect RAR message (s) from the TB when the following conditions are met:
  • the UE detects a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI and/or C-RNTI.
  • LSBs of an SFN field in the DCI format 1_0, if applicable, are the same as corresponding LSBs of the SFN in which the UE transmitted PRACH.
  • the RAR message (s) of the TB may include at least one of an MAC subheader, a Backoff indicator, a fallbackRAR, a successRAR, an MAC SDU for CCCH or DCCH, and a padding.
  • the UE may continue MSG3, and Msg4 of a Type-1 RA procedure when the UE detects a RAR UL grant.
  • the UE may transmit a PUCCH with HARQ-ACK information having ACK value, where:
  • a PUCCH resource for transmission of the PUCCH may be indicated by a PUCCH resource indicator field of 4 bits in the successRAR from a PUCCH resource set that is provided by the network.
  • a slot for the PUCCH transmission may be indicated by a PDSCH-to-HARQ_feedback timing indicator field of 3 bits in the successRAR having a value k from ⁇ 1, 2, 3, 4, 5, 6, 7, 8 ⁇ and the slot may be determined (be the UE) as n + k + ⁇ .
  • the UE may not expect the first symbol of the PUCCH transmission to be after the last symbol of the PDSCH reception by a time smaller than N T, 1 +0.5 msec.
  • N T, 1 may be a PDSCH processing time for UE processing capability 1.
  • a C-RNTI MAC CE is included in MsgA (for example, if the 2-step RACH is triggered in RRC_CONNECTED, such as triggered by SR failure or PDCCH order for UL timing synchronization)
  • the UE may monitor the PDCCH addressed to C-RNTI for success response and MsgB-RNTI.
  • the UE may transmit a PUCCH with HARQ-ACK information, which has ACK value if the UE correctly detects the TB or has NACK value if the UE incorrectly detects the TB and a time alignment timer is running.
  • the UE may not expect to be indicated to transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time when the UE applies a TA command that is provided by the TB.
  • FIG. 7 illustrates a timing diagram 700 when a fallbackRAR 710 is received within an MsgB-RAR window 712 according to an example implementation of the present disclosure.
  • the UE DL 702 stands for a UE DL timeline.
  • the UE UL 704 stands for a UE UL timeline.
  • the UE transmits the PUSCH 708 at t1.
  • the MsgB-RAR window 712 starts at t2.
  • the UE receives the fallbackRAR 710 (included in the MsgB) at t4.
  • the UE transmits the Msg3 714 at t5.
  • the RA-CR window 718 starts at t6.
  • the UE receives the Msg4 716 at t8.
  • the UE transmits the HARQ-ACK 720 at t9.
  • the MsgA may include the PRACH 706 and the PUSCH 708.
  • the 1 st offset may be a timing offset between t1 and t2.
  • the 2 nd offset may be associated with a timing offset between t4 and t5.
  • the 3 rd offset may be a timing offset between t5 and t6.
  • the 4 th offset may be associated with a timing offset between t8 Msg4 reception and t9. There may be (selected) ROs at t3, t7 and t10.
  • the 1 st offset and the 3 rd offset may be derived by the UE.
  • the 2 nd offset may be provided by the fallbackRAR 710 accompanying with SI (e.g., K_offset provided in SIB1 or NTN SIBs) if needed.
  • the 4 th offset may be indicated by a DCI format in the PDCCH within the RA-CR window 718 accompanying with SI if needed.
  • the 1 st TA may be derived by the UE with GNSS.
  • the 2 nd TA may be updated by the fallbackRAR 710.
  • the HARQ-ACK transmission 720 may be included in PUCCH transmission.
  • the Msg4 reception 716 may be within the RA-CR window 718 controlled by an ra-ContentionResolutionTimer.
  • the UE may start the ra-ContentionResolutionTimer and restart the ra-ContentionResolutionTimer at each HARQ retransmission in the first symbol after an end of Msg3 transmission 714. If the ra-ContentionResolutionTimer expires, the UE may consider Contention Resolution unsuccessful.
  • the UE may transmit HARQ-ACK (information) 720 for the received Msg4 716.
  • the network may guarantee proper scheduling regarding required TA and UE processing time.
  • the 2 nd offset may be provided by K_offset (e.g., broadcast in SI) , but formulation detail is still unknown.
  • FIG. 8 illustrates a timing diagram 800 when a successRAR 810 is received within an MsgB-RAR window 812 according to an example implementation of the present disclosure.
  • the UE DL 802 stands for a UE DL timeline.
  • the UE UL 804 stands for a UE UL timeline.
  • the UE transmits the PUSCH 808 at t1.
  • the MsgB-RAR window 812 starts at t2.
  • the UE receives the successRAR 810 (included in the MsgB) at t4.
  • the UE transmits the HARQ-ACK 814 at t5.
  • the MsgA may include the PRACH 806 and the PUSCH 808.
  • the 1 st offset may be a timing offset between t1 and t2.
  • the 2 nd offset may be associated with a timing offset between t4 and t5.
  • a minimum processing time associated with the successRAR 810 and another (e.g., next) UL transmission may be 1.5 ms.
  • UE processes another UL transmission within 1.5 ms after receiving a successRAR.
  • There may be (selected) ROs at t3 and t6.
  • the 1 st TA may be derived by the UE.
  • the 2 nd TA may be updated via the received successRAR 810.
  • the HARQ-ACK (information) 814 may be ACK value only.
  • the HARQ-ACK transmission 814 may be included in PUCCH transmission.
  • FIG. 9 illustrates a timing diagram 900 when MsgA 906 includes a C-RNTI MAC CE according to an example implementation of the present disclosure.
  • the UE DL 902 stands for a UE DL timeline.
  • the UE UL 904 stands for a UE UL timeline.
  • the UE transmits the C-RNTI MAC CE in the MsgA 906.
  • the MsgA includes the PRACH and the PUSCH 908 transmitted at t1.
  • the MsgB-RAR window 912 starts at t2.
  • the UE receives the PDSCH 910 in the at t4.
  • the UE may receive an MsgB in the PDSCH 910.
  • the UE transmits the HARQ-ACK 914 at t5.
  • the 1 st offset may be a timing offset between t1 and t2.
  • the 2 nd offset may be associated with a timing offset between t4 and t5.
  • the UE may receive a DCI format in the PDCCH within the MsgB-RAR window 912.
  • the DCI format in the PDCCH may provide the 2 nd offset for the HARQ-ACK (information) 914 (e.g., either ACK or NACK value) for the received PDSCH 910.
  • the HARQ-ACK transmission 914 may be included in PUCCH transmission.
  • the network may guarantee that the 2 nd offset is long enough to cover the 2 nd TA value required for the PUCCH transmission.
  • a UE may (re) transmit Msg1 or MsgA if at least one of the following conditions (for determining unsuccessful RAR reception) are met:
  • the UE detects the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of an SFN field in the DCI format 1_0, if applicable, are not the same as corresponding LSBs of the SFN in which the UE transmitted the PRACH.
  • the UE does not identify an RAPID associated with the PRACH transmission from the UE.
  • the UE may perform at least one of the following operations.
  • the UE may (be expected to) (re) transmit a PRACH no later than N T, 1 +0.75 msec after the last symbol of the window, or the last symbol of a PDSCH reception.
  • N T, 1 may be a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured.
  • FIG. 10 illustrates a timing diagram 1000 regarding MsgA retransmission with (both) PRACH retransmission 1018 and PUSCH retransmission 1020 according to an example implementation of the present disclosure.
  • the UE DL 1002 stands for a UE DL timeline.
  • the UE UL 1004 stands for a UE UL timeline.
  • the UE transmits the 1 st PRACH 1006 at t1 and transmits the 1 st PUSCH 1008.
  • the 1 st MsgB-RAR window 1012 starts at the CORESET 1010/t2.
  • the 1 st MsgB-RAR window 1012 expires at t3.
  • the UE transmits the 2 nd PRACH 1018 at t4 and transmits the 2 nd PUSCH 1020 at t5.
  • the 2 nd PRACH 1018 may be transmitted within the processing time (e.g., 2 ms) after t3. That is, t4 may be prior to t6.
  • the periodicity of RO 1014 is 5 ms.
  • the periodicity of PO 1016 is 5 ms.
  • the duration of the 1 st MsgB-RAR window 1012 is 10 ms.
  • the 1 st TA value may be 16.25 ms.
  • An RTT may be 16.25 ms.
  • a timing offset between two consecutive CSSs may be 5ms. It should be noted that the parameters are exemplary rather than limiting.
  • additional processing time may be considered.
  • the additional processing time may be used to (re) calculate a new autonomous TA value (e.g., 2 nd TA) and be used to update an autonomous TA report via the PUSCH of the MsgA retransmission.
  • the TA may be used for timing alignment of UL transmission from all served UEs in a cell.
  • the network may control UE-specific UL transmission timing by advancing a UL frame to a DL frame, as shown in FIG. 7.
  • the network scheduler may consider appropriate timing constraints due to a minimum UE processing time and a required TA value.
  • FIG. 11 illustrates a timing diagram 1100 regarding a TA and UE processing time requirement according to an example implementation of the present disclosure.
  • the network scheduler may need a large scheduling offset to accommodate large TA values required in NTN.
  • the enhancement may include introducing an offset K 0ffset and applying it to modify the relevant timing relationship involved DL-UL timing interaction.
  • the scheduled PUSCH may be indicated on n + K2 + K offset slot.
  • the UE may calculate a propagation delay on a service link (e.g., a transmission delay between the UE and a satellite) , when assistant information (e.g., UE GNSS information and Satellite ephemeris) is available.
  • a service link e.g., a transmission delay between the UE and a satellite
  • assistant information e.g., UE GNSS information and Satellite ephemeris
  • the TA value may also include a feeder link delay, which may need location information about a gNB or GW location that provides NTN access to the gNB.
  • the GW may also provide other missions than commercial Satcom service, and lead to a security issue.
  • FIG. 12 illustrates a timing diagram 1200 regarding UL and DL timing alignment at a satellite 1204 according to an example implementation of the present disclosure.
  • an alternative to handle the above mentioned issue is that the UL and DL frames are aligned only at the satellite 1204.
  • TA at the UE (side) 1202 may cover only the service link and a new additional timing delay at the gNB (side) 1206 may cover the feeder link delay.
  • this timing delay for the feeder link may be broadcast via SI (e.g., SIB1, or NTN SIBs) if needed.
  • SI e.g., SIB1, or NTN SIBs
  • UE autonomous TA may only cover the service link delay by UE GNSS and satellite ephemeris. However, for the offset applied to the start of ra-ResponseWindow, the complete RTT between gNB and UE is required that may include the feeder link delay as well.
  • Logical Time may mean that all of the following are assumed to be zero.
  • Actual Time may mean that values observed by the UE are assumed for at least one of the following:
  • the UE may start the RAR window after PRACH transmission.
  • an expected RAR message may be missed (e.g., not found) within a configured window if RTT is not considered, for example, in an NTN scenario.
  • a UE-specific and/or a cell-specific offset between a PRACH transmission and the start of the RAR window based on a UE-specific and/or a cell-specific RTT prediction may be introduced.
  • the RTT prediction may include a service link delay only.
  • the RTT prediction may include at least one of the service link delay and a feeder link delay.
  • the service link delay may be associated with at least one of the following relations.
  • GNSS clock timing provided by a GNSS receiver and gNB clock timing (e.g., the timestamp in SIB9) provided by the network.
  • GNSS information on a center of a serving cell and/or a shape and size of the serving cell on a sea level or a certain height for airplane mounted devices.
  • a serving satellite Being indicated by the network via a reference delay between a serving satellite and the reference location on the ground, for example, the center of the serving cell on the sea level or the certain height for flights.
  • the feeder link delay may be associated with at least one of the following relations.
  • SI e.g., SIB1 or other SIBs
  • An RTT prediction may be used as a UE-specific offset after the PRACH transmission to start the RAR window.
  • Approaches based on either UE UL-frame timing or UE DL-frame timing are disclosed as follows.
  • the UE may postpone the start of the RAR window by the RTT prediction.
  • the start may be based on the UE-UL frame timing (as well) .
  • the RAR window may be started on UE UL slot p+K RTT .
  • K RTT may denote the RTT prediction in a UL slot number.
  • the RAR window may start on the first UE DL slot/symbol after UE UL slot p+K RTT .
  • the existence of PDCCH monitoring occasion (s) may be used to the first UE DL slot.
  • the UE may postpone the start of the RAR window by the RTT prediction.
  • the start may be based on the UE-DL frame timing.
  • the UE may start the RAR window after the UE DL slot p.
  • FIG. 13 illustrates a timing diagram 1300 regarding a start of an RAR window according to an example implementation of the present disclosure.
  • the NW DL 1302 stands for a NW DL timeline.
  • the NW UL 1312 stands for a NW UL timeline.
  • the UE DL 1322 stands for a UE DL timeline.
  • the UE UL 1332 stands for a UE UL timeline.
  • the NW DL slot 1304, the NW UL slot 1314, the UE DL slot 1324, and the UE UL slot 1334 may correspond to the same slot index.
  • the NW DL slot 1306, the NW UL slot 1316, the UE DL slot 1326, and the UE UL slot 1336 may correspond to the same slot index.
  • the start of the RAR window is on the UE DL slot 1328.
  • the start of the RAR window is based on the UE UL slot 1336 or the UE DL slot 1326. This timing may be interpreted via the slot that has the new offset after the UE UL slot 1326 or the slot after the UE DL slot 1336.
  • the UE may receive an indication (e.g., in SIB1) that prevents UEs from starting a PRACH transmission or an MsgA transmission before receiving network assistant information in other indications (e.g., other SIBs and/or a dedicated RRC configuration) if provided.
  • This indication and/or a specific indication may be used to request the UE to perform autonomous TA compensation for the Msg1 transmission or the MsgA transmission.
  • the UE may only be allowed to initiate a RA procedure after the calculation of the TA compensation or the RTT prediction for the Msg1 transmission or the MsgA transmission is completed.
  • the UE may perform the calculation of the TA compensation or the RTT prediction for the Msg1 transmission or the MsgA transmission if the UE operates in an NTN scenario, which may be explicitly indicated by SI or implicitly determined by the UE (e.g., if NTN related indication, parameter (s) , information, and/or SIBs are provided) .
  • the MAC entity may perform the operations according to Table 4 once the RA Preamble is transmitted and regardless of possible occurrence of a measurement gap.
  • Table 4 illustrates UE behavior for an RAR reception.
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window (e.g., controlled by the network) .
  • the window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set, which is at least K RTT symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • K RTT T SL +T FL , if the UE attempts to camp on an NTN cell
  • T SL may be the predicted RTT for the service link used for the PRACH transmission and T FL may be the indicated RTT for the feeder link provided via SI in a number of symbols.
  • the length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by ra-ResponseWindow.
  • the K RTT may be provided by the network (e.g., via SI, RRC configuration) .
  • the UE may (need to) start the RAR window/MsgB window at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. In this case, the UE may need to extend the RAR window.
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window (e.g., controlled by the network) .
  • the window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set.
  • the first symbol of the earliest CORESET is at least one symbol after at least one of the following time resources of the PRACH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • a length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by ra-ResponseWindow.
  • the indicated value of a TA command provided from the gNB or the autonomous TA value derived from the UE may have a format including at least one of an SFN, a subframe number, slot number, and symbol number or any combinations of the above numbers. For example, only SFN and slot number shown in the format of the TA value may be applied for the UL transmission.
  • the UE may start the MsgB-RAR window after PRACH and/or PUSCH transmission. However, an expected MsgB-RAR message may be missed (e.g., not found) within the window if RTT is not considered.
  • a UE-specific offset between MsgA transmission and the start of the MsgB-RAR window based on a UE-specific RTT prediction may be introduced.
  • the RTT prediction may be used as the UE-specific offset after the MsgA transmission to start the MsgB-RAR window.
  • Approaches based on either UE UL-frame timing or UE DL-frame timing are disclosed as follows.
  • the UE may postpone the start of the Msg-B RAR window by the RTT prediction.
  • the start may be based on the UE-UL frame timing (as well) .
  • the MsgB-RAR window may be started on UE UL slot u+K RTT .
  • K RTT may denote the RTT prediction in a UL slot number.
  • the UE may postpone the start of the MsgB-RAR window by the RTT prediction, where the start is based on the UE-DL frame timing.
  • the UE may start the MsgB-RAR window after the UE DL slot u.
  • FIG. 14 illustrates a timing diagram 1400 regarding a start of an MsgB-RAR window according to an example implementation of the present disclosure.
  • the NW DL 1402 stands for a NW DL timeline.
  • the NW UL 1412 stands for a NW UL timeline.
  • the UE DL 1422 stands for a UE DL timeline.
  • the UE UL 1432 stands for a UE UL timeline.
  • the NW DL slot 1404, the NW UL slot 1414, the UE DL slot 1424, and the UE UL slot 1434 may correspond to the same slot index.
  • the NW DL slot 1406, the NW UL slot 1416, the UE DL slot 1426, and the UE UL slot 1436 may correspond to the same slot index.
  • the start of the RAR window is on UE DL slot 1430.
  • the TA applied to the UE-UL frame may be derived based on either the PRACH transmission (on slot 1436) or the PUSCH transmission (on slot 1438) .
  • the UE may derive a TA value based on RTT prediction on the service link and use the TA value to adjust UL timing for an MsgA transmission (including transmission of a PRACH and a PUSCH) .
  • the UE may (attempt to) derive the TA value for the PUSCH transmission or to derive the TA value for the PRACH transmission.
  • the UE may (attempt to) derive the TA value for the PRACH transmission.
  • the UE may apply the derived TA value on the PRACH transmission only or the transmission of the PRACH and the PUSCH.
  • the UE may derive and apply one TA value for the PRACH transmission and another TA value for the PUSCH transmission.
  • the UE may derive a UL frequency compensation value based on some prediction on the service link and use the compensation value to adjust the UL frequency for an MsgA transmission (including transmission of a PRACH and a PUSCH) .
  • the UE may (attempt to) derive the compensation value for the PUSCH transmission or to derive the compensation value for the PRACH transmission.
  • the UE may (attempt to) derive the compensation value for the PRACH transmission.
  • the UE may apply the derived UL frequency compensation value on the PRACH transmission only or the transmission of the PRACH and the PUSCH.
  • the UE may derive and apply one UL frequency compensation value for the PRACH transmission and another UL frequency compensation value for the PUSCH transmission.
  • the MAC entity (of the UE) may perform at least one of the following operations once the MsgA preamble is transmitted and regardless of possible occurrence of a measurement gap.
  • Table 5 illustrates UE behavior for an MsgB reception.
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window (e.g., controlled by the network) .
  • the window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set, which is at least K RTT symbol after the last symbol of the PUSCH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • K RTT T SL +T FL , if the UE attempts to camp on an NTN cell
  • T SL may be the predicted RTT for the service link used for the PRACH transmission or the PUSCH transmission and T FL may be the indicated RTT for the feeder link provided via SI in a number of symbols.
  • the length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by msgB-ResponseWindow.
  • the K RTT may be provided by the network (e.g., via SI, RRC configuration) .
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window (e.g., controlled by the network) .
  • the window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set, which is at least K_RTT symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • K RTT T SL +T FL , if the UE attempts to camp on an NTN cell
  • T SL may be the predicted RTT for the service link used for the PRACH transmission and T FL may be the indicated RTT for the feeder link provided via SI in a number of symbols.
  • the length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by msgB-ResponseWindow.
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window (e.g., controlled by the network) .
  • the window may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set.
  • the first symbol of the earliest CORESET is at least one symbol after at least one of the following time resources of the PUSCH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • a length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by msgB-ResponseWindow.
  • a UE In response to a transmission of a PRACH, if the PRACH preamble is not mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window (e.g., controlled by the network) .
  • the window starts at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for Type1-PDCCH CSS set.
  • the first symbol of the earliest CORESET is at least one symbol after at least one of the following time resources of the PRACH occasion corresponding to the PRACH transmission.
  • the symbol duration may correspond to the SCS for Type1-PDCCH CSS set.
  • a length of the window in terms of slots, based on the SCS for Type1-PDCCH CSS set, may be provided by msgB-ResponseWindow.
  • the UE may (be expected to) (re) transmit a new PRACH. However, it is unclear if the UE shall derive a new TA value for the new PRACH (re) transmission. If the new TA value is needed, the UE may need additional processing time to handle the derivation.
  • the UE may only need to derive the TA value one time for the first Msg1 transmission and reuse the derived TA value for the other Msg1 (re) transmissions until the preamble transmission counter reaches its maximum or until the RA procedure is stopped.
  • the UE may only need to derive the TA value one time for the first Msg1 transmission and reuse the derived TA value for the other Msg1 (re) transmission in the same RA procedure.
  • the UE may re-derive the TA value for the Msg1 transmission in the same RA procedure if at least one of the following criteria is met.
  • the UE may re-derive the TA value for the Msg1 transmission in the same RA procedure if the RSRP of the DL path loss reference has changed more than a given value.
  • the UE may re-derive the TA value for the Msg1 transmission in the same RA procedure if the moving distance of the UE is longer than a given value.
  • the UE may re-derive the TA value for the Msg1 retransmission in the same RA procedure if the estimated TA change is larger than a (pre) specified/ (pre) configured value.
  • the estimated TA change may be based on, for example, UE location and/or satellite ephemeris escaped time from the last TA estimation/calculation.
  • the UE may re-derive the TA value for the Msg1 transmission in the same RA procedure if the UE is provided with an updated configuration for TA derivation (e.g., via SI) .
  • the UE may re-derive the TA value for the Msg1 transmission in the same RA procedure if a timer expires.
  • the UE may consider the derived TA is still valid while the timer is running. It should be noted that the criteria are not limited herein.
  • the UE may apply the latest derived TA value for the Msg1 transmission in the same RA procedure.
  • the UE may use a UE variable to store the derived TA value.
  • the MAC entity may indicate RA problem to higher layers and/or consider this RA procedure unsuccessfully completed (e.g., if the RA preamble is transmitted on the SpCell and if this RA procedure was triggered for SI request, and/or the RA preamble is transmitted on SCell) .
  • the new processing time may be numerology dependent given in a time duration of symbols or absolute time given in milliseconds.
  • This principle may also be applied to UL frequency pre-compensation, the UE may only need to derive the UL frequency compensation value one time for the first Msg1 transmission, and reuse the derived compensation value for the other Msg1 (re) transmissions until the preamble transmission counter reaches its maximum.
  • the UE may only need to derive the UE frequency compensation value one time for the first Msg1 transmission and reuse the derived compensation value for the other Msg1 (re) transmission in the same RA procedure.
  • the UE may re-derive the UE frequency compensation value for the Msg1 transmission in the same RA procedure if at least one of the following criteria is met.
  • the UE may re-derive the UE frequency compensation value for the Msg1 transmission in the same RA procedure if the RSRP of the DL path loss reference has changed more than a given value.
  • the UE may re-derive the UE frequency compensation value for the Msg1 transmission in the same procedure if the moving distance of the UE is longer than a given value. It should be noted that the criteria are not limited herein.
  • the UE may apply the latest derived UE frequency compensation value for Msg1 transmission in the same RA procedure.
  • the UE may re-derive the UL frequency compensation value for the Msg1 transmission in the same RA procedure if the UE is provided with an updated configuration for UL frequency compensation value (e.g., via SI) .
  • the UE may re-derive the UL frequency compensation value for the Msg1 transmission in the same RA procedure if a timer expires.
  • the UE may consider the derived UL frequency compensation value is still valid while the timer is running.
  • the UE may use a UE variable to save the derived UL frequency compensation value.
  • the new processing time may be numerology dependent given in a time duration of symbols or absolute time given in milliseconds.
  • the higher layers may indicate the physical layer to transmit a PRACH if at least one of the following conditions occurs.
  • the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and LSBs of an SFN field in the DCI format 1_0, if included and applicable, are not same as corresponding LSBs of the SFN in which the UE transmitted PRACH.
  • the UE may (be expected to) transmit a PRACH no later than a timing period (msec) after the last symbol of the window (or the last symbol of the PDSCH reception) .
  • the time period is disclosed as follows:
  • N T, 1 +0.75+N T, pre if UL timing or frequency pre-compensation is needed, e.g., a TA value.
  • N T, 1 maybe a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 .
  • N T, pre may be a time duration of N 1, pre symbols or slots corresponding to the processing time for the UL timing or UL frequency pre-compensation.
  • N 1, pre may be numerology dependent (e.g., different values of N 1, pre by different values of ⁇ ) .
  • ⁇ may correspond to the smallest SCS configuration among the SCS configurations for the PDCCH carrying the DCI format 1_0.
  • N T, pre may be provided by the network in SI, RRC messages, or may be predetermined values known between the network and UEs regulated in specifications.
  • the UE may report N T, pre as part of the UE capability report.
  • the UE may compile and transfer its UE capability information upon receiving a UECapabilityEnquiry from the network.
  • the UE may transmit a PRACH no later than N T, 1 +0.75 msec by using the same UL timing and UL frequency pre-compensation (e.g., the UE autonomous TA value and the UL Doppler frequency compensation) used for the previous PRACH transmission if the preamble transmission counter does not reach its maximum.
  • the same UL timing and UL frequency pre-compensation e.g., the UE autonomous TA value and the UL Doppler frequency compensation
  • the UE may (be expected to) transmit a new MsgA or a new PRACH. However, it is unclear if UE shall derive a new TA value for the new transmission. If the new TA value is needed, the UE may need additional processing time to handle the derivation.
  • the UE may only need to derive the TA value one time for the first MsgA transmission and reuse the derived TA value for the other MsgA (re) transmissions until the preamble transmission counter reaches its maximum.
  • the UE may only need to derive the TA value one time for the first MsgA transmission and reuse the derived TA value for the other MsgA (re) transmission in the same RA procedure.
  • the UE may re-derive the TA value for the MsgA transmission in the same RA procedure if at least one of the following criteria is met.
  • the UE may re-derive the TA value for the MsgA transmission in the same RA procedure if the RSRP of the DL path loss reference has changed more than a given value.
  • the UE may re-derive the TA value for the MsgA transmission in the same procedure if the moving distance of the UE is longer than a given value. It should be noted that the criteria are not limited herein.
  • the UE may apply the latest derived TA value for the MsgA transmission in the same RA procedure.
  • the UE may re-derive the TA value for the MsgA transmission in the same RA procedure if the UE is provided with an updated configuration for TA derivation (e.g., via SI) .
  • the UE may re-derive the TA value for the MsgA transmission in the same RA procedure if a timer expires.
  • the UE may consider the derived TA is still valid while the timer is running.
  • the new processing time may be numerology dependent given in a time duration of symbols or slots or absolute time given in milliseconds.
  • the UE may only need to derive the UL frequency compensation value one time for the first MsgA transmission, and reuse the derived compensation value for the other MsgA (re) transmissions until the preamble transmission counter reaches its maximum.
  • the UE may only need to derive the UE frequency compensation value one time for the first MsgA transmission and reuse the derived compensation value for the other MsgA transmission in the same RA procedure.
  • the UE may re-derive the UE frequency compensation value for the MsgA transmission in the same RA procedure if at least one of the following criteria is satisfied.
  • the UE may re-derive the UE frequency compensation value for the MsgA transmission in the same RA procedure if the RSRP of the DL path loss reference has changed more than a given value.
  • the UE may re-derive the UE frequency compensation value for the MSGA transmission in the same procedure if the moving distance of the UE is longer than a given value. It should be noted that the criteria are not limited herein.
  • the UE may apply the latest derived UE frequency compensation value for the MsgA transmission in the same RA procedure.
  • the UE may re-derive the UL frequency compensation value for the MsgA transmission in the same RA procedure if the UE is provided with an updated configuration for UL frequency compensation value (e.g., via SI) .
  • the UE may re-derive the UL frequency compensation value for the MsgA transmission in the same RA procedure if a timer expires.
  • the UE may consider the derived UL frequency compensation value is still valid while the timer is running.
  • the new processing time may be numerology dependent given in a time duration of symbols or absolute time given in milliseconds.
  • the higher layers may indicate the physical layer to transmit only PRACH according to a Type-1 RA procedure or to transmit both PRACH and PUSCH according to a Type-2 RA procedure if at least one of the following conditions occurs.
  • the UE detects the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of an SFN field in the DCI format 1_0, if applicable, are not same as corresponding LSBs of the SFN in which the UE transmitted the PRACH.
  • the UE may (be expected to) transmit a PRACH no later than a timing period (msec) after the last symbol of the window (or the last symbol of the PDSCH reception) .
  • the time period is disclosed as follows:
  • N T, 1 +0.75+N T, pre if UL timing or frequency pre-compensation is needed, e.g., a TA value.
  • N T, 1 may be a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured.
  • N T, pre may be a time duration of N 1, pre symbols or slots corresponding to the processing time for the UL timing or UL frequency compensation.
  • N 1, pre may be numerology dependent (e.g., different values of N 1, pre by different values of ⁇ ) .
  • ⁇ may correspond to the smallest SCS configuration among the SCS configurations for the PDCCH carrying the DCI format 1_0.
  • the UE may transmit a PRACH no later than N T, 1 +0.75 msec by using the same UL timing and UL frequency pre-compensation (e.g., the UE autonomous TA value and the UL Doppler frequency compensation) used for the previous PRACH transmission or the previous PUSCH transmission if the preamble transmission counter does not reach its maximum.
  • the same UL timing and UL frequency pre-compensation e.g., the UE autonomous TA value and the UL Doppler frequency compensation
  • the additional processing time to derive UL timing and frequency pre-compensation for Msg1 or MsgA transmission may be NTN scenario dependent.
  • the required processing time may be different based on NTN types (e.g. GEO satellite, LEO satellite, ATG, or High-Altitude Platform Station (HAPS) ) , or based on UE type (e.g., handheld device, VSAT, or mounted device on vehicles) .
  • NTN types e.g. GEO satellite, LEO satellite, ATG, or High-Altitude Platform Station (HAPS)
  • UE type e.g., handheld device, VSAT, or mounted device on vehicles
  • the UE when the UE receives the fallback RAR within the MsgB-RAR window, the UE may continue to transmit Msg3, receive Msg4, and transmit HARQ-ACK information.
  • the 2 nd offset, the 3 rd offset, and the 4 th offset there exists a need for enhancement on the 2 nd offset, the 3 rd offset, and the 4 th offset.
  • FIG. 15 illustrates a timing diagram 1500 regarding HARQ-ACK transmission when a fallbackRAR is received within an RA-CR window according to an example implementation of the present disclosure.
  • the NW DL 1502 stands for a NW DL timeline.
  • the NW UL 1512 stands for a NW UL timeline.
  • the UE DL 1522 stands for a UE DL timeline.
  • the UE UL 1532 stands for a UE UL timeline.
  • the NW DL slot 1504, the NW UL slot 1514, the UE DL slot 1524, and the UE UL slot 1534 may correspond to the same slot index.
  • the NW DL slot 1508, the NW UL slot 1518, the UE DL slot 1528, and the UE UL slot 1538 may correspond to the same slot index.
  • the UE transmits the Msg3 on the UE UL slot 1534.
  • the NW receives the Msg3 on the NW DL slot 1504.
  • the RA-CR window starts on UE DL slot 1526.
  • the NW transmits the DCI format (with C-RNTI) on the NW UL slot 1516.
  • the UE receives the DCI format (with C-RNTI) on the UE DL slot 1526.
  • the NW transmits the Msg4 on the NW UL slot 1518.
  • the UE receives the Msg4 on the UE DL slot 1528.
  • the UE transmits the HARQ-ACK on the UE UL slot 1540.
  • the 3 rd offset may be a scheduling offset between the Msg3 transmission on the UE UL slot 1534 and the start of the RA-CR window/timer (e.g., ra-ContentionResolutionTimer) on the UE DL slot 1526.
  • the 4th offset may refer to a scheduling offset between the Msg4 reception on the UE DL slot 1528 and the HARQ-ACK transmission on the UE UL slot 1540.
  • the 3rd offset may be for power saving by avoiding non-necessary PDCCH monitoring.
  • the 4th offset may be for proper scheduling by preventing the HARQ-ACK transmission prior to a time in which the UE receives the Msg4.
  • the UE may reuse the 1 st offset with some corrections from the TA command received from the fallback RAR.
  • the TA command may correct an RTT prediction by the Msg1/MsgA reception at the network side.
  • the TA command may provide a differential value for TA correction.
  • the differential value for the TA correction may be added to the 1 st offset value to determine the 3 rd offset value.
  • the UE may apply the TA (only) based on the TA command received from the fallback RAR to determine the 3 rd offset. For the 4 th offset, the UE may use a new scheduling offset K 1 +K offset .
  • K 1 may be indicated by a PDSCH-to-HARQ_feedback timing indicator field in a DCI format scheduling the Msg4 reception.
  • K offset may be provided by SI or cell-specific RRC parameters to accommodate long propagation delay required by NTN.
  • the scheduling offset of K 1 may be extended by adding more rows in a current lookup table or a new lookup table, provided by the network via a UE-specific RRC message.
  • the MAC entity may perform at least one of the following operations.
  • the UE may (attempt to) detect a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH during the RA-CR timer controlled by the ra-ContentionResolutionTimer that includes a UE contention resolution ID.
  • the UE may transmit HARQ-ACK information in a PUCCH.
  • the PUCCH transmission may be within the same active UL BWP as the PUSCH transmission.
  • the RA-CR timer may start at the first symbol of the earliest CORESET in which the UE is configured to receive PDCCH for a CSS set or a USS set.
  • the first symbol of the earliest CORESET is at least K RTT symbol after the last symbol of the Msg3 transmission.
  • the symbol duration may correspond to the SCS of the configured search space.
  • K RTT T SL +T FL +T C , if the UE attempts to camp on an NTN cell
  • T SL may be the predicted RTT for the service link used for the Msg1 or MsgA transmission.
  • T FL may be the indicated RTT for the feeder link provided via SI in a number of symbols.
  • T C may be the UL timing correction in a number of symbols corresponding to the index value provided by the TA Command field in the fallbackRAR.
  • a length of the window in terms of slots may be based on the SCS for the configured search space set.
  • the start of the RA-CR window may be based on the UE DL timeline.
  • the RA-CR window may start after a DL slot (e.g., UE DL slot 1524) corresponding to the UL slot (e.g., UE UL slot 1534) for the Msg3 transmission.
  • the UE may transmit HARQ-ACK information in a PUCCH.
  • the PUCCH transmission may be within the same active UL BWP as the PUSCH transmission.
  • the minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with the HARQ-ACK information may be equal to N T, 1 +0.5+N T, pre msec.
  • N T, pre may be used when an update of the timing or frequency pre-compensation is required and UL timing or UL frequency correction is provided by the Msg4.
  • the UE may provide corresponding HARQ-ACK information in a PUCCH transmission within slot n + k+K offset .
  • k may be a number of slots and may be indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format.
  • K offset may be a number of slots and may be provided by SI in RRC_IDLE or RRC_INACTIVE, or is provided by dedicated RRC messages in RRC_CONNECTED.
  • the UE may transmit HARQ-ACK information.
  • current timing definitions may not hold when there is a large offset between DL and UL frames at the UE side.
  • FIG. 16 illustrates a timing diagram 1600 regarding HARQ-ACK transmission when a successRAR is received within an MsgB-RAR window according to an example implementation of the present disclosure.
  • the NW DL 1602 stands for a NW DL timeline.
  • the NW UL 1612 stands for a NW UL timeline.
  • the UE DL 1622 stands for a UE DL timeline.
  • the UE UL 1632 stands for a UE UL timeline.
  • the NW DL slot 1604, the NW UL slot 1614, the UE DL slot 1624, and the UE UL slot 1634 may correspond to the same slot index.
  • the NW transmits the successRAR on the NW UL slot 1616.
  • the UE receives the successRAR on the UE DL slot 1626.
  • the UE transmits the HARQ-ACK on the UE UL slot 1538.
  • the NW receives the HARQ-ACK on the UE DL slot 1608.
  • the enhancement may (be expected to) prevent the UE to be indicated to transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time in which the UE receives the success RAR or applies a TA command which is provided by the TB.
  • K_offset for the HARQ-ACK transmission corresponding to the successRAR within the MsgB-RAR window may be introduced for enhancement on the 2 nd offset.
  • the UE may pass the TB to higher layers (e.g., the MAC entity) .
  • the higher layers may indicate the physical layer transmission of a PUCCH with HARQ-ACK information having ACK value if the RAR message (s) is for successRAR.
  • a slot for the PUCCH transmission may be indicated by a PDSCH-to-HARQ_feedback timing indicator field of 3 bits in the successRAR having a value k selected from ⁇ 1, 2, 3, 4, 5, 6, 7, 8 ⁇ .
  • the slot may be determined (by the UE) as n + k + ⁇ +K offset .
  • n may be a slot of the PDSCH reception.
  • K offset may be a number of slots as the scheduling enhancement provided by SI in an NTN cell.
  • the UE does not transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time in which the UE applies a TA command which is provided by the transport block.
  • the UE may transmit HARQ-ACK information.
  • current timing definitions may not hold when there is a large offset between DL and UL frames at the UE side.
  • K_offset may be introduced for HARQ-ACK transmission corresponding to the TB with the C-RNTI within the MsgB-RAR window.
  • the UE may transmit a PUCCH with HARQ-ACK information having ACK value if the UE correctly detects the TB. If the UE detects the DCI format 1_0 with the CRC scrambled by the C-RNTI and the TB in the corresponding PDSCH within the MsgB-RAR window, the UE may transmit the PUCCH with the HARQ-ACK information having NACK value if the UE incorrectly detects the TB and the time alignment timer is running.
  • a slot for the PUCCH transmission may be indicated by n+k+ ⁇ +K offset , which is similar to the 2 nd offset between the successRAR and the HARQ-ACK.
  • the UE may not transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time in which the UE applies a TA command which is provided by the TB.
  • a UE may apply the UE autonomous TA to a preamble transmission.
  • the network may not (be able to) correct a UL timing due to a lack of negative values in a TA command (e.g., TA command field of an RAR) .
  • the TA command may provide a delta adjustment to the TA.
  • 4-step RACH with pre-compensation at the UE side at least one of the following procedures may be used.
  • the UE may apply the estimated TA in the preamble transmission.
  • the UE may apply the TA command received in the RAR as the delta adjustment to the TA maintained on the UE side (e.g., the TA estimated in the Msg1 transmission) .
  • gNB may ensure a sufficient processing time on the UE side for the Msg3 transmission (e.g., the gNB may assume maximum TA is used on the UE side, where the maximum TA may be determined based on a coverage of the NTN cell) .
  • the UE may need enhancement on the UE autonomous TA estimation.
  • FIG. 17 illustrates a schematic diagram 1700 regarding uncertainty of UE autonomous TA estimation according to an example implementation of the present disclosure.
  • the estimation range of the UE autonomous TA assuming that the UE uses an unbiased estimator (e.g., a mean value of its estimation is on the (targeted) RO 1702 at t1) is illustrated. Due to existence of uncertainty, the UE may overestimate the TA value (e.g., before t1) , and transmit a preamble too early for the network to receive (e.g., after the (targeted) RO 1702) .
  • an unbiased estimator e.g., a mean value of its estimation is on the (targeted) RO 1702 at t1
  • the UE may overestimate the TA value (e.g., before t1) , and transmit a preamble too early for the network to receive (e.g., after the (targeted) RO 1702) .
  • a biased estimator e.g., the mean value of its estimation has been shifted by the standard deviation or by a predetermined value
  • the predetermined value may be associated with at least one of a PRACH format, a SCS, a targeted satellite orbit, and reliability on UE GNSS and satellite ephemeris information.
  • FIG. 18 illustrates a schematic diagram 1800 regarding a TA margin based on standard deviation for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • the TA margin may refer to the additional biased value of a PRACH transmission or the duration between the PRACH transmission with or without a margin shift for avoiding negative TA values in an RAR.
  • the TA margin shown in FIG. 18 may be the standard deviation or a confident region obtained (e.g., derived) from a TA estimator (e.g., biased estimator) .
  • the UE may guarantee variance of estimation errors of the TA estimator and use the variance (information) to transmit the PRACH transmission including a preamble that guarantees a certain low chance (e.g., 10 %) for the targeted gNB to receive the preamble (e.g., after (or on) the configured RO 1802) .
  • FIG. 19 illustrates a schematic diagram 1900 regarding a TA margin based on CP for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • the TA margin may be half of the longest (e.g., 0.5 ⁇ 684 ⁇ s or the shortest duration, e.g., 0.5 ⁇ 7 ⁇ s) of all available CP options for the network to configure. Since this information may be fixed and may be known between the gNB and the UE, signaling overhead may be save.
  • the scenario in which the UE transmits a preamble too early for the network to receive is thus prevented.
  • FIG. 20 illustrates a schematic diagram 2000 regarding a TA margin based on a maximum TA for UE autonomous TA estimation according to an example implementation of the present disclosure.
  • the TA margin may be half of the maximum TA which may be compensated during an initial access.
  • the UE may determine the TA margin based on the configured SCS on the PRACH transmission. For example, for SCS set to 15kHz, the maximum TA compensated may be 2ms and the TA margin may be 1 ms. That is, the UE may postpone the PRACH transmission 1 ms to the (selected) RO after the TA pre-compensation is applied.
  • the scenario in which the UE transmits a preamble too early for the network to receive is thus prevented.
  • Table 6 illustrates example of maximum TA compensated during initial access for different SCSs.
  • ⁇ may stand for an SCS configuration or an SCS index.
  • the TA value provided by the RAR may be for the subsequent message (s) (e.g., Msg3 and/or MsgB transmission) .
  • the TA value may be a differential value and may be added to an initial TA used by the UE for corresponding Msg1/MsgA transmission.
  • the TA value may be carried in at least one of MAC RAR, fallback RAR) , and success RAR.
  • An example format for the MAC RAR, the fallback RAR, and the success RAR may refer to, for example, TS 38.321 V16.1.0 Section 6.2.3 and 6.2.3a.
  • the TA value may indicate both negative value and positive value for combining the initial TA value. Such an indication may be identified by the reserved bit “R” in the MAC RAR, the fallback RAR, and the success RAR.
  • the TA command in the corresponding MAC CE may be mapped to positive TA values.
  • the TA command in the corresponding MAC CE may be mapped to negative TA values.
  • one bit from the TA command may be used to indicate the sign of the remaining bits.
  • MSB/LSB bit of the TA command field may be used to indicate whether the remaining bits of the TA command field is mapped to a positive value or a negative value.
  • the received bit of the RAR may only be used when the UE camps on an NTN cell (e.g., certain PLMN) .
  • NTN cell e.g., certain PLMN
  • At least one of NTN SIBs and autonomous TA request in SI may be identified during the cell search process.
  • the value of Z may be provided in SI or predetermined (e.g., in spec) .
  • the UE may apply the TA equal to (N TA +N TA, offset - N TA, margin ) ⁇ T c .
  • N TA may be estimation of TA by the UE.
  • N TA, offset may depend on band and LTE/NR coexistence.
  • N TA, margin may be a configurable parameter used as a margin to handle estimation uncertainty of the UE.
  • a maximal supported HARQ process number has been agreed to increase to 32 for at least one of the following reasons:
  • the UE capability may be considered. In this way, the UE may skip additional hardware requirements by reporting not to support the maximal HARQ process number more than 16.
  • the gNB may (be able to) support the maximal HARQ process number of 32 for any capable UE capable of camping on the NTN cell.
  • RAN1 may determine whether further constraint shall be added. For example, only certain UE types (e.g., with certain UE capabilities) are allowed to enable more than 16 HARQ processes.
  • UE categories may be defined as Handheld, Vehicular/Airplane/Building-mounted devices (other devices) , and VSAT. If the UE has a UE category that belongs to the Handheld, the UE may not be able to report via UE capability reporting to support or to enable more than 16 HARQ processes. If the UE is categorized as the VSAT or other (mounted devices) , the UE may be able to report via the UE capability reporting to support or to enable more than 16 HARQ processes. The UE may report the UE category in a UE capability report via RRC messages after the network requests it. The network may broadcast in system information whether a certain type of UE categories may camp on the provided NTN cell.
  • FIG. 21 illustrates a method 1700 for handling transmission timing performed by a UE according to an example implementation of the present disclosure.
  • the UE receives, from a BS, a first timing offset (e.g., K_offset) used in NTN.
  • the UE receives, from the BS, a response message in a RA procedure.
  • the UE obtains, according to the first timing offset, a first scheduling offset between the reception of the response message and a transmission of a HARQ-ACK feedback in response to the response message.
  • the UE transmits, to the BS, the HARQ-ACK feedback according to the first scheduling offset. For example, .
  • the response message may include a success RAR (e.g, successRAR) indicating a second timing offset (e.g., K) for the HARQ-ACK feedback used in TN.
  • the first scheduling offset may depend on a sum of the second timing offset, a processing time (e.g., ⁇ ) for a PUSCH transmission, and the first timing offset.
  • the response message may be a MsgB of a 2-step RA procedure.
  • the UE may receive, from the BS, DCI indicating a third timing offset (e.g., K_1) for the HARQ-ACK feedback used in TN.
  • the first scheduling offset may depend on a sum of the third timing offset and the first timing offset.
  • the response message may be a Msg4 of a 4-step RA procedure.
  • the UE may start a MsgB-RAR window according to a second scheduling offset.
  • the UE may receive, from the BS, a fallback RAR (e.g., fallbackRAR) within the MsgB-RAR window.
  • the fallback RAR may indicate a value (e.g., differential value) for a TA correction.
  • the UE may obtain, according to the first timing offset, a third scheduling offset between the reception of the fallback RAR and a transmission of a Msg3 in response to the fallback RAR.
  • the UE may transmit, to the BS, the Msg3 according to the third scheduling offset.
  • the UE may obtain a fourth scheduling offset between the transmission of the Msg3 and a start of an RA-CR window by adding the value with the second scheduling offset.
  • the UE may start the RA-CR window according to the fourth scheduling offset.
  • the DCI and the response message may be received within the RA-CR window.
  • the first timing offset may be received via SI (e.g., SIB1, MIB) . In some implementations, the first timing offset may be received via RRC signaling. In some implementations, the first timing offset may be received via a MAC CE.
  • SI e.g., SIB1, MIB
  • RRC Radio Resource Control
  • the first timing offset may be received via a MAC CE.
  • the first timing offset may be in terms of slots.
  • the first timing offset may be a cell specific value. In some implementations, the first timing offset may be a UE specific value.
  • actions 2102, 2104, 2106, and 2108 should not be construed as necessarily order dependent on their performance.
  • the order in which the process is described is not intended to be construed as a limitation, and any number of the described actions may be combined in any order to implement the method or an alternate method.
  • one or more of the actions illustrated in FIG. 21 may be omitted in some implementations.
  • FIG. 22 is a block diagram illustrating a node 2200 for wireless communication according to an example implementation of the present disclosure.
  • a node 2200 may include a transceiver 2220, a processor 2228, a memory 2234, one or more presentation components 2238, and at least one antenna 2236.
  • the node 2200 may also include a RF spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input /Output (I/O) ports, I/O components, and a power supply (not illustrated in FIG. 22) .
  • I/O Input /Output
  • the node 2200 may be a UE or a BS that performs various functions disclosed with reference to FIGs. 1 through 21.
  • the transceiver 2220 has a transmitter 2222 (e.g., transmitting/transmission circuitry) and a receiver 2224 (e.g., receiving/reception circuitry) and may be configured to transmit and/or receive time and/or frequency resource partitioning information.
  • the transceiver 2220 may be configured to transmit in different types of subframes and slots including but not limited to usable, non-usable and flexibly usable subframes and slot formats.
  • the transceiver 2220 may be configured to receive data and control channels.
  • the node 2200 may include a variety of computer-readable media.
  • Computer-readable media may be any available media that may be accessed by the node 2200 and include both volatile and non-volatile media, removable and non-removable media.
  • the computer-readable media may include computer storage media and communication media.
  • Computer storage media include both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or data.
  • Computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices.
  • Computer storage media do not include a propagated data signal.
  • Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media.
  • modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • Communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the previously listed components should also be included within the scope of computer-readable media.
  • the memory 2234 may include computer-storage media in the form of volatile and/or non-volatile memory.
  • the memory 2234 may be removable, non-removable, or a combination thereof.
  • Example memory includes solid-state memory, hard drives, optical-disc drives, etc.
  • the memory 2234 may store computer-readable, computer-executable instructions 2232 (e.g., software codes) that are configured to cause the processor 2228 to perform various disclosed functions, for example, with reference to FIGs. 1 through 21.
  • the instructions 2232 may not be directly executable by the processor 2228 but be configured to cause the node 2200 (e.g., when compiled and executed) to perform various disclosed functions.
  • the processor 2228 may include an intelligent hardware device, e.g., a Central Processing Unit (CPU) , a microcontroller, an ASIC, etc.
  • the processor 2228 may include memory.
  • the processor 2228 may process data 2230 and the instructions 2232 received from the memory 2234, and information transmitted and received via the transceiver 2220, the base band communications module, and/or the network communications module.
  • the processor 2228 may also process information to be sent to the transceiver 2220 for transmission via the antenna 2236 to the network communications module for transmission to a core network.
  • presentation components 2238 present data indications to a person or another device.
  • presentation components 2238 include a display device, a speaker, a printing component, and a vibrating component, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un UE et un procédé de gestion de synchronisation de transmission. Le procédé consiste à recevoir, en provenance d'une BS, un premier décalage de synchronisation utilisé dans NTN ; à recevoir, en provenance de la BS, un message de réponse dans une procédure RA ; à obtenir, selon le premier décalage de synchronisation, un premier décalage de planification entre la réception du message de réponse et la transmission d'une rétroaction HARQ-ACK en réponse au message de réponse ; et à transmettre, à la BS, la rétroaction HARQ-ACK selon le premier décalage de planification.
PCT/CN2021/125417 2020-10-22 2021-10-21 Équipement utilisateur et procédé de gestion de synchronisation de transmission WO2022083705A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104466P 2020-10-22 2020-10-22
US63/104,466 2020-10-22

Publications (1)

Publication Number Publication Date
WO2022083705A1 true WO2022083705A1 (fr) 2022-04-28

Family

ID=81289691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125417 WO2022083705A1 (fr) 2020-10-22 2021-10-21 Équipement utilisateur et procédé de gestion de synchronisation de transmission

Country Status (2)

Country Link
TW (1) TW202234938A (fr)
WO (1) WO2022083705A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4091387A4 (fr) * 2020-02-05 2024-06-26 MediaTek Singapore Pte. Ltd. Procédé et appareil pour une opération d'avance temporelle de canal d'accès aléatoire physique dans des communications de réseau non terrestre

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019161044A1 (fr) * 2018-02-14 2019-08-22 Idac Holdings, Inc. Accès aléatoire dans un réseau non terrestre
WO2019195457A1 (fr) * 2018-04-03 2019-10-10 Idac Holdings, Inc. Avance temporelle pour une communication de réseau non terrestre
WO2020182006A1 (fr) * 2019-03-11 2020-09-17 Mediatek Inc. Synchronisation de transmission en liaison montante destinée à des réseaux non terrestres

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019161044A1 (fr) * 2018-02-14 2019-08-22 Idac Holdings, Inc. Accès aléatoire dans un réseau non terrestre
WO2019195457A1 (fr) * 2018-04-03 2019-10-10 Idac Holdings, Inc. Avance temporelle pour une communication de réseau non terrestre
WO2020182006A1 (fr) * 2019-03-11 2020-09-17 Mediatek Inc. Synchronisation de transmission en liaison montante destinée à des réseaux non terrestres

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On Random Access in NTN", 3GPP DRAFT; R2-2007715, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051912342 *
OPPO: "NTN control procedure for physical layer", 3GPP DRAFT; R1-1910386, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 5 October 2019 (2019-10-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051789191 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4091387A4 (fr) * 2020-02-05 2024-06-26 MediaTek Singapore Pte. Ltd. Procédé et appareil pour une opération d'avance temporelle de canal d'accès aléatoire physique dans des communications de réseau non terrestre

Also Published As

Publication number Publication date
TW202234938A (zh) 2022-09-01

Similar Documents

Publication Publication Date Title
US20220232503A1 (en) Method of channel scheduling for narrowband internet of things in non-terrestrial network and user equipment using the same
US11985662B2 (en) Method and apparatus for transmission timing enhancement for different numerologies in NTN
WO2022052917A1 (fr) Rapport d'avance temporelle spécifique à un équipement utilisateur dans un réseau non terrestre
CN114930742A (zh) 非地面网络中的定时提前调整方法及相关设备
US11864142B2 (en) User equipment and method for timing alignment
US20230116580A1 (en) Method and related device for operating in a non-terrestrial network (ntn)
US20230291504A1 (en) Method and user equipment for constructing harq-ack codebook
US20220124660A1 (en) Mac-ce command action timing control in non-terrestrial networks
US20220312283A1 (en) Method of handover procedure and related device
US20220369264A1 (en) User equipment and method for timing alignment
WO2023011524A1 (fr) Procédé de surveillance de signal de référence de suivi et dispositif associé
WO2021249206A1 (fr) Procédé de communication sans fil et équipement d'utilisateur pour transmission d'un prach ul
WO2022083705A1 (fr) Équipement utilisateur et procédé de gestion de synchronisation de transmission
CN116158158A (zh) 非地面网络中的mac-ce命令动作时序控制
EP4160938A1 (fr) Équipement utilisateur et procédé pour maintenir une synchronisation de liaison montante (ul) dans un réseau non terrestre (ntn)
WO2021164703A1 (fr) Procédé d'obtention d'une synchronisation de transmission de liaison montante et dispositif associé
US20220338241A1 (en) Method and user equipment for hybrid automatic repeat request process identity selection
WO2022052989A1 (fr) Procédé et équipement d'utilisateur dans un réseau non terrestre
WO2021088994A1 (fr) Procédé et appareil de correction de fréquence en liaison montante
US20230164721A1 (en) Methods and apparatus for triggering a scheduling request in non-terrestrial networks
US20220311558A1 (en) Method and user equipment for hybrid automatic repeat request operation
WO2022199687A1 (fr) Procédé et équipement utilisateur pour opération de rétroaction de demande de répétition automatique hybride

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: 21882119

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21882119

Country of ref document: EP

Kind code of ref document: A1