WO2021155572A1 - Relation spatiale par défaut destinée à la transmission de ressources srs - Google Patents

Relation spatiale par défaut destinée à la transmission de ressources srs Download PDF

Info

Publication number
WO2021155572A1
WO2021155572A1 PCT/CN2020/074505 CN2020074505W WO2021155572A1 WO 2021155572 A1 WO2021155572 A1 WO 2021155572A1 CN 2020074505 W CN2020074505 W CN 2020074505W WO 2021155572 A1 WO2021155572 A1 WO 2021155572A1
Authority
WO
WIPO (PCT)
Prior art keywords
coreset
scheduled
srs resource
srs
spatial relation
Prior art date
Application number
PCT/CN2020/074505
Other languages
English (en)
Inventor
Bingchao LIU
Chenxi Zhu
Wei Ling
Lingling Xiao
Yi Zhang
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2020/074505 priority Critical patent/WO2021155572A1/fr
Publication of WO2021155572A1 publication Critical patent/WO2021155572A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H04L5/0025—Spatial division following the spatial signature of the channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • the subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for determining default spatial relation for SRS transmission in multi-TRP scenario.
  • Multi-DCI based multi-TRP is an important scenario in Release 16, the default DL reception beam determination for the UE has been supported in NR Release 16 based on the configured higher layer parameter CORESETPoolIndex for each CORESET in multi-TRP scenario.
  • This disclosure targets the determination of the default spatial relation for the SRS (including aperiodic SRS, semi-persistent SRS or periodic SRS) resource transmission.
  • a method comprises determining a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and transmitting the SRS resource using the determined default spatial relation.
  • the SRS resource is for aperiodic SRS scheduled by DCI.
  • CORESET (s) are configured on a scheduled CC; and the higher layer parameter CORESETPoolIndex is configured for each CORESET
  • the default spatial relation for SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among CORESET (s) in the active DL-BWP in the scheduled CC with the same value of CORESETPoolIndex as that configured for the CORESET transmitting the triggering DCI on a scheduling CC.
  • the default spatial relation for SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all the configured CORESET (s) in the active DL-BWP in the scheduled CC.
  • the default spatial relation for SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the scheduled CC.
  • the default spatial relation for SRS resource transmission is determined by the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB.
  • the default spatial relation for SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all CORESET (s) configured in the active DL-BWP in the scheduled CC with the lowest CC index among all CCs configured with CORESET within the simultaneousTCI-CellList.
  • the default spatial relation for SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC with the lowest CC index among all CCs with activated TCI state for PDSCH within the simultaneousTCI-CellList.
  • the SP SRS is associated with a CORESETPoolIndex by a field in the SP SRS Activation/Deactivation MAC CE or by the CORESET transmitting the DCI scheduling the PDSCH carrying the SP SRS Activation/Deactivation MAC CE, or a CORESETPoolIndex is directly configured in the SRS resource or SRS resource set containing the SRS resource.
  • each periodic SRS resource or each periodic SRS resource set is associated with a CORESETPoolIndex.
  • the default spatial relation for SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest ID among all the CORESETs configured with the same CORESETPoolIndex as that associated with the SP or periodic SRS resource.
  • the default spatial relation for SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC.
  • the default spatial relation for SRS resource transmission is determined by the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB on the CC.
  • a method comprises determining a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and receiving the SRS resource using the determined default spatial relation.
  • a remote unit comprises a processor configured to determine a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and a transmitter configured to transmit the SRS resource using the determined default spatial relation.
  • a base unit comprises a processor configured to determine a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and a receiver configured to receive the SRS resource using the determined default spatial relation.
  • Figure 1 illustrates an example of cross-carrier SRS scheduling
  • Figure 2 illustrates a semi-persistent SRS Activation/Deactivation MAC CE
  • Figure 3 is a schematic flow chart diagram illustrating an embodiment of a method
  • Figure 4 is a schematic flow chart diagram illustrating a further embodiment of a method.
  • Figure 5 is a schematic block diagram illustrating apparatuses according to one embodiment.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” .
  • code computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” .
  • the storage devices may be tangible, non-transitory, and/or non-transmission.
  • the storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • modules may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in code and/or software for execution by various types of processors.
  • An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
  • a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices.
  • the software portions are stored on one or more computer readable storage devices.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing code.
  • the storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.
  • each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .
  • the spatial relation information (e.g. spatial domain transmission filter) is not configured to the UE (or although configured, no activation command is received at the UE) for transmission of SRS resource (s) .
  • SRS can be aperiodic SRS, semi-persistent SRS or periodic SRS.
  • the first embodiment is related to aperiodic SRS.
  • Aperiodic SRS used for codebook, non-codebook, beam management and antenna switching can be triggered by DCI format 0_1 or format 1_1 with a non-zero ‘SRS request’ field.
  • Cross-carrier aperiodic SRS triggering in carrier aggregation (CA) scenario can be supported by DCI format 0_1 and format 1_1.
  • DCI format 2_3 with SRS request can be used to trigger an aperiodic SRS resource transmission on another carrier of serving cells in a condition that a UE is not configured for PUSCH and/or PUCCH transmission.
  • the default spatial relation for aperiodic SRS resource transmission in a component carrier (CC) in frequency range 2 (FR2) triggered by DCI format 0_1 or 1_1 or 2_3 can be determined according to different configurations for scheduling CC and scheduled CC.
  • the DCI used for triggering SRS resource is transmitted in the scheduling CC.
  • the triggered SRS resource is transmitted in the scheduled CC.
  • the configurations may include but are not limited to: in-carrier scheduling or cross-carrier scheduling; whether CORESET (s) are configured on the scheduled CC and/or the scheduling CC; whether CORESET (s) are configured with higher layer parameter CORESETPoolIndex; whether TCI state is activated for the PDSCH transmission on the scheduled CC; whether simultaneousTCI-CellList is configured, etc.
  • In-carrier scheduling means that the scheduling CC and the scheduled CC are the same CC.
  • Case 1 when (1) CORESET (s) are configured on the scheduled CC for the SRS resource transmission;
  • the default spatial relation for the SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among CORESET (s) in the active DL-BWP in the scheduled CC configured with the same value of CORESETPoolIndex as that configured for the CORESET transmitting the scheduling DCI.
  • the UE will transmit the SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest CORESET-ID in the active DL-BWP in the scheduled CC configured with the same value of CORESETPoolIndex as that configured for the CORESET transmitting the scheduling DCI.
  • Scenario 2 cross-carrier scheduling and the scheduled CC configured with CORESET.
  • Cross-carrier scheduling means that the scheduling CC and the scheduled CC are different CCs.
  • CORESET (s) are configured on the scheduled CC.
  • Case 2-1 when (1) CORESET (s) are configured on the scheduled CC for the SRS resource transmission;
  • the default spatial relation for the SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all the CORESET (s) configured in the active DL-BWP in the scheduled CC no matter whether the CORESET transmitting the DCI is configured with a CORESETPoolIndex or not.
  • the UE will transmit the SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest CORESET-ID in the active DL-BWP in the scheduled CC.
  • Case 2_2 when (1) CORESET (s) are configured on the scheduled CC for the SRS resource transmission;
  • each configured CORESET on the scheduled CC is configured with a higher layer parameter CORESETPoolIndex
  • the CORESET transmitting the DCI on the scheduling CC is also configured with a CORESETPoolIndex
  • the default spatial relation for the SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among CORESET (s) configured with the same value of CORESETPoolIndex in the active DL-BWP in the scheduled CC as that configured for the CORESET transmitting the scheduling DCI on the scheduling CC.
  • the UE will transmit the SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest CORESET-ID in the active DL-BWP in the scheduled CC configured with the same value of CORESETPoolIndex as that configured for the CORESET transmitting the scheduling DCI on the scheduling CC.
  • Case 2_3 when (1) CORESET (s) are configured on the scheduled CC for the SRS resource transmission;
  • each configured CORESET on the scheduled CC is configured with a higher layer parameter CORESETPoolIndex
  • the default spatial relation for the SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all the CORESET (s) configured in the active DL-BWP in the scheduled CC.
  • the UE will transmit the SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest CORESET-ID in the active DL-BWP in the scheduled CC.
  • Figure 1 illustrates an example of cross-carrier SRS scheduling for e.g. cases 2_1, 2_2 and 2_3.
  • UE receives a DCI format 0_1 or 1_1 or 2_3 with a non-zero ‘SRS request’ field in slot n on CC#1 (scheduling CC) scheduling an aperiodic SRS resource transmission on CC#2 (scheduled CC) in slot n+k.
  • SRS request a DCI format 0_1 or 1_1 or 2_3 with a non-zero ‘SRS request’ field in slot n on CC#1 (scheduling CC) scheduling an aperiodic SRS resource transmission on CC#2 (scheduled CC) in slot n+k.
  • the default spatial relation for the corresponding SRS resource transmission on CC#2 is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all the CORESETs configured in the active DL-BWP in CC#2.
  • Scenario 3 cross-carrier scheduling and no CORESET configured on the scheduled CC.
  • no CORESET is configured on the scheduled CC.
  • the default spatial relation for the SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the scheduled CC no matter whether the CORESET transmitting the DCI on the scheduling CC is configured with a CORESETPoolIndex or not.
  • Case 3_2 when (1) no CORESET is configured on the scheduled CC;
  • the default spatial relation for the SRS resource transmission is determined by the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB.
  • the UE will transmit the SRS resource with the same spatial domain transmission filter as that used for the reception of the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB.
  • the default spatial relation for the SRS resource transmission can be determined on the basis of the scheduling CC according to Case 1. That is, the default spatial relation for the SRS resource transmission on the scheduled CC is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among CORESET (s) configured in the active DL-BWP in the scheduling CC.
  • the gNB can only configure the TCI state for PDSCH and/or PDCCH for one CC in the simultaneousTCI-CellList.
  • Case 3_3 when (1) no CORESET is configured on the scheduled CC;
  • the default spatial relation for the SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all CORESET (s) configured in the active DL-BWP in the CC with the lowest CC index among all CCs configured with CORESET within the simultaneousTCI-CellList no matter whether the CORESET transmitting the DCI on the scheduling CC is configured with a CORESETPoolIndex or not.
  • CC#2 (the scheduled CC)
  • CC#3, CC#4 and CC#5 belong to a simultaneousTCI-CellList.
  • No CORESET is configured on the CC#2 (the scheduled CC) .
  • No TCI state is activated for the PDSCH transmission on the CC#2 (the scheduled CC) .
  • CORESETs are configured on the CC#4 and CC#5 but not on CC#3.
  • the default spatial relation for SRS resource transmission on CC#2 is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest CORESET-ID among all the CORESET (s) configured in the active DL-BWP in CC#4 (which has the lowest CC index among CCs that are configured with CORESET within the simultaneousTCI-CellList) .
  • the default spatial relation for the SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC with the lowest CC index among all CCs with activated TCI state for PDSCH within the simultaneousTCI-CellList no matter whether the CORESET transmitting the DCI on the scheduling CC is configured with a CORESETPoolIndex or not.
  • CC#2 (the scheduled CC)
  • CC#3, CC#4 and CC#5 belong to a simultaneousTCI-CellList.
  • No CORESET is configured on the CC#2 (the scheduled CC) .
  • No TCI state is activated for the PDSCH transmission on the CC#2 (the scheduled CC) .
  • CORESETs are not configured on the CC#3, CC#4 and CC#5, either.
  • Each of CC#4 and CC#5 (but not CC#3) is activated with at least one TCI state for PDSCH for the active DL-BWP.
  • the default spatial relation for the SRS resource transmission on CC#2 is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC#4 (which has the lowest CC index among the CCs with activated TCI state for PDSCH within the simultaneousTCI-CellList) .
  • the second embodiment is related to semi-persistent (SP) SRS.
  • SP SRS resource is activated or deactivated by a SP SRS Activation/Deactivation MAC CE.
  • the spatial relation for each activated SP SRS resource may be configured in the MAC CE.
  • the UE support the default spatial relation feature for SRS i.e. the UE is configured with a higher layer parameter enableDefaultBeamPlForSRS with the value of enable
  • the spatial relation for each SP SRS resource may not be configured in the MAC CE. Instead, the UE can transmit the SP SRS resource by using a default spatial relation.
  • the association between a SP SRS resource and CORESETPoolIndex may be achieved by introducing an additional CORESETPoolIndex field in the current SP SRS Activation/Deactivation MAC CE as illustrated in Figure 2.
  • the MAC CE is associated with a CORESETPoolIndex indicated by the T field. Therefore, the activated SP SRS resource is also associated with the indicated CORESETPoolIndex.
  • the T field (CORESETPoolIndex field) is only present if CORESETPoolIndex is configured for the CORESET configured on the BWP in the CC indicated by the MAC CE.
  • the association between the SP SRS resource and CORESETPoolIndex may be alternatively achieved by being based on the DCI scheduling the PDSCH carrying the MAC CE.
  • the activated SP SRS resource is associated with the CORESETPoolIndex configured for the CORESET transmitting the DCI scheduling the PDSCH carrying the MAC CE.
  • the associated CORESETPoolIndex is directly configured in the SRS resource or the SRS resource set containing the SRS resource.
  • the default spatial relation for SP SRS resource transmission in a CC (e.g. in FR2) can be determined by the following manner:
  • the default spatial relation for SP SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest ID among all the CORESETs configured with the same CORESETPoolIndex as that associated with the activated SRS resource.
  • the UE will transmit the SP SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest ID among all the CORESETs configured with the same CORESETPoolIndex as that associated with the activated SRS resource.
  • the default spatial relation for SP SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC.
  • the default spatial relation for SP SRS resource transmission is determined by the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB on this CC if applicable.
  • the UE will transmit the SP SRS resource with the same spatial domain transmission filter as that used for the reception of the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB.
  • the third embodiment is related to periodic SRS.
  • each SRS resource set is associated with a CORESETPoolIndex
  • each SRS resource contained in the SRS resource set is associated with the CORESETPoolIndex.
  • each SRS resource is associated with the CORESETPoolIndex.
  • the default spatial relation for periodic SRS resource transmission in a CC (e.g. in FR2) can be determined by the following manner:
  • the default spatial relation for periodic SRS resource transmission is determined by the RS with ‘QCL-Type-D’ corresponding to the QCL assumption of the CORESET with the lowest ID among all the CORESETs configured with the same CORESETPoolIndex as that associated with the periodic SRS.
  • the UE will transmit the periodic SRS resource with the same spatial domain transmission filter as that used for the reception of the CORESET with the lowest ID among all the CORESETs configured with the same CORESETPoolIndex as that associated with the periodic SRS.
  • the default spatial relation for periodic SRS resource transmission is determined by the activated TCI state with the lowest ID applicable to PDSCH in the active DL-BWP in the CC.
  • the default spatial relation for periodic SRS resource transmission is determined by the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB if applicable.
  • the UE will transmit the periodic SRS resource with the same spatial domain transmission filter as that used for the reception of the RS resource obtained from the SS/PBCH block reception that the UE uses to obtain MIB.
  • Figure 3 is a schematic flow chart diagram illustrating an embodiment of a method 300 according to the present application.
  • the method 300 is performed by an apparatus, such as a base unit.
  • the method 300 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 300 may include 302 determining a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and 304 receiving the SRS resource using the determined default spatial relation.
  • Figure 4 is a schematic flow chart diagram illustrating a further embodiment of a method 400 according to the present application.
  • the method 400 is performed by an apparatus, such as a remote unit.
  • the method 400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 400 may include 402 determining a default spatial relation for SRS resource transmission according to a higher layer parameter CORESETPoolIndex; and 404 transmitting the SRS resource using the determined default spatial relation.
  • Figure 5 is a schematic block diagram illustrating apparatuses according to one embodiment.
  • the UE i.e. the remote unit
  • the UE includes a processor, a memory, and a transceiver.
  • the processor implements a function, a process, and/or a method which are proposed in Figure 4.
  • the eNB i.e. base unit
  • the processors implement a function, a process, and/or a method which are proposed in Figure 3.
  • Layers of a radio interface protocol may be implemented by the processors.
  • the memories are connected with the processors to store various pieces of information for driving the processors.
  • the transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.
  • the memories may be positioned inside or outside the processors and connected with the processors by various well-known means.
  • each component or feature should be considered as an option unless otherwise expressly stated.
  • Each component or feature may be implemented not to be associated with other components or features.
  • the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.
  • the embodiments may be implemented by hardware, firmware, software, or combinations thereof.
  • the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays

Abstract

L'invention concerne des procédés et des appareils permettant de déterminer une relation spatiale par défaut. Un procédé comprend la détermination d'une relation spatiale par défaut pour la transmission de ressources SRS selon un paramètre de couche supérieure CORESETPoolIndex; et la transmission des ressources SRS à l'aide de la relation spatiale par défaut déterminée.
PCT/CN2020/074505 2020-02-07 2020-02-07 Relation spatiale par défaut destinée à la transmission de ressources srs WO2021155572A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/074505 WO2021155572A1 (fr) 2020-02-07 2020-02-07 Relation spatiale par défaut destinée à la transmission de ressources srs

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/074505 WO2021155572A1 (fr) 2020-02-07 2020-02-07 Relation spatiale par défaut destinée à la transmission de ressources srs

Publications (1)

Publication Number Publication Date
WO2021155572A1 true WO2021155572A1 (fr) 2021-08-12

Family

ID=77199126

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074505 WO2021155572A1 (fr) 2020-02-07 2020-02-07 Relation spatiale par défaut destinée à la transmission de ressources srs

Country Status (1)

Country Link
WO (1) WO2021155572A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190319823A1 (en) * 2018-04-13 2019-10-17 Qualcomm Incorporated Uplink multi-beam operation
CN110535580A (zh) * 2018-08-08 2019-12-03 中兴通讯股份有限公司 传输控制方法、探测参考信号传输方法、终端、基站及介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190319823A1 (en) * 2018-04-13 2019-10-17 Qualcomm Incorporated Uplink multi-beam operation
CN110535580A (zh) * 2018-08-08 2019-12-03 中兴通讯股份有限公司 传输控制方法、探测参考信号传输方法、终端、基站及介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
AT&T: "Remaining Issues on Multi-Beam Enhancements", 3GPP DRAFT; R1-1912845, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, NV; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051823643 *
LENOVO, MOTOROLA MOBILITY: "Discussion of multi-beam operation", 3GPP DRAFT; R1-1912317, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051819991 *

Similar Documents

Publication Publication Date Title
WO2021258279A1 (fr) Détermination de faisceau par défaut pour transmission de signal de liaison montante (ul)
WO2021203414A1 (fr) Détermination de faisceau par défaut
CN115769538A (zh) 定位参考信号资源配置
US20220345903A1 (en) Determining Default Spatial Relation for UL Signals
WO2022141006A1 (fr) Indication de faisceau tx commun et application pour ul
WO2022133701A1 (fr) Commutation dynamique de faisceau commun pour réception dl
WO2021134772A1 (fr) Mac ce pour configurer un signal de référence de perte de trajet pour signal de référence de sondage
WO2021155572A1 (fr) Relation spatiale par défaut destinée à la transmission de ressources srs
WO2021022398A1 (fr) Configuration et indication de relation spatiale pour des ressources pucch
WO2021051379A1 (fr) Signal de synchronisation de porteuse non d'ancrage
WO2020198914A1 (fr) Procédés et dispositifs pour configurer et déclencher une transmission de srs apériodique
WO2021212397A1 (fr) Détermination de faisceau par défaut dans une planification inter-porteuses
WO2023130247A1 (fr) Transmission ul basée sur plusieurs trp multi-dci dans une structure tci unifiée
US20230049134A1 (en) Aperiodic srs triggering and transmission
WO2021134779A1 (fr) Ce mac pour la configuration d'un signal de référence d'affaiblissement de trajet pour pusch
WO2023184311A1 (fr) Réception de pdcch et de csi-rs dans un scénario multi-trp avec infrastructure tci unifiée
US20230254856A1 (en) Default beam determination for reception of pdsch transmissions with repetition
WO2023137648A1 (fr) Commutation de paramètre de commande de puissance en boucle ouverte dynamique entre embb et urllc dans une structure de tci unifiée
WO2023137654A1 (fr) Transmission ul basée sur trp multiples à dci uniques dans une structure de tci unifiée
WO2022213254A1 (fr) Sondage de fréquence partielle
WO2022151135A1 (fr) Indication de faisceau commun basée sur mac ce
US20220278814A1 (en) Wireless system wider bandwidth carrier indication

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20917740

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 08/02/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20917740

Country of ref document: EP

Kind code of ref document: A1