WO2024035159A1 - Procédé et appareil associés à une avance temporelle dans un système de communication sans fil - Google Patents

Procédé et appareil associés à une avance temporelle dans un système de communication sans fil Download PDF

Info

Publication number
WO2024035159A1
WO2024035159A1 PCT/KR2023/011836 KR2023011836W WO2024035159A1 WO 2024035159 A1 WO2024035159 A1 WO 2024035159A1 KR 2023011836 W KR2023011836 W KR 2023011836W WO 2024035159 A1 WO2024035159 A1 WO 2024035159A1
Authority
WO
WIPO (PCT)
Prior art keywords
tag
time alignment
alignment timer
index
ssb
Prior art date
Application number
PCT/KR2023/011836
Other languages
English (en)
Korean (ko)
Inventor
고성원
고현수
강지원
Original Assignee
엘지전자 주식회사
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 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2024035159A1 publication Critical patent/WO2024035159A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • This specification relates to a method and device related to timing advance in a wireless communication system.
  • Mobile communication systems were developed to provide voice services while ensuring user activity.
  • the mobile communication system has expanded its scope to include not only voice but also data services.
  • the explosive increase in traffic is causing a shortage of resources and users are demanding higher-speed services, so a more advanced mobile communication system is required. .
  • next-generation mobile communication system The requirements for the next-generation mobile communication system are to support explosive data traffic, a dramatic increase in transmission rate per user, a greatly increased number of connected devices, very low end-to-end latency, and high energy efficiency.
  • dual connectivity massive MIMO (Massive Multiple Input Multiple Output), full duplex (In-band Full Duplex), NOMA (Non-Orthogonal Multiple Access), and ultra-wideband (Super)
  • massive MIMO Massive Multiple Input Multiple Output
  • full duplex In-band Full Duplex
  • NOMA Non-Orthogonal Multiple Access
  • Super ultra-wideband
  • M-DCI based M-TRP operation Multiple-DCI based Multiple-Transmission and Reception point operation
  • differences in propagation delay, slot boundary, and inter-UE panel delay may occur between target TRPs of uplink transmission within CC/BWP.
  • this phenomenon can occur more significantly in non-ideal backhaul operations where coordination between TRPs is not achieved.
  • uplink timing needs to be determined differently for each TRP.
  • the operation of connecting/corresponding TAG to the TCI state of unified TCI e.g. joint TCI state, separate TCI state (DL TCI state or UL TCI state) has been agreed upon.
  • time alignment timers related to multiple TAGs are used, ambiguity may arise in uplink time alignmet management operations according to the existing method. For example, the operation of releasing UL/DL settings based on the expiration of the time alignment timer related to the TAG (PTAG) (e.g., release operation of PUCCH/SRS, DL assignment, UL grant, and clear operation of PUSCH resource) ) is performed. At this time, it is unclear whether the operation is performed based on the expiration of any timer among the plurality of timers (e.g., i) expiration of each timer, ii) expiration of a specific timer among the plurality of timers, or iii) expiration of all timers. expiration).
  • PTAG time alignment timer related to the TAG
  • the purpose of this specification is to resolve the ambiguity of the operation related to the expiration of the Time Alignment Timer in the management of TRP-specific TAs and to propose a method to minimize the impact of the operation on UL/DL.
  • the UE selects a random SSB (SSB index) and transmits a random access preamble based on the SSB index.
  • This operation is not efficient in acquiring/managing TRP-specific TA.
  • the Time Alignment Timer for the TA e.g., the first TA
  • TRP 1 e.g., the first CORESET pool index
  • the SSB index related to TRP 2 (or the DL transmission beam of TRP 2) may be selected. In this case, it may be difficult to obtain TA for TRP 1 or an inaccurate TA may be obtained.
  • Another purpose of this specification is to propose a method for solving the above-mentioned problems.
  • a method performed by a terminal in a wireless communication system includes receiving configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs), Timing Advance Group (TAG) ) and releasing settings related to uplink transmission based on expiration of a Time Alignment Timer related to the TAG.
  • COntrol REsource SETs CORESETs
  • TAG Timing Advance Group
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • the settings related to the uplink transmission may be related to at least one of i) a physical uplink control channel (PUCCH) and/or ii) a sounding reference signal (SRS).
  • PUCCH physical uplink control channel
  • SRS sounding reference signal
  • the PUCCH for i) all serving cells or ii) serving cells belonging to the first TAG may be released.
  • the SRS may be released for i) all serving cells or ii) serving cells belonging to the first TAG.
  • PUSCH physical uplink shared channel
  • the PUSCH resource may be related to semi-persistent CSI reporting.
  • uplink transmission except Random Access Preamble transmission and MsgA transmission may not be performed.
  • the method may further include receiving downlink control information (DCI) and transmitting a random access preamble.
  • DCI downlink control information
  • the DCI may include information related to PDCCH (Physical Downlink Control Channel) order.
  • PDCCH Physical Downlink Control Channel
  • a random access procedure may be initiated according to the PDCCH order.
  • the DCI may include a Synchronization Signal/Physical Broadcast Channel Block index (SSB index) related to the PDCCH order.
  • SSB index Synchronization Signal/Physical Broadcast Channel Block index
  • the SSB index related to the PDCCH order may be included in i) a first SSB group related to the first CORESET pool index or ii) a second SSB group related to the second CORESET pool index.
  • RSRP Reference Signal Received Power
  • the random access preamble may be transmitted based on the SSB index related to the PDCCH order.
  • the SSB based on the SSB index related to the PDCCH order may be related to at least one contention-free random access resource (Contention-Free Random Access (CFRA) resource).
  • CFRA Contention-Free Random Access
  • RSRP Reference Signal Received Power
  • the random access preamble may be transmitted based on the SSB index in the first SSB group or the second SSB group to which the SSB index related to the PDCCH order belongs.
  • the SSB based on the SSB index in the first SSB group or the second SSB group may be related to at least one contention-based random access (CBRA) resource.
  • CBRA contention-based random access
  • the second TA associated with the second TAG may be determined based on i) the first TA associated with the first TAG and ii) an offset value.
  • the method further includes receiving a Timing Advance Command.
  • the timing advance command may be related to the first TAG or the second TAG.
  • Timing advance (TA) for uplink timing can be determined with a specific TA.
  • the specific TA may be i) a first TA related to the first TAG or ii) a TA configured for the specific serving cell.
  • a terminal operating in a wireless communication system includes one or more transceivers, one or more processors, and operably connectable to the one or more processors, based on execution by the one or more processors. , including one or more memories that store instructions that configure the one or more processors to perform operations.
  • the operations include receiving configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs), receiving configuration information related to a Timing Advance Group (TAG), and time alignment related to the TAG. It includes releasing settings related to uplink transmission based on the expiration of a timer (Time Alignment Timer).
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • a device includes one or more memories and one or more processors functionally connected to the one or more memories.
  • the one or more memories include instructions that configure the one or more processors to perform operations based on execution by the one or more processors.
  • the operations include receiving configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs), receiving configuration information related to a Timing Advance Group (TAG), and time alignment related to the TAG. It includes releasing settings related to uplink transmission based on the expiration of a timer (Time Alignment Timer).
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • One or more non-transitory computer-readable media stores one or more instructions.
  • One or more instructions executable by one or more processors configure the one or more processors to perform operations.
  • the operations include receiving configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs), receiving configuration information related to a Timing Advance Group (TAG), and time alignment related to the TAG. It includes releasing settings related to uplink transmission based on the expiration of a timer (Time Alignment Timer).
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • a method performed by a base station in a wireless communication system includes transmitting configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs) and a Timing Advance Group (Timing Advance Group, TAG) and transmitting setting information related to it.
  • COntrol REsource SETs COntrol REsource SETs, CORESETs
  • TAG Timing Advance Group
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • a base station operating in a wireless communication system includes one or more transceivers, one or more processors, and operably connectable to the one or more processors, and based on the execution by the one or more processors Thus, it includes one or more memories that store instructions that configure the one or more processors to perform operations.
  • the operations include transmitting configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs) and transmitting configuration information related to a Timing Advance Group (TAG).
  • COntrol REsource SETs COntrol REsource SETs, CORESETs
  • TAG Timing Advance Group
  • CORESETs based on two different control resource set pool indexes (CORESET pool indexes) are set.
  • the TAG includes i) a first TAG associated with a first CORESET pool index and ii) a second TAG associated with a second CORESET pool index.
  • the time alignment timer includes i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • the settings related to the uplink transmission are released based on expiration of the first time alignment timer.
  • a release operation according to the expiration of a time alignment timer is limitedly performed based on the expiration of a timer related to the first CORESET pool index among a plurality of time alignment timers.
  • the random access preamble is transmitted to the first SSB to which the SSB index related to the PDCCH order belongs. It is transmitted based on the SSB index within the group or the second SSB group.
  • FIG. 1 illustrates MAC RAR according to an embodiment of the present disclosure.
  • Figure 2 illustrates Timing Advance Command MAC CE according to an embodiment of the present specification.
  • FIG. 3 is a flowchart illustrating a method performed by a terminal in a wireless communication system according to an embodiment of the present specification.
  • FIG. 4 is a flowchart illustrating a method performed by a base station in a wireless communication system according to another embodiment of the present specification.
  • Figure 5 is a diagram showing the configuration of a first device and a second device according to an embodiment of the present specification.
  • downlink refers to communication from the base station to the terminal
  • uplink refers to communication from the terminal to the base station
  • DL downlink
  • UL uplink
  • the transmitter may be part of the base station and the receiver may be part of the terminal.
  • the transmitter may be part of the terminal and the receiver may be part of the base station.
  • the base station may be represented as a first communication device
  • the terminal may be represented as a second communication device.
  • a base station (BS) is a fixed station, Node B, evolved-NodeB (eNB), Next Generation NodeB (gNB), base transceiver system (BTS), access point (AP), and network (5G).
  • eNB evolved-NodeB
  • gNB Next Generation NodeB
  • BTS base transceiver system
  • AP access point
  • 5G network
  • the terminal may be fixed or mobile, and may include UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), and AMS (Advanced Mobile).
  • UE User Equipment
  • MS Mobile Station
  • UT user terminal
  • MSS Mobile Subscriber Station
  • SS Subscriber Station
  • AMS Advanced Mobile
  • MTC Machine-Type Communication
  • M2M Machine-to-Machine
  • D2D Device-to-Device
  • vehicle robot
  • AI module drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.
  • the M-TRP transmission method in which M TRPs transmit data to one terminal (User equipment, UE), includes eMBB M-TRP transmission, which is a method to significantly increase the transmission rate, and URLLC M-TRP, a method to increase reception success rate and reduce latency.
  • TRP transmission can be divided into two types.
  • the M-TRP (multiple TRP) transmission method is i) M-DCI (multiple DCI) based M-TRP transmission in which each TRP transmits a different DCI and ii) one TRP It can be divided into S-DCI (single DCI) based M-TRP transmission method that transmits DCI.
  • M-DCI based MTRP PDSCH transmission This is a method in which each TRP schedules and transmits PDSCH through DCI. That is, TRP 1 transmits PDSCH 1 through DCI 1 and TRP 2 transmits PDSCH 2 through DCI 2. If PDSCH 1 and PDSCH 2 overlap on the same frequency and time resource, two PDSCHs are received for the same RE, thereby increasing resource efficiency and increasing transmission capacity.
  • the R16 standard introduced the CORESET pool, which is a group of several CORESETs, and TRP 1 transmits the PDCCH through the CORESET belonging to CORESET pool 0, and the PDSCH scheduled by the corresponding PDCCH is also transmitted by TRP 1.
  • TRP 2 transmits PDCCH through CORESET belonging to CORESET pool 1, and TRP 2 also transmits the PDSCH scheduled by the corresponding PDCCH.
  • PUSCH can also be scheduled by a specific TRP to transmit PUSCH to the UE through CORESET belonging to each COERSET pool.
  • For PUCCH some PUCCH resources are scheduled by TRP 1 and receive UCI, and the remaining PUCCH resources are scheduled by TRP 2 and receive UCI.
  • the channels scheduled/used by each TRP are TDM each other so that no overlap occurs, so an increase in transmission capacity cannot be expected.
  • the UE can transmit independent PUSCH/PUCCH for each of TRPs 1 and 2.
  • the UE recognizes the PUSCH (or PUCCH) scheduled by the DCI received through different CORESETs (or CORESETs belonging to different CORESET groups) as a PUSCH (or PUCCH) transmitted to different TRPs, or as a PUSCH (or PUCCH) transmitted to different TRPs. (or PUCCH).
  • the method for UL transmission e.g. PUSCH/PUCCH
  • PUSCH/PUCCH can also be applied to UL transmission (e.g. PUSCH/PUCCH) transmitted to different panels belonging to the same TRP.
  • CORESET group ID (or COERSET pool index with the same meaning) described/mentioned in this specification may mean an index / identification information (e.g. ID) for distinguishing CORESET for each TRP/panel.
  • the CORESET group may be an index / identification information (e.g. ID) to distinguish the CORESET for each TRP/panel / a group / union of the CORESETs distinguished by the CORESET group ID, etc.
  • CORESET group ID may be specific index information defined within CORSET configuration.
  • a CORESET group can be set/indicated/defined by an index defined within the CORESET configuration for each CORESET.
  • CORESET group ID may mean an index/identification information/indicator, etc.
  • the CORESET group ID for distinction/identification between CORESETs set/related to each TRP/panel, and the CORESET group ID described/mentioned in this specification is for each TRP/panel. It may be expressed in place of a specific index / specific identification information / specific indicator for distinction / identification between CORESETs set / related to.
  • the CORESET group ID that is, a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated with each TRP / panel, is used for higher layer signaling (e.g. RRC siganling) / L2 signaling (e.g. MAC -CE) / Can be set/instructed through L1 signaling (e.g. DCI), etc.
  • PDCCH detection may be set/instructed to be performed for each TRP/panel on a CORESET group basis, and/or uplink control information (e.g. CSI, HARQ-A/ N, SR) and/or uplink physical channel resources (e.g. PUCCH/PRACH/SRS resources) may be set/instructed to be managed/controlled separately, and/or scheduled for each TRP/panel on a per CORESET group basis.
  • HARQ A/N process/retransmission
  • PDSCH/PUSCH etc.
  • the ControlResourceSet IE (information element), which is a higher layer parameter, is used to set a time/frequency control resource set (CORESET).
  • the control resource set (CORESET) may be related to detection and reception of downlink control information.
  • the ControlResourceSet IE may include CORESET-related ID (e.g., controlResourceSetID)/index of CORESET pool for CORESET (e.g., CORESETPoolIndex)/time/frequency resource settings of CORESET/TCI information related to CORESET, etc.
  • the index of the CORESET pool (e.g. CORESETPoolIndex) may be set to 0 or 1.
  • CORESET group may correspond to CORESET pool
  • CORESET group ID may correspond to CORESET pool index (e.g. CORESETPoolIndex).
  • ControlResourceSet i.e. CORESET
  • RRC Radio Resource Control
  • Uplink frame number i Transmission of uplink frame number i from a terminal (User Equipment, UE) occurs earlier than the start of the corresponding downlink frame at the terminal. You have to start earlier.
  • UE User Equipment
  • Uplink timing (e.g., uplink frame) related to can be based on Table 1 below.
  • N TA and N TA,offset can be set/applied as follows.
  • N TA 1) Set via RAR (Random access response), 2) Set via Timing advance command (MAC-CE)
  • N TA,offset 1) Set a specific value for each serving cell, 2) Apply a predefined value to the serving cell according to the duplex mode/FR.
  • the terminal may receive configuration information (e.g., ServingCellConfigCommon Information) including information about N TA,offset from the base station.
  • the configuration information may be received based on RRC signaling. Table 2 below illustrates the setting information.
  • the terminal can apply the predefined value of N TA,offset according to the duplex mode (TDD/FDD)/FR to the serving cell.
  • Table 3 illustrates the value of N TA,offset .
  • the terminal may receive RAR from the base station.
  • N TA may be determined/set based on the RAR.
  • the RAR may include a timing advance command.
  • the timing advance command indicates an index value (eg, index value TA) related to timing adjustment.
  • N TA can be determined based on the index value (see Table 5 below).
  • the RAR may be based on MAC RAR.
  • FIG. 1 illustrates MAC RAR according to an embodiment of the present disclosure.
  • MAC RAR may include R (Reserved bit), Timing Advance Command, UL Grant, and Temporary C-RNTI. Table 4 below illustrates the MAC payload of the MAC RAR.
  • Table 5 illustrates transmission timing adjustments based on the Timing advance command.
  • N TA may be set/determined based on MAC-CE. Specifically, N TA can be determined based on Timing Advance Command MAC CE.
  • the Timing Advance Command MAC CE may include a timing advance command. The decision of N TA based on the above timing advance command is the same as described in Case 1, so redundant explanation is omitted (see Table 5).
  • Timing Advance Command MAC CE will be described with reference to FIG. 2.
  • Figure 2 illustrates Timing Advance Command MAC CE according to an embodiment of the present specification.
  • Timing Advance Command MAC CE may include a TAG ID and Timing Advance Command.
  • Table 6 below illustrates the payload of the Timing Advance Command MAC CE.
  • Timing Advance Group refers to a group of serving cells that use the same Timing Advance value.
  • Table 7 illustrates the definition of TAG and setting information related to TAG.
  • Uplink Time Alignment can be performed based on Table 8 below.
  • Multi-TRP Timing Advance, etc.
  • the contents examined above can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical characteristics of the methods proposed in this specification.
  • the methods described below are divided for convenience of explanation, and it goes without saying that some components of one method may be replaced with some components of another method or may be applied in combination with each other.
  • timing advance (TA) setting for uplink transmission of the base station to the terminal to compensate for propagation delay between the base station and the terminal can be performed through higher layer signaling. Additionally, TA for specific cell(s) can be set/managed separately through the concept/definition of timing advance group (TAG).
  • TAG timing advance group
  • the TA (TA value) may be based on the description in FIG. 2 and the content described in the TA (Timing advance) related procedure described above.
  • the base station manages the UE TA value through the values N TA and N TA,offset .
  • the base station can set N TA as follows. You can set N TA through i) RAR MAC CE or ii ) TA command MAC CE (Timing Advance Command MAC CE). Additionally, the base station can use the concept of TAG (Timing Advance Group) to set up to four TAGs for a specific cell or cell combination in the terminal.
  • TAG Tuiming Advance Group
  • the base station can perform update/manage of N TA values for each TAG. In other words, the N TA value related to the uplink timing of the terminal can be determined/set for each TAG based on the RAR MAC CE/TA command MAC CE.
  • the base station in order to support different TA values of the terminal according to the target TRP, i) the base station sets two TRP-specific values in a specific CC/BWP for N TA (or/and N TA,offset ) values. or ii) the base station uses a separate parameter (eg, N TA ,TRP1 and/or N TA, TRP2) to set/give a TRP-specific TA offset value in addition to the N TA or/or N TA, offset value. can be set in a specific CC/BWP through MAC CE signaling.
  • the TA offset by the above separate parameter may need to be additionally subtracted/added from the calculation of the existing TA value of the terminal.
  • the two TA values managed by methods i or/and ii can be expressed as TA1 (or first TA) and TA2 (or second TA).
  • two TA values may correspond to two TAGs.
  • TA1 corresponding to TRP1 may be related to TAG 1
  • TA2 corresponding to TRP2 may be related to TAG 2.
  • each TRP can be distinguished based on the CORESET pool index associated with the CORESET(s) existing within the BWP. Based on the CORESET pool index, each TRP can be divided into i) a TRP performing DL transmission (i.e., PDCCH, PDSCH) or/and ii) a target TRP for UL transmission.
  • a TRP performing DL transmission i.e., PDCCH, PDSCH
  • ii a target TRP for UL transmission.
  • CORESET 0 and 1 with CORESET pool index 0 set may correspond to TRP 1
  • CORESET 2 and 3 with CORESET pool index 1 set may correspond to TRP 2.
  • the base station sets a specific reference RS that it wants to use as a common beam for the DL/UL reception/transmission beam of the terminal to DL/UL joint TCI state and/or DL.
  • /UL can be indicated dynamically using a separate TCI state.
  • the DL/UL joint TCI state may be based on the joint TCI state set for UL and DL operations.
  • the joint TCI state can be set based on dl-OrJointTCI-StateList.
  • DL/UL separate TCI state may be based on DL TCI state and/or UL TCI state.
  • the DL TCI state can be set based on dl-OrJointTCI-StateList and the UL TCI state can be set based on ul-TCI-ToAddModList.
  • TCI state (e.g. joint/DL TCI state) can be indicated/set based on dl-OrJoint-TCIStateList in PDSCH-config.
  • dl-OrJoint-TCIStateList i) provides a list of up to 128 TCI states (explicitlist -> dl-OrJointTCI-StateToAddModList), or ii) a serving cell where the list of TCI states (dl-OrJointTCI-StateToAddModList) is defined, and (DL/UL)BWP can be indicated (unifiedTCI-StateRef-> ServingCellAndBWP-Id).
  • the TCI state (e.g.
  • joint/DL TCI state may provide a reference RS for quasi co-location of DM-RS of PDSCH, DM-RS of PDCCH, and CSI-RS.
  • the TCI state (e.g., joint TCI state) includes dynamic grant based PUSCH (dynamic grant based PUSCH), configured grant based PUSCH (configured grant based PUSCH), PUCCH resources, and uplink transmission spatial filter (UL Tx spatial filter) for SRS.
  • a reference RS can be provided to determine .
  • UL TCI state can be indicated/set by ul-TCI-StateList in BWPUplinkDedicated.
  • ul-TCI-StateList i) provides a list of up to 64 UL TCI states (explicitlist -> ul-TCI-ToAddModList), or ii) a serving cell and UL BWP where UL TCI states applicable to the corresponding UL BWP are defined. can be indicated (unifiedTCI-StateRef-> ServingCellAndBWP-Id).
  • the reception/transmission beam of a DL/UL channel/RS that is not a common beam target can be set as follows. Based on RRC and MAC CE signaling, the TCI state of the unified TCI framework can be set for each channel/RS.
  • M/N means the number of DL common beams (M) and/or the number of UL common beams (N).
  • TCI states and source/target TRP can have a connection relationship.
  • two or more TCI states corresponding to M/N>1 may have a connection relationship with the CORESET pool index.
  • the two TA values for multiple TRP can be set/indicated by higher layer signaling such as MAC CE, similar to existing standards.
  • multiple TA values can be connected/corresponding to two or more TCI states corresponding to M/N>1.
  • the TCI state set/indicated may correspond to TA2 (e.g., TAG 2 or TA2 for TAG 2).
  • a specific payload may be included/added/defined in the MAC CE to set/give/activate TA values to each of two or more TCI states corresponding to M/N>1.
  • the target TCI state(s) (group) for assigning each TA value (e.g., TA1 and TA2).
  • Operations/methods/terms according to embodiments of the present specification described later may be based on Table 10.
  • methods/operations/terms according to embodiments of the present specification described later may be interpreted/changed/applied based on Table 10.
  • multiple TA values may mean multiple TAGs (Timing Advance Groups) or multiple TAG IDs.
  • One TA value may mean one TAG (TAG ID).
  • multiple TA values may mean TA values corresponding to multiple TAGs (multiple TAG IDs).
  • One TA value is the TA value (Table 1) for one TAG (TAG ID). ) can mean.
  • the two TRP-specific TA values (e.g., two TAGs or TAs corresponding to two TAGs) for a specific TCI state(s) (group) ) can be connected/corresponding.
  • the terminal uses the TRP-specific TA value connected to each TCI state in UL transmission using each TCI state.
  • UL transmission can be performed using UL transmission.
  • the timing of UL transmission based on the first TCI state is determined based on the TA (e.g., the first TAG or the first TA for the first TAG) associated with the first TCI state
  • the timing of the UL transmission based on the first TCI state is determined based on the second TCI state.
  • the timing of the based UL transmission may be determined based on the TA associated with the second TCI state (eg, the second TAG or the second TA for the second TAG).
  • UL spatialRelationInfo or/and reference RS of UL TCI cannot be applied in FR 1 (Frequency Range 1).
  • FR 1 Frequency Range 1
  • the UE capability for spatialRelation of the terminal can be defined as shown in Table 11 below.
  • '/' may be interpreted as 'and', 'or', or 'and/or' depending on the context.
  • the terminal can receive unified TCI settings corresponding to M/N>1 (in FR1 operation). For example, the terminal can receive configuration information for two or more unified TCI states from the base station.
  • the two or more unified TCI states include i) two or more joint TCI states (two or more joint TCI states), ii) two or more DL TCI states (two or more DL TCI states), and /or ii) may include at least one of two or more UL TCI states.
  • UL related TCI state (e.g., DL/UL) connected to/corresponding to each of the two CORESET pool indexes joint TCI state and/or DL/UL separate TCI state) may be set/instructed.
  • the terminal may receive configuration information for a plurality of CORESETs from the base station. CORESETs based on two CORESET pool indexes can be set based on the configuration information.
  • the terminal may receive information indicating two UL related TCI states (e.g., two joint TCI states or two UL TCI states) connected/corresponding/related to the two CORESET pool indexes from the base station.
  • Information indicating the two UL related TCI states may be received based on at least one of DCI, MAC CE, or RRC messages.
  • Two TRP-specific TA values may be connected/corresponding to the two UL related TCI states. Additionally, the power control parameter set set in each of the two UL related TCI states is, respectively, in M-TRP UL transmission (e.g., M-TRP PUSCH/PUCCH repetition) (for S-DCI based M-TRP operation) It can be used as a power control parameter set for target TRP.
  • M-TRP UL transmission e.g., M-TRP PUSCH/PUCCH repetition
  • S-DCI based M-TRP operation for S-DCI based M-TRP operation
  • TCI states for setting/instructing two TAs/PC parameter sets can be set/used as follows.
  • the reference RS corresponding to QCL type-D or/and UL spatialRelationInfo may not be set in the two TCI states.
  • the referenceSignal field (in QCL-Info) may not exist in each TCI state.
  • the terminal may not expect the referenceSignal field (in QCL-Info) to be set in each TCI state.
  • the terminal omits/ignores/overrides the reference RS to set each target TRP (e.g., first/ UL transmission can be performed using only TA/PC information corresponding to second TCI or CORESET pool index 0/1).
  • the terminal can determine TA/PC information corresponding to each target TRP (e.g., each TRP among two target TRPs) based on the two TCI states.
  • the terminal can perform UL transmission for each target TRP based on the TA information/PC information.
  • UL transmission timing e.g., uplink frame
  • TA information e.g., TAG or TA value for the TAG
  • UL transmission power for each target TRP may be determined based on PC information (e.g., one or more PC parameters).
  • the TCI state can be set/indicated to RRC, MAC CE, or/and DCI, similar to existing Rel-17 operation.
  • the base station can utilize i) DL(/UL) grant DCI or ii) DL(/UL) grant DCI without data scheduling.
  • the base station can dynamically indicate the TCI state for each target TRP through the TCI field of the corresponding DCI. For example, when a TCI indication is performed through DCI as above in a CORESET with a specific CORESET pool index, the terminal sends the corresponding TCI to the reception/transmission of the DL/UL channel/RS connected/corresponding to the CORESET pool index. You can utilize it.
  • the terminal can transmit Ack (/Nack) after receiving DCI (via PUCCH and/or PUSCH) (e.g., Use ACK/NACK mechanism analogous to that for SPS PDSCH release with both type-1 and type-2 HARQ-ACK codebook).
  • the terminal can skip Ack (/Nack) transmission.
  • the omission of the Ack (/Nack) transmission is based on the following technical considerations.
  • the base station checks whether the terminal has properly received the TCI state containing beam information (e.g. reference RS) for reception/transmission of the terminal indicated by DCI. Afterwards, the base station can utilize its transmission/reception beam corresponding to the indicated TCI information for subsequent DL/UL transmission/reception.
  • the indication for the TCI state that does not include the terminal's reception/transmission beam information allows the base station to set two TAs (e.g., two TAGs or two TAs corresponding to two TAGs) and two PCs (e.g., two parameter sets).
  • /It is for instructions. Whether the instruction to the TA/PC has been successfully transmitted can be determined through subsequent transmission from the corresponding terminal. Specifically, after the base station receives the UL transmission of the subsequent terminal, the base station can determine whether the TA/PC instruction by the preceding DCI was successfully delivered to the terminal and the terminal performed UL transmission in accordance with the instruction. there is.
  • the terminal may omit Ack (/Nack) transmission for the indication of the TCI state (an indication of the TCI state that does not include the terminal's reception/transmission beam information).
  • the beamAppTime parameter can be set based on PDSCH-config.
  • the beamAppTime parameter indicates the first slot to which the unified TCI indicated by DCI is applied.
  • the beamAppTime parameter may indicate the number of symbols (Y) (e.g., n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336).
  • the first slot may be a slot at least Y symbols after the last symbol of the ack (acknowledgment of joint or separate DL/UL beam indication).
  • the BAT can be applied as a setting value for when UL TA/PC should be applied. Or/and, since the TCI state is unrelated to beam application, the terminal may not expect BAT to be set, or may expect the BAT value to be set to 0. As a specific example, it may be assumed that unified TCI states for FR1 are indicated by DCI (e.g., DL grant DCI, UL grant DCI, DCI without DL grant, or DCI without UL grant). Since the indicated unified TCI states are unrelated to beam application, transmission of HARQ-ACK information for the DCI can be omitted.
  • DCI e.g., DL grant DCI, UL grant DCI, DCI without DL grant, or DCI without UL grant
  • the timing (eg, symbol, slot, subframe, or frame) for application of the unified TCI states indicated by the beamAppTime parameter cannot be determined. In this case, even if the beamAppTime parameter is set, the terminal may not use the corresponding beamAppTime parameter. In other words, the terminal can ignore the corresponding beamAppTime parameter.
  • the timing (e.g., symbol, slot, subframe, or frame) for application of the indicated unified TCI states may be determined without applying the beamAppTime parameter.
  • the timing for application of the indicated unified TCI states may be determined regardless of the beamAppTime parameter.
  • the base station can set separate parameter(s) for two TRP-specific TA values or/and two TRP-specific PC parameter sets. Specifically, (in FR1 operation) two TRP-specific TA values or/and two TRP-specific PC parameter sets may be set/connected/corresponding to the separately set parameter(s).
  • the separate parameter(s) may include a TRP-specific TA value.
  • the corresponding parameter(s) can be set as follows i) or ii).
  • a single parameter containing both the first TA value and the second TA value can be set.
  • the first parameter may contain the first TA value and the second parameter may contain the second TA value.
  • the separate parameter(s) may include a TRP-specific PC parameter set.
  • the corresponding parameter(s) can be set as follows i) or ii).
  • a single parameter can be set that includes both the first PC parameter set and the second PC parameter set.
  • the first parameter may include the first PC parameter set and the second parameter may include the second PC parameter set.
  • a specific CORESET pool index and a specific TA value or/and a specific PC parameter set within the single parameter may be connected/corresponding.
  • CORESET pool index 0 and the first TA/first PC parameter set value may be connected
  • CORESET pool index 1 and the second TA/second PC parameter set value may be connected.
  • a specific CORESET pool index and a specific parameter among the two parameters may be connected/corresponding.
  • CORESET pool index 0 and the first parameter can be connected
  • CORESET pool index 1 and the second parameter can be connected.
  • the first TA/PC parameter set value and the second TA/PC parameter set value can be set to specific parameter(s) and connected to a specific CORESET pool index.
  • the terminal may perform UL transmission using the TRP-specific TA value or/and TRP-specific PC parameter set associated with the CORESET pool index.
  • TRP-specific TA values corresponding to the above two TA values or/and the two TRP-specific PC parameter sets can be set/connected/mapping/updated. You can. Accordingly, when transmitting UL associated with a specific CORESET (group), the terminal can perform UL transmission by utilizing the TRP-specific TA value or/and PC parameter set set for the corresponding CORESET.
  • the expression “(a specific parameter and another parameter) can be connected/corresponding” may mean that a specific parameter can be associated with another parameter through RRC/MAC CE/DCI signaling.
  • the embodiments of Proposal 1 to Proposal 2 may be combined and applied to operations between base stations and terminals.
  • the operation of setting a unified TCI (Proposal 1) and the operation of setting separate parameter(s) (Proposal 2) cannot be combined, but other embodiments can be applied in combination.
  • the embodiments of proposal 1 and embodiments of proposal 2 associated with two TRP-specific TA values can be combined and applied to terminal/base station operation.
  • Proposal 3 proposes a method for a UE to perform two TA acquisition without RACH enhancement and a method for setting the TA of the base station
  • Proposal 4 proposes a method for a UE to perform two TA acquisition through RACH enhancement and a method for setting the TA of the base station. Suggestions on how to set it up.
  • the first TA or second TA is connected/corresponding to a specific CORESET pool index, meaning that the first TA or/and second TA is the first TCI state (for common beam operation in the unified TCI framework) or/and the second TCI state. It may mean connected/corresponding to.
  • first TA and second TA may refer to first/second TA values managed to set two TRP-specific TA values within a specific TAG (i.e., one TAG).
  • first TA and second TA may mean the first TA value and second TA value managed in correspondence to different TAGs (first TAG, second TAG) for the same CC (set).
  • the UE can perform RACH transmission with a single (and/or primary/first) TA in a RACH transmission procedure including initial access (e.g., PDCCH ordered RACH, RACH transmitted by TA timer expiration, etc.).
  • the base station can measure first/second TA by receiving the SRS of the following terminal.
  • the following operations can be performed on the aperiodic SRS resource (set) corresponding to dynamic scheduling.
  • the terminal can receive SRS triggering DCI from CORESET with a specific CORESET pool index.
  • the aperiodic SRS resource (set) transmitted by the terminal may be connected/corresponding to the specific CORESET pool index.
  • the following operations can be performed in relation to the periodic/semi-persistent SRS resource (set) transmitted by the terminal through RRC/MAC CE signaling.
  • the base station can (explicitly) set/connect/correspond to the associated CORESET pool index for a specific SRS resource (set). Through this, the terminal/base station can know which CORESET pool index a specific SRS resource (set) has a connection/correspondence relationship with.
  • the base station/terminal can understand that the specific P/SP/AP SRS resource (set) transmitted by the terminal is associated with/corresponds to a specific CORESET pool index.
  • the base station can identify the CORESET pool index associated with/corresponding to a specific P/SP/AP SRS resource (set) transmitted by the terminal.
  • the base station can measure the first TA or/and second TA through the SRS transmitted by the terminal.
  • the first(/primary) TA can be obtained through the existing RACH procedure.
  • the second TA can be obtained through SRS related to CORESET pool index 1 as above.
  • the base station can measure the first TA or/and second TA connected to/corresponding to a specific CORESET pool index through proposal 3-1 above.
  • the base station may set/instruct a TRP-specific TA value (i.e., first/second TA) using the enhanced RAR MAC CE format or/and the enhanced TA command MAC CE.
  • the base station can configure a target CORESET pool index in the enhanced MAC CE format.
  • the TA value associated with/corresponding to the corresponding CORESET pool index can be set/indicated.
  • the enhanced MAC CE format may include a field indicating the target CORESET pool index.
  • the base station may configure the first/second TCI corresponding to M/N>1 for TRP-specific common beam operation as a target in the enhanced MAC CE format.
  • the TA value associated with/corresponding to the first/second TCI can be set/indicated.
  • the enhanced MAC CE format may include a field indicating the target TCI (e.g., first TCI state or second TCi state).
  • the base station may configure a specific joint and/or separate UL TCI state(s) index as a target in the enhanced MAC CE format.
  • the TA value to be applied to the corresponding TCI state(s) can be set/instructed.
  • the TA value in the MAC CE format for setting/indicating the second TA value may be set/defined/indicated differently from the first TA value in the same MAC CE format in terms of TA granularity or/and value range. This is because in M-TRP operation, the difference in UL TA values of different TRPs may differ by more than CP length from the DL timing reference.
  • the granularity of the second TA value can be expressed as a step size slightly larger than the first TA value.
  • the value range of the second TA value can be expressed as a value range that is slightly larger than the first TA value.
  • the base station can set/instruct first/second TA for a specific target CORESET pool index/target common TCI/target TCI state(s).
  • the terminal applies the set/indicated first/second TA value.
  • uplink transmission can be performed.
  • the base station After setting/instructing the TRP-specific TA through Proposal 3-2, the base station can perform update/activation of the TRP-specific TA value by measuring the UE's TRP-specific SRS transmission based on Proposal 3-1.
  • TRP-specific TA measurement For TRP-specific TA measurement, a method that supports TRP-specific RACH transmission may be considered.
  • the base station can perform grouping on the SSB (SS/PBCH block) that the terminal uses for RACH transmission.
  • the base station can connect/correspond to a specific SSB group and a specific CORESET pool index.
  • SSBs corresponding to SSB index 0 ⁇ 31 can be connected/corresponding to CORESET pool index 0
  • SSBs corresponding to SSB index 32 ⁇ 64 can be connected/corresponding to CORESET pool index 1.
  • the SSB index may be the SS/PBCH index of the SS/PBCH block.
  • the base station can configure/instruct to utilize a specific SSB index when configuring/instructing to transmit (PDCCH ordered) RACH to the UE.
  • the RACH may mean random access preamble.
  • the base station may transmit a DCI (e.g., DCI format 1_0) containing information related to the PDCCH order to the terminal.
  • a random access procedure is initiated by the PDCCH order.
  • the terminal transmits a random access preamble to the base station.
  • Information related to the PDCCH order may include SS/PBCH index.
  • the SS/PBCH index may be connected/related to a specific CORESET pool index.
  • the random access preamble may be transmitted based on the SS/PBCH index.
  • the base station can use the RACH to measure the TRP-specific TA associated with/corresponding to each CORESET pool index.
  • the base station instructs (PDCCH ordered) RACH transmission
  • multiple RACH transmission is instructed to the terminal through single PDCCH (e.g., single DCI) transmission so that the terminal can transmit the RACH associated with each CORESET pool index.
  • the single DCI may include information related to the PDCCH order.
  • information related to the PDCCH order may include two SS/PBCH indices.
  • the terminal may transmit two random access preambles to the base station based on the two SS/PBCH indexes.
  • overhead/delay can be reduced with a single PDCCH transmission and the UE can be instructed to transmit all RACHs destined for each TRP.
  • the base station can perform TA measurement for each TRP at once.
  • the connection/correspondence relationship between the specific SSB group and a specific CORESET pool index can be established/defined/regulated by connecting/corresponding to a specific CORESET pool index and PRACH preamble index/RACH occasion/PRACH mask index.
  • DCI e.g., DCI Format 1_0
  • DCI Format 1_0 related to the PDCCH order may include a Random Access Preamble index, SS/PBCH index, and PRACH Mask index. If the value of the Random Access Preamble index is not zero, the PRACH Mask index indicates the RACH occasion associated with the SS/PBCH indicated by the SS/PBCH index.
  • the specific CORESET pool index may be set to connect/correspond to at least one of the PRACH preamble index, PRACH mask index, or RACH occasion.
  • the base station can schedule the UE's RACH transmission according to the PDCCH order through CORESET with a specific CORSET pool index.
  • the terminal may perform RACH transmission corresponding to the SSB connected to/corresponding to the specific CORESET pool index (or such RACH transmission may be forced).
  • the UE can perform RACH transmission based on the CORESET pool index of the CORESET for which the DCI (related to the PDCCH order) was received.
  • the RACH transmission in Proposition 4-1 may not be used for RACH transmission during initial access.
  • the RA procedure may include a 4-step RACH procedure and/or a 2-step RACH procedure.
  • a 4-step RACH procedure i.e. contention-based RACH
  • a 2-step RACH procedure may include Msg A (preamble and PUSCH) transmission and Msg B (RAR) reception operations.
  • the terminal can release UL transmission and transmit RACH.
  • PTAG Primary Timing Advance Group
  • timeAlignmentTimer per TAG
  • This embodiment proposes a method for managing the timeAlignmentTimer corresponding to the TA timer in a TRP-specific manner.
  • the terminal can manage up to two TA timers corresponding to CORESET pool index 0, 1 or/and first and second TA values.
  • each of the two timers may be a timer set in a different TAG for a different TRP.
  • the terminal when the TA timer expires, the terminal transmits a RACH corresponding to a random SSB (e.g., SSB based on one of the SSB indexes).
  • a RACH corresponding to a random SSB e.g., SSB based on one of the SSB indexes.
  • the terminal RACH based on the CORESET pool index associated with/corresponding to the expired TA timer. can be transmitted. That is, the RACH corresponding to the SSB in a connection/correspondence relationship with the corresponding CORESET pool index can be transmitted.
  • the terminal can transmit the RACH for the TRP.
  • the base station can measure the TA value of the terminal from the corresponding TRP and set/instruct/update the TRP-specific TA value to the terminal (as in Proposal 3-2).
  • the UE may not need to perform all predefined UL OOS operations (e.g., RRC release operations, etc. are not performed). If both timers have expired, all predefined UL OOS operations may need to be performed.
  • the UE's specific RACH transmission corresponds to a specific SSB.
  • a specific RACH transmission and a specific CORESET pool index may naturally have a correspondence.
  • the base station can receive a specific RACH that corresponds to a specific CORESET pool index.
  • the base station may transmit the RAR for the corresponding RACH to the terminal based on some CORESETs among the CORESETs having the specific CORESET pool index.
  • some of the CORESETs may be CORESETs with the lowest index among CORESETs for which the corresponding CORESET pool index has been set.
  • the terminal can receive settings for type1-PDCCH CSS set (Common Search Space set) for receiving RAR from the base station.
  • the type1-PDCCH CSS set can be set based on the ra-searchspace of PDCCH-ConfigCommon IE.
  • the RAR may be received based on monitoring PDCCH candidates in a search space set (SS set).
  • SS set search space set
  • Proposal 4-3 proposes a method that allows the UE to receive TRP-specific RAR through not only the type1-PDCCH CSS set but also a separate USS set (UE-specific Search Space set).
  • a method of connecting/configuring the separate USS set and CORESET for receiving the TRP-specific RAR may be considered.
  • Each USS set can be connected/corresponding to a CORESET with a different CORESET pool index.
  • the base station may transmit RAR for RACH for first/primary (and/or corresponding to CORESET pool index 0) TA value measurement through the existing type1-PDCCH CSS set.
  • RAR for RACH for measuring the second (and/or CORESET pool index 1) TA value can be transmitted.
  • a separate RNTI for receiving the TRP-specific RAR may be set in the terminal.
  • the terminal may receive a TRP-specific RAR based on the configuration of a plurality of CSS sets (e.g., configuration of two CSS sets considering 2 TRPs).
  • Each of the two CSS sets can be connected/corresponding to a CORESET with a different CORESET pool index.
  • the MAC CE format transmitted through this TRP-specific RAR may include all settings/instructions for a plurality of TA values within a specific CC/BWP, as in Proposal 3-2 above.
  • the MAC CE format transmitted through the TRP-specific RAR may only include settings/instructions for the TA value associated with/corresponding to the CORESET pool index through which the RAR is transmitted.
  • the terminal specifies the DL timing reference based on reception of the RAR (UL grant DCI) transmitted from CORESET with the corresponding CORESET pool index. /Can be defined.
  • the terminal can apply the TA value indicated from the corresponding DL timing reference.
  • the DL timing reference between TRPs may differ significantly.
  • the base station can indicate to the terminal an appropriate TRP-specific TA value for the DL timing reference for each TRP through the above-described operation.
  • Proposal 5 describes additional embodiments related to Proposal 4. Specifically, the following describes i) an embodiment related to the timer related to two TAs in Proposal 4-2, ii) an embodiment related to RAR corresponding to the TRP-specific RACH transmission in Proposal 4-1 and the corresponding RACH transmission in Proposal 4-3. Let’s look at them in turn.
  • Proposal 4-2 a method for managing TA (TRP-specific TA) for each TRP in a UE-specific CC/BWP in an M-DCI based M-TRP environment was proposed. Specifically, according to Proposal 2, timers related to each TA are managed separately. A method different from the operation of Proposal 4-2 described above may be considered.
  • the above-described UL OOS operation may be performed when the timer of a specific TA value (e.g., first TA value) among two TA values expires. Additionally, this embodiment may assume/consider at least one of the following technical matters.
  • a primary TRP e.g., CORESET pool with CORESET pool index 0
  • the specific TA value may be related to the primary TRP (CORESET pool index 0).
  • the second TA value of the second TRP (i.e., CORESET pool with CORESET pool index 1) can be managed by an offset value from the first TA value of the first TRP (i.e., CORESET pool with CORESET pool index 0).
  • timer i.e. timeAlignmentTimer
  • timeAlignmentTimer can be set only for the first TA value.
  • the UL OOS operation may be performed based on the expiration of a set timer.
  • a timer related to each TA can be set in the terminal. That is, Timers related to multiple TAs can be set in the terminal. For example, a timer (i.e. first/second timeAlignmentTimer) may be set for the first TA value and second TA, respectively.
  • the UL OOS operation may be performed based on the expiration of a specific timer (first timeAlignmentTimer or second timeAlignmentTimer).
  • the UL OOS operation may be based on an operation performed according to the expiration of a timer related to PTAG (or STAG).
  • the UL OOS operation may include operations performed when timeAlignmentTimer expires in Table 8.
  • the terminal can perform a release operation for all UL channels/RSs (of CC/BWP related to the TA value (or related to the TAG)). there is. More specifically, the terminal can perform release and clear operations based on Table 8. Based on the expiration of the above-mentioned timer, the terminal i) releases PUCCH and SRS, and ii) configures downlink assignments, configured uplink grant, and PUSCH resources (e.g. PUSCH resource for semi-persistent CSI reporting can be cleared. Additionally, the terminal may perform RACH transmission to update the expired TA value.
  • PUSCH resources e.g. PUSCH resource for semi-persistent CSI reporting can be cleared.
  • the above proposal can be applied both when the first TA and the second TA are managed in one TAG and when the first TA and the second TA are managed in two different TAGs.
  • TRP-specific RACH transmission can be performed using a specific SSB index in both RACH transmission by higher layer settings (MIB, etc.) and PDCCH ordered RACH transmission.
  • MIB layer settings
  • PDCCH Physical Downlink Control Channel
  • CFRA resource(s) or CBRA resource(s) may be used. This will be described in detail below.
  • RACH (or RA preamble) can be transmitted based on the set/indicated SSB index. More specifically, RACH (or RA preamble) may be transmitted based on contention-free random access (CRFA) resource(s) associated with the set/indicated SSB index.
  • CRFA contention-free random access
  • the RSRP of the SSB based on the SSB index set/indicated for RACH transmission is less than or equal to a specific threshold value (e.g. rsrp-ThresholdSSB).
  • CBRA resources may be used based on fall-back operation.
  • the terminal can select any SSB.
  • RACH (or RA preamble) may be transmitted based on the selected SSB. More specifically, RACH (or RA preamble) may be transmitted based on Contention Based Random Access (CBRA) resource(s) associated with the selected SSB.
  • CBRA Contention Based Random Access
  • obtaining a TRP-specific TA may be difficult because RACH transmission is performed based on a random SSB.
  • a TA other than the TA whose timer has expired may be obtained from the RACH transmission.
  • TRP-specific TA management is not efficient.
  • the operations of [1] and [2] above can be extended and applied to Proposal 4-1 to solve the above-mentioned problem.
  • the terminal when CFRA transmission is configured/instructed (in RACH transmission by higher layer configuration and PDCCH ordered RACH transmission), the terminal can operate as follows.
  • the terminal can operate in the same manner as the existing method. That is, RACH (or RA preamble) can be transmitted based on the set/indicated SSB index.
  • the terminal may operate differently from the existing method. That is, rather than performing RACH transmission by selecting a random SSB, the terminal may perform RACH (or RA preamble) transmission based on a specific SSB index.
  • the specific SSB index may be one of the SSB indexes in the SSB group to which the set/indicated SSB index belongs.
  • the terminal may select a random SSB (SSB index) within the SSB group that includes/corresponds to the set/indicated SSB index and perform RACH transmission based on the selected SSB index.
  • RACH (or RA preamble) is transmitted based on Contention Based Random Access (CBRA) resource(s) associated with the selected SSB within the SSB group containing/corresponding to the set/indicated SSB index. It can be.
  • CBRA Contention Based Random Access
  • RACH transmission can be performed for the group.
  • the base station can obtain the TA value corresponding to the desired TRP.
  • the RSRP of the SSB corresponding to the SSB index indicated in relation to the PDCCH order is less than or equal to the threshold for utilizing CFRA resources, it is based on the SSB index to obtain a TRP-specific TA value, not on any SSB index.
  • RACH transmission may be performed.
  • the following operations may be considered in relation to RAR for the RACH transmission (RACH transmission based on a specific SSB index belonging to a specific SSB group).
  • RAR for RACH transmission related to the specific SSB group may be transmitted/received with a specific (same for each TRP) RNTI in a specific CSS set as in the existing method.
  • RAR based on a specific RNTI may be transmitted (received) in a specific CSS set.
  • RAR for RACH transmission related to the specific SSB group may be transmitted/received in CORESET(s) (SS set) in which the CORESET pool index associated with the group is set, as in Proposal 4-3.
  • CORESET(s) SS set
  • the RAR is set in the CORESET(s) (or the SS set of the CORESET(s)) for which the CORESET pool index associated with the group is set. Can be transmitted (received).
  • a method of indicating the TA value for each TRP may be considered.
  • the operation according to this embodiment takes into account the following technical details.
  • RAR MAC CE and/or timing advance command (TAC) MAC CE when assuming a non-ideal backhaul situation, which is the main scenario of M-DCI based M-TRP, dynamic-level coordination between two TRPs is not performed. Therefore, indication of TA value is required for each TRP. This will be described in detail below.
  • two TAs may be assumed within one TAG (two TAs within single TAG case). In this case, the following operations can be performed.
  • TA value indication/update for the TA value within the target TAG may be performed based on the RAR MAC CE or/and TAC MAC CE associated with each CORESET pool index.
  • the TA value in the target TAG may be a TA value associated with/corresponding to the corresponding CORESET pool index.
  • the TA value in the target TAG may be the TA value of a sub-TAG (or TASG (TA Sub Group)) associated with/corresponding to the corresponding CORESET pool index.
  • the TA value indication/update can be performed only for the TA value.
  • two TAs within two TAGs may be assumed (two TAs within two TAGs case). That is, it can be assumed that different TAs are based on different TAGs. In this case, the following operations can be performed.
  • TA value indication/update may be performed for (or only) the TA value corresponding to the TAG associated with the pool index.
  • the two TA values within the TAG Ambiguity in UE operation arises as to which TA value should be used for UL transmission.
  • at least one of the following operations i) and/or ii) may be performed.
  • the terminal can assume that the index of the pool is 0.
  • the terminal can use the TA value associated with CORESET pool index 0 or the fisrt TA value.
  • the terminal can utilize the set TA value.
  • the first or second TA value to be used in the above case may be defined/set/instructed in advance or by the base station.
  • the two TAs within two TAGs case, among the intersection CC/BWPs (or intersection serving cells) in the CC/BWP combination constituting the first TAG and the CC/BWP combination (serving cell combination) constituting the second TAG.
  • a single CORESET pool is set in a specific CC/BWP (or a specific serving cell)
  • ambiguity in UE operation occurs as to which TA value among the 2 TAG TA values should be used for UL transmission.
  • at least one of the following operations i), ii) and/or iii) may be performed.
  • the terminal can assume that the index of the pool is 0.
  • the terminal can utilize the TA value corresponding to the TAG associated with CORESET pool index 0 or the TA value corresponding to the fisrt TAG.
  • the terminal can utilize the set TA value.
  • the first or second TAG to be used may be defined/set/instructed in advance or by the base station.
  • the first TAG and second TAG may be forced to include the same CC/BWP combination.
  • TAC MAC CE may include both absolute TAC and relative TAC by offset value.
  • Proposals 1 to 5 are applicable to an intra-cell M-DCI based M-TRP environment and an inter-cell M-DCI based M-TRP environment.
  • the operation to enable TRP-specific RACH transmission by performing SSB grouping by CORESET pool index divides SSB into two groups based on the following i) and ii) to determine TRP (CORESET pool index or cell). )-can be extended and applied to the operation of performing RACH transmission.
  • TRP-specific RAR or/and TRP-specific TAC MAC CE operations can also be extended and applied in the inter-cell M-DCI based M-TRP environment.
  • the embodiments of Proposals 3 to 5 may be applied to operations between base stations and terminals in combination with the embodiments of Proposal 1 and the embodiments of Proposal 2, as long as they do not exclude each other.
  • the operation of performing ⁇ TA acquisition without RACH enhancement (Proposal 3) and the operation of performing two TA acquisition through RACH enhancement (Proposal 4, Proposal 5) cannot be combined, but other embodiments can be combined. can be applied.
  • the embodiments of Proposal 3 and the embodiments of Proposals 4 and 5 associated with two TRP-specific TA values can be combined and applied to UE/base station operation.
  • An example of a terminal (or base station) operation based on at least one of the above-described embodiments is as follows.
  • the terminal receives (transmits) unified TCI-related setting information or/and TRP-specific TA/PC-related setting information.
  • the above setting information may be based on the contents of Proposals 1 to 5.
  • the terminal transmits (receives) SRS or/and RACH based on Proposal 3 to Proposal 5 depending on the base station settings.
  • the base station receives the SRS or/and RACH, measures the TRP-specific TA, and then sets/instructs the UE to set/instruct the TRP-specific TA value through MAC CE (RAR or/and TA command) based on Proposal 3 to Proposal 5.
  • the terminal receives (transmits) a message scheduling TRP-specific UL transmission
  • the message may be based on at least one of the first PDCCH (first DCI) and/or the second PDCCH (first DCI)
  • the message may be associated with a specific CORESET pool index or/and a specific CORESET (group)
  • the terminal transmits (receives) a UL channel/RS using TRP-specific TA/PC configuration information.
  • the UL channel/RS may be based on at least one of SRS, PUSCH, PUCCH, or random access preamble, and the UL channel/RS transmission may be performed based on the contents of Proposals 1 to 5.
  • the terminal can manage the TRP-specific TA timer based on the contents of Proposal 4 and Proposal 5.
  • the above terminal/base station operation is only an example, and each operation (or step) is not necessarily essential.
  • Uplink transmission using the TRP-specific TA/PC of the terminal according to the above-described embodiments depends on the terminal/base station implementation method. Operations related to may be omitted or added.
  • the operations of the base station/terminal e.g., operations related to uplink transmission using the TRP-specific TA/PC of the terminal based on at least one of Proposals 1 to 5 will be described later. It may be processed by the device of FIG. 5 (eg, processors 110 and 210 of FIG. 5).
  • the operations of the base station/UE according to the above-described embodiment include at least one processor ( Example: 110, 210 in FIG. 5) may be stored in a memory (e.g., 140, 240 in FIG. 5) in the form of instructions/programs (e.g., instructions, executable code) for driving.
  • a processor Example: 110, 210 in FIG. 5
  • a memory e.g., 140, 240 in FIG. 5
  • instructions/programs e.g., instructions, executable code
  • FIG. 3 is a flowchart illustrating a method performed by a terminal in a wireless communication system according to an embodiment of the present specification.
  • the method performed by the terminal in the wireless communication system includes a step of receiving configuration information related to CORESETs (S310), a step of receiving configuration information related to TAG (S320), and uplink Includes a step (S330) of canceling settings related to transmission.
  • the terminal receives configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs) from the base station.
  • COntrol REsource SETs COntrol REsource SETs, CORESETs
  • CORESETs e.g., first CORESETs and second CORESETs
  • first control resource set pool index and the second control resource set pool index CORESET pool index
  • the terminal receives configuration information related to the timing advance group (TAG) from the base station.
  • TAG timing advance group
  • the configuration information related to the TAG may be configuration information (eg, TAG-Config) based on Table 7 above.
  • the terminal releases settings related to uplink transmission based on the expiration of a time alignment timer related to the TAG.
  • the terminal can perform an operation based on Table 8.
  • the terminal i) releases settings related to uplink transmission (e.g., PUCCH/SRS), and ii) configured downlink assignment(s), configured uplink grant(s). ) and/or PUSCH resources can be cleared.
  • uplink transmission e.g., PUCCH/SRS
  • PUSCH resources can be cleared.
  • the terminal may not perform uplink transmission except for random access preamble transmission and MsgA transmission.
  • the TAG may include i) a first TAG related to the first CORESET pool index and ii) a second TAG related to the second CORESET pool index. This embodiment may be based on Proposal 5-1.
  • the time alignment timer may include i) a first time alignment timer associated with the first TAG and ii) a second time alignment timer associated with the second TAG.
  • Settings related to the uplink transmission may be released based on expiration of the first time alignment timer.
  • the settings related to the uplink transmission are related to at least one of i) a physical uplink control channel (PUCCH) and/or ii) a sounding reference signal (SRS). It can be.
  • PUCCH physical uplink control channel
  • SRS sounding reference signal
  • the first TAG may be Primary Timing Advance Group (PTAG) or Secondary Timing Advance Group (STAG).
  • PTAG Primary Timing Advance Group
  • STAG Secondary Timing Advance Group
  • release operations based on (1) and (2) described above may be performed regardless of the type (PTAG/STAG) of the TAG (i.e., the first TAG) associated with the expired time alignment timer. This will be described in detail below.
  • the PUCCH may be released for i) all serving cells or ii) serving cells belonging to the first TAG.
  • the SRS may be released for i) all serving cells or ii) serving cells belonging to the first TAG.
  • the PUCCH and the SRS for i) all serving cells or ii) serving cells belonging to the first TAG may be released.
  • PUSCH Physical Uplink Shared Channel
  • This embodiment may be based on Proposal 5-1.
  • the PUSCH resource may be related to semi-persistent CSI reporting.
  • the serving cells on which the above-described clear operation is performed may be the same as the serving cells on which the above-described release operation is performed.
  • the clear operation may be performed on i) all serving cells (e.g., the first TAG is a PTAG) or ii) serving cells belonging to the first TAG. It may be performed on cells (e.g., the first TAG is STAG).
  • the clear operation (i.e., regardless of the type of the first TAG) may be performed on i) all serving cells or ii) serving cells belonging to the first TAG.
  • PUSCH physical uplink shared channel
  • uplink transmission except Random Access Preamble transmission and MsgA transmission may not be performed.
  • the serving cell(s) on which UL transmission is not performed may be the same as the serving cells on which the above-described release/clear operation is performed.
  • the first time alignment timer For example, based on the expiration of the first time alignment timer: for all serving cells or serving cells belonging to the first TAG, excluding Random Access Preamble transmission and MsgA transmission. Uplink transmission may not be performed.
  • serving cells may vary based on the type of the first TAG. Specifically, based on the expiration of the first time alignment timer: all serving cells (e.g., if the first TAG is a PTAG) or serving cells belonging to the first TAG (e.g., the first TAG) 1 TAG is a STAG), uplink transmission except random access preamble transmission and MsgA transmission may not be performed.
  • the second TA associated with the second TAG is It may be determined based on i) the first TA related to the first TAG and ii) an offset value. This embodiment may be based on proposal 5-1 above.
  • the method may further include a DCI receiving step and a random access preamble transmitting step.
  • the DCI receiving step and the random access preamble transmitting step may be performed after S330.
  • the terminal receives downlink control information (DCI) from the base station.
  • DCI downlink control information
  • the DCI may include information related to PDCCH (Physical Downlink Control Channel) order.
  • the DCI may include a Synchronization Signal/Physical Broadcast Channel Block index (SSB index) related to the PDCCH order.
  • SSB index may be the SS/PBCH index of the SS/PBCH block.
  • the SSB index related to the PDCCH order may be included in i) a first SSB group related to the first CORESET pool index or ii) a second SSB group related to the second CORESET pool index.
  • Each SSB group may be based on a group based on proposal 4-1 above.
  • the first SSB group may include one or more first SSBs belonging to SSB index 0 to 31
  • the second SSB group may include one or more second SSBs belonging to SSB index 32 to 63. .
  • the DCI may be DCI format 1_0.
  • the DCI format 1_0 may include an SS/PBCH index field.
  • the SS/PBCH index field may indicate the SS/PBCH (or SSB index) used to determine the RACH occasion for PRACH transmission (i.e., random access preamble transmission).
  • a random access procedure may be initiated according to the PDCCH order.
  • a random access procedure may be initiated by the PDCCH order. That is, the DCI related to the PDCCH order can be transmitted from the base station to the terminal.
  • the random access procedure may be a Type-1 random access procedure (4-step RA) or a Type-2 random access procedure (2-step RA).
  • the Type-1 random access procedure involves transmitting a random access preamble (Msg1) on a physical random access channel (PRACH), receiving a random access response (RAR) (Msg2), and PUSCH scheduled by the UL grant of the RAR. may include transmission (Msg3) and PDSCH (Msg4) for contention resolution. If the random access procedure is contention-free random access (CFRA), Msg3 transmission and Msg4 reception operations are omitted.
  • the Type-2 random access procedure may include transmission of a random access preamble and PUSCH (MsgA) and reception of RAR (MsgB).
  • MsgA random access preamble and PUSCH
  • MsgB reception of RAR
  • the terminal transmits a random access preamble to the base station.
  • the random access preamble may be transmitted based on a random access procedure (eg, 4-step RA or 2-step RA) initiated by the PDCCH order.
  • a random access procedure eg, 4-step RA or 2-step RA
  • the random access preamble may be based on Msg1 of the Type-1 random access procedure or MsgA of the Type-2 random access procedure.
  • the random access preamble may be transmitted based on an SSB index related to the PDCCH order or a specific SSB index. This embodiment may be based on proposal 5-2 above.
  • RSRP Reference Signal Received Power
  • the random access preamble may be transmitted based on the SSB index related to the PDCCH order.
  • the SSB based on the SSB index related to the PDCCH order may be related to at least one contention-free random access resource (Contention-Free Random Access (CFRA) resource).
  • CFRA Contention-Free Random Access
  • RSRP Reference Signal Received Power
  • the random access preamble may be transmitted based on the SSB index in the first SSB group or the second SSB group to which the SSB index related to the PDCCH order belongs.
  • the SSB based on the SSB index in the first SSB group or the second SSB group may be related to at least one contention-based random access (CBRA) resource.
  • CBRA contention-based random access
  • the method may further include receiving a timing advance command.
  • the terminal receives a timing advance command from the base station.
  • the timing advance command reception step may be performed after S330.
  • the Timing Advance Command may be received based on a Medium Access Control Control Element (MAC CE) (e.g., Timing Advance MAC CE, FIG. 2) or MAC RAR (FIG. 1).
  • MAC CE Medium Access Control Control Element
  • the timing advance command may be related to the first TAG or the second TAG. This embodiment may be based on proposal 5-2 above.
  • the CORESET pool index of one of the serving cells (e.g., CC/BWPs) belonging to the first TAG and the second TAG is set:
  • Timing advance (TA) for uplink timing can be determined with a specific TA.
  • the specific TA may be i) a first TA related to the first TAG or ii) a TA configured for the specific serving cell.
  • the TA configured for the specific serving cell may be set/defined by the base station or in advance as a first TA associated with the first TAG or a second TA associated with the second TAG.
  • the timing advance command indicates an index related to timing adjustment (see Figure 1, Table 4 and Table 5).
  • the index related to the timing adjustment may refer to the index value T A of Tables 4 and 5.
  • N TA for calculating timing advance (TA) may be indicated based on the index related to the timing adjustment.
  • the TA is in Table 1 It can mean.
  • the TA may be a TRP-specific TA (eg, a first TA or a second TA). Specifically, the TA may be related to a first timing advance group (TAG) or a second timing advance group (TAG).
  • the first TAG (or first TAG ID) may be related to the first CORESET pool index
  • the second TAG (or second TAG ID) may be related to the second CORESET pool index.
  • the terminal 200 may include one or more transceivers 230 and/or one or more memories ( 240) can be controlled.
  • the DCI transmission step, the random access preamble reception step, and the timing advance command transmission step described later correspond to the SS310 to S330, the DCI reception step, the random access preamble transmission step, and the timing advance command reception step described in FIG. Considering the above correspondence, redundant description will be omitted. That is, the detailed description of the base station operation described later can be replaced with the description/embodiment of FIG. 3 corresponding to the corresponding operation.
  • the description/embodiment of S310 to S330 of FIG. 3 may be additionally applied to the base station operation of S410 to S420, which will be described later.
  • the description/embodiment of the DCI reception step, the random access preamble transmission step, and the timing advance command reception step may be additionally applied to the base station operations of the DCI transmission step, random access preamble reception step, and timing advance command transmission step described later. .
  • FIG. 4 is a flowchart illustrating a method performed by a base station in a wireless communication system according to another embodiment of the present specification.
  • the method performed by the base station in a wireless communication system includes a step of transmitting configuration information related to CORESETs (S410) and a step of transmitting configuration information related to TAG (S420). .
  • the base station transmits configuration information related to a plurality of control resource sets (COntrol REsource SETs, CORESETs) to the terminal.
  • COntrol REsource SETs COntrol REsource SETs, CORESETs
  • the base station transmits configuration information related to the timing advance group (TAG) to the terminal.
  • TAG timing advance group
  • settings related to uplink transmission of the terminal may be released.
  • the method may further include a DCI transmission step and a random access preamble reception step.
  • the DCI transmission step and the random access preamble reception step may be performed after S420.
  • the base station transmits downlink control information (DCI) to the terminal.
  • DCI downlink control information
  • the base station receives a random access preamble from the terminal.
  • the method may further include transmitting a timing advance command.
  • the base station transmits a timing advance command to the terminal.
  • the timing advance command transmission step may be performed after S420.
  • Operations based on the above-described S410 to S420, DCI transmission step, random access preamble reception step, and timing advance command transmission step can be implemented by the device of FIG. 5.
  • the base station 100 may use one or more transceivers 130 and/or one or more memories 140 to perform operations based on steps S410 to S420, a DCI transmission step, a random access preamble reception step, and a timing advance command transmission step. You can control it.
  • Figure 5 is a diagram showing the configuration of a first device and a second device according to an embodiment of the present specification.
  • the first device 100 may include a processor 110, an antenna unit 120, a transceiver 130, and a memory 140.
  • the processor 110 performs baseband-related signal processing and may include an upper layer processing unit 111 and a physical layer processing unit 115.
  • the upper layer processing unit 111 can process operations of the MAC layer, RRC layer, or higher layers.
  • the physical layer processing unit 115 can process PHY layer operations. For example, when the first device 100 is a base station device in base station-to-device communication, the physical layer processing unit 115 may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device 100 is the first terminal device in terminal-to-device communication, the physical layer processing unit 115 performs downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. can do. In addition to performing baseband-related signal processing, the processor 110 may also control the overall operation of the first device 100.
  • the antenna unit 120 may include one or more physical antennas, and may support MIMO transmission and reception when it includes a plurality of antennas.
  • the transceiver 130 may include a radio frequency (RF) transmitter and an RF receiver.
  • the memory 140 may store information processed by the processor 110 and software, operating system, and applications related to the operation of the first device 100, and may also include components such as buffers.
  • the processor 110 of the first device 100 is set to implement the operation of the base station in communication between base stations and terminals (or the operation of the first terminal device in communication between terminals) in the embodiments described in this disclosure. It can be.
  • the second device 200 may include a processor 210, an antenna unit 220, a transceiver 230, and a memory 240.
  • the processor 210 performs baseband-related signal processing and may include an upper layer processing unit 211 and a physical layer processing unit 215.
  • the upper layer processing unit 211 can process operations of the MAC layer, RRC layer, or higher layers.
  • the physical layer processing unit 215 can process PHY layer operations. For example, when the second device 200 is a terminal device in communication between a base station and a terminal, the physical layer processing unit 215 may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device 200 is a second terminal device in terminal-to-device communication, the physical layer processing unit 215 performs downlink received signal processing, uplink transmitted signal processing, sidelink received signal processing, etc. can do.
  • the processor 210 may also control the overall operation of the second device 210.
  • the antenna unit 220 may include one or more physical antennas, and may support MIMO transmission and reception when it includes a plurality of antennas.
  • Transceiver 230 may include an RF transmitter and an RF receiver.
  • the memory 240 may store information processed by the processor 210 and software, operating system, and applications related to the operation of the second device 200, and may also include components such as buffers.
  • the processor 210 of the second device 200 is set to implement the operation of the terminal in communication between base stations and terminals (or the operation of the second terminal device in communication between terminals) in the embodiments described in this disclosure. It can be.
  • the base station and the terminal in base station-to-device communication (or the first terminal and the second terminal in terminal-to-device communication)
  • the items described can be applied equally, and overlapping explanations will be omitted.
  • the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may include Narrowband Internet of Things (NB-IoT) for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is not limited to the above-mentioned names.
  • LPWAN Low Power Wide Area Network
  • LTE-M technology may be an example of LPWAN technology, and may be called various names such as enhanced Machine Type Communication (eMTC).
  • eMTC enhanced Machine Type Communication
  • LTE-M technologies include 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine. It can be implemented in at least one of various standards such as Type Communication, and/or 7) LTE M, and is not limited to the above-mentioned names.
  • the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication. It may include one, and is not limited to the above-mentioned names.
  • ZigBee technology can create personal area networks (PANs) related to small/low-power digital communications based on various standards such as IEEE 802.15.4, and can be called by various names.

Landscapes

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

Abstract

Un procédé mis en œuvre par un terminal, selon un mode de réalisation de la présente invention, comprend les étapes consistant à : recevoir des informations de configuration associées à une pluralité d'ensembles de ressources de commande (CORESET) ; recevoir des informations de configuration associées à un groupe d'avance temporelle (TAG) ; et libérer une configuration associée à une transmission de liaison montante sur la base du fait qu'un temporisateur d'alignement temporel associé au TAG a expiré. Le TAG comprend i) un premier TAG associé à un premier indice de groupe de CORESET et ii) un second TAG associé à un second indice de groupe de CORESET. Le temporisateur d'alignement temporel comprend i) un premier temporisateur d'alignement temporel associé au premier TAG et ii) un second temporisateur d'alignement temporel associé au second TAG. La configuration associée à la transmission de liaison montante est libérée sur la base du fait que le premier temporisateur d'alignement temporel a expiré.
PCT/KR2023/011836 2022-08-11 2023-08-10 Procédé et appareil associés à une avance temporelle dans un système de communication sans fil WO2024035159A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20220100887 2022-08-11
KR10-2022-0100887 2022-08-11

Publications (1)

Publication Number Publication Date
WO2024035159A1 true WO2024035159A1 (fr) 2024-02-15

Family

ID=89852142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/011836 WO2024035159A1 (fr) 2022-08-11 2023-08-10 Procédé et appareil associés à une avance temporelle dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024035159A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220007410A1 (en) * 2019-03-28 2022-01-06 Ofinno, Llc Multiplexing and/or Prioritization of Uplink Signals
WO2022126149A2 (fr) * 2021-04-05 2022-06-16 Futurewei Technologies, Inc. Système et procédé pour établir des communications à l'aide de points d'émission-réception multiples intercellulaires et intracellulaires

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220007410A1 (en) * 2019-03-28 2022-01-06 Ofinno, Llc Multiplexing and/or Prioritization of Uplink Signals
WO2022126149A2 (fr) * 2021-04-05 2022-06-16 Futurewei Technologies, Inc. Système et procédé pour établir des communications à l'aide de points d'émission-réception multiples intercellulaires et intracellulaires

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Two TAs for multi-DCI", 3GPP DRAFT; R1-2204034, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052153323 *
LG ELECTRONICS: "Two TAs for multi-TRP/panel", 3GPP DRAFT; R1-2204142, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052144006 *
XIAOMI: "38.321 CR Correction on the HARQ buffer flush for MBS broadcast.", 3GPP DRAFT; R2-2207470, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20220817 - 20220829, 10 August 2022 (2022-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052260790 *

Similar Documents

Publication Publication Date Title
AU2018306399B2 (en) Method and apparatus for performing random access procedure
WO2022145995A1 (fr) Procédé et appareil de réglage de temporisation de liaison montante
WO2020167019A1 (fr) Procédé, dispositif terminal, station de base, support lisible par ordinateur pour mesurer une interférence de liaison croisée, et procédés et appareils pour attribution, détermination, et transmission de données, de préambule d'accès aléatoire
WO2017146550A1 (fr) Appareil et procédé d'exécution d'accès aléatoire dans un système à formation de faisceau
WO2019139299A1 (fr) Procédé d'émission et de réception de canal d'accès aléatoire sans fil et dispositif associé
WO2017135674A1 (fr) Procédé de communication dans un réseau prenant en charge des bandes sous licence et sans licence
WO2020036365A1 (fr) Procédé et appareil de détermination de type d'accès à un canal dans un système de communication sans fil
WO2020218894A1 (fr) Procédé et appareil de commutation entre des procédures d'accès aléatoire (ra) à 2 étapes et 4 étapes et résolutions de désaccord
WO2017123060A1 (fr) Système, procédé et appareil de suivi de faisceau et de fonctionnement de rétroaction faisceau dans un système à base de formation de faisceau
WO2019240512A1 (fr) Procédé et système de communication sans fil permettant de gérer un fonctionnement d'une minuterie
WO2018079969A1 (fr) Procédé de réalisation d'une gestion de faisceau dans un système de communication sans fil et appareil associé
WO2017213420A1 (fr) Procédé pour obtenir des informations relatives à un préfixe cyclique dans un système de communication sans fil et dispositif associé
WO2019027297A1 (fr) Procédé par lequel un terminal transmet un signal de liaison montante dans un système de communication sans fil prenant en charge une bande sans licence, et appareil de prise en charge de celui-ci
WO2015023128A1 (fr) Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile
WO2014196748A1 (fr) Procédé de transmission d'informations permettant la synchronisation d'équipement utilisateur par une station de base dans un système de communication sans fil et appareil correspondant
WO2019182401A1 (fr) Procédé et appareil pour effectuer une localisation dans un réseau sans fil de prochaine génération
EP3387756A1 (fr) Système, procédé et appareil de suivi de faisceau et de fonctionnement de rétroaction faisceau dans un système à base de formation de faisceau
WO2019199051A1 (fr) Procédé et dispositif pour une communication de latence faible dans un système de communication
WO2022060014A1 (fr) Procédé et dispositif de rapport de faisceau dans un système de communication sans fil
WO2018147672A1 (fr) Procédé d'émission et de réception de signal de liaison montante entre un terminal et une station de base dans un système de communication sans fil, et dispositif prenant en charge ce procédé
WO2019074237A1 (fr) Procédé de réception d'un signal de référence de suivi de phase par un terminal dans un système de communication sans fil et appareil le prenant en charge
WO2023055179A1 (fr) Procédé et appareil de mise en œuvre de procédure d'accès aléatoire dans un système de communication sans fil
WO2022131804A1 (fr) Procédé et dispositif de gestion de ressources dans un système de communication sans fil
WO2018110765A1 (fr) Procédé de réalisation de planification dans un système de communication sans fil et dispositif associé
WO2024029965A1 (fr) Procédé et appareil pour économiser l'énergie dans un système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1