Wireless communication method and device
By including the TA command domain in the RAR and using the index ID in the PDCCH command, the terminal device obtains the TA value and optimizes the uplink transmission in the multi-TRP scenario, solving the uplink transmission efficiency and coverage problems of multi-TRP within and between cells. It realizes the accurate acquisition of TA values and the optimization of uplink transmission.
Patent Information
- Application Number
- PCT/CN2023/094024
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-21
AI Technical Summary
In the uplink transmission scenarios of multiple TRPs in the cell and multiple TRPs in the cell, it is difficult for the terminal device to effectively obtain the timing advance (TA) value, resulting in limited uplink transmission efficiency and coverage.
By including m TA command fields in the RAR, the terminal device can determine the TA values corresponding to m TAGs, thereby optimizing uplink transmission in multiple TRP scenarios. At the same time, using the CSI-RS index, uplink TCI state ID or joint TCI state ID in the PDCCH command, the terminal device can determine the PL RS and uplink space filter used to send the PRACH to optimize the PRACH transmission.
It realizes TA value acquisition and uplink transmission optimization in multi-TRP scenarios, solves the QCL conflict problem, and improves the efficiency and coverage of uplink transmission.
Smart Images

Figure CN2023094024_21112024_PF_FP_ABST
Abstract
Description
Wireless communication method and device Technical Field
[0001] The present invention relates to the field of communications, and more specifically, to a method and device for wireless communications. Background Art
[0002] In the uplink transmission scenarios of intra-cell multi-TRP and inter-cell multi-TRP, how a terminal device obtains timing advance (TA) is a problem that needs to be solved.
[0003] Summary of the Invention
[0004] An embodiment of the present application provides a method and device for wireless communication, in which a terminal device can determine the TA values corresponding to m TAGs based on the m TA command fields in the RAR, thereby obtaining the TA value in the uplink transmission scenarios of intra-cell multi-TRP and inter-cell multi-TRP, thereby optimizing the uplink transmission in the multi-TRP scenario.
[0005] In a first aspect, a wireless communication method is provided, the method comprising:
[0006] The terminal device sends PRACH;
[0007] The terminal device receives a RAR; wherein the RAR includes m TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m TAGs, where m is a positive integer, and m=1 or m≥2.
[0008] In a second aspect, a wireless communication method is provided, the method comprising:
[0009] The first network node sends a RAR; wherein the RAR includes m TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m TAGs, where m is a positive integer, and m=1 or m≥2.
[0010] According to a third aspect, a wireless communication method is provided, the method comprising:
[0011] The second network node sends a PDCCH command, where the PDCCH command is used to trigger the terminal device to send a PRACH;
[0012] The PDCCH command includes at least one of the following: a CSI-RS index, an uplink TCI state ID, and a joint TCI state ID;
[0013] The CSI-RS index is associated with the PL RS used to send the PRACH;
[0014] The uplink TCI state is associated with an uplink spatial filter for sending the PRACH, and / or the DL RS included in the uplink TCI state is associated with a PL RS used for sending the PRACH;
[0015] The joint TCI state is associated with an uplink spatial filter used to send the PRACH, and / or the DL RS included in the joint TCI state is associated with a PL RS used to send the PRACH.
[0016] Through the technical solutions of the first and second aspects above, the terminal device can determine the TA values corresponding to m TAGs based on the m TA command fields in the RAR, so that the TA value can be obtained in the uplink transmission scenarios of intra-cell multi-TRP and inter-cell multi-TRP, thereby optimizing the uplink transmission in the multi-TRP scenario.
[0017] Through the technical solution of the third aspect above, the terminal device can determine the PL RS used to send PRACH and / or the uplink spatial filter for sending PRACH based on at least one of the CSI-RS index, uplink TCI state ID, and joint TCI state ID contained in the PDCCH command, thereby optimizing PRACH transmission.
[0018] The embodiments of the present application solve the problem of a PDCCH command sent by the second network node conflicting with the QCL of the RAR sent by the first network node. Specifically, the terminal device uses the activated TCI state of the CORESET where the PDCCH command is located for receive beamforming to receive the PDCCH command, and uses the activated TCI state of the CORESET associated with the RAR-associated type 1 CSS to receive the RAR-associated PDCCH and PDSCH.
[0019] The embodiments of the present application solve the problem of a terminal device sending a PRACH to a second network node and a QCL conflict with a RAR sent by a first network node. The terminal device uses the CSI-RS index or downlink TCI state ID or joint TCI state ID indicated in the PDCCH command to send the PRACH, and uses the activated TCI state of the RAR-associated type 1 CSS-associated CORESET to receive the RAR-associated PDCCH and PDSCH.
[0020] The embodiments of the present application solve the problem of a QCL conflict between a terminal device sending a PRACH to a second network node and a first network node sending a PDCCH command. The terminal device uses the CSI-RS index or downlink TCI state ID or joint TCI state ID indicated in the PDCCH command to send the PRACH, and the terminal device uses the activated TCI state of the CORESET where the PDCCH command is located to perform receive beamforming to receive the PDCCH command. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] FIG1 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.
[0022] FIG2 is a schematic diagram of a TA command provided in this application.
[0023] FIG3 is a schematic diagram of another TA command provided in this application.
[0024] FIG4 is a schematic diagram of yet another TA command provided in the present application.
[0025] FIG5 is a schematic diagram of an uplink and downlink frame structure from the perspective of a UE, provided in this application.
[0026] FIG6 is a schematic diagram of an uplink and downlink scheduling scenario of mDCI-mTRP provided in the present application.
[0027] FIG7 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.
[0028] 8 to 18 are schematic diagrams of RAR provided according to embodiments of the present application.
[0029] 19 to 22 are schematic diagrams of obtaining TA according to embodiments of the present application.
[0030] Figure 23 is a schematic flowchart of another wireless communication method provided according to an embodiment of the present application.
[0031] Figure 24 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
[0032] Figure 25 is a schematic block diagram of a network device provided according to an embodiment of the present application.
[0033] Figure 26 is a schematic block diagram of another network device provided according to an embodiment of the present application.
[0034] Figure 27 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
[0035] Figure 28 is a schematic block diagram of a device provided according to an embodiment of the present application.
[0036] Figure 29 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION
[0037] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0038] The technical solutions of the embodiments of the present application can be applied to various communication systems, including new radio (NR) systems, evolved systems of NR systems, NR-based access to unlicensed spectrum (NR-U) systems, non-terrestrial communication networks (NTN) systems, wireless local area networks (WLAN), Internet of Things (IoT), wireless fidelity (WiFi), fifth-generation communication (5G) systems, sixth-generation communication (6G) systems or other communication systems.
[0039] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), vehicle-to-vehicle (V2V) communication, sidelink (SL) communication, vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0040] In some embodiments, the communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, an independent (SA) networking scenario, or a non-standalone (NSA) networking scenario.
[0041] In some embodiments, the communication system in the embodiments of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiments of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.
[0042] In some embodiments, the communication system in the embodiments of the present application can be applied to the FR1 frequency band (corresponding to the frequency band range of 410MHz to 7.125GHz), can also be applied to the FR2 frequency band (corresponding to the frequency band range of 24.25GHz to 52.6GHz), and can also be applied to new frequency bands such as high-frequency bands corresponding to the frequency band range of 52.6GHz to 71GHz or the frequency band range of 71GHz to 114.25GHz.
[0043] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0044] The terminal device can be a station (STA) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0045] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
[0046] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city or a wireless terminal device in a smart home, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc.
[0047] As an example and not a limitation, in an embodiment of the present application, the terminal device may also be a wearable device.
[0048] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or a base station (gNB) or a transmission reception point (TRP) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.
[0049] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments, the network device may also be a base station set up in a location such as land or water.
[0050] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station).
[0051] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.
[0052] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.
[0053] In some embodiments, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
[0054] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.
[0055] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.
[0056] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.
[0057] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain it through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain it through C; it can also mean that there is an association between A and B.
[0058] It should be understood that the "at least one or at least one" mentioned in the embodiments of the present application can mean "one or more", and the "positive integer" mentioned in the embodiments of the present application can mean "values such as 1, 2, 3...", and the "non-negative integer" mentioned in the embodiments of the present application can mean "values such as 0, 1, 2, 3...", and the "integer" mentioned in the embodiments of the present application can mean "values such as..., -3, -2, -1, 0, 1, 2, 3,...", and can be replaced with any possible value based on the requirements of the embodiment.
[0059] It should be understood that the figures and / or tables shown in the embodiments of the present application are merely examples. Specifically, in some cases, some of the information contained in the figures and / or tables shown in the embodiments of the present application may independently constitute an optional embodiment. For example, each row or column in the table may independently constitute an optional embodiment. The present application does not limit this.
[0060] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.
[0061] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.
[0062] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may be an evolution of an existing LTE protocol, NR protocol, Wi-Fi protocol, or a protocol related to other communication systems. The present application does not limit the protocol type.
[0063] To facilitate a better understanding of the embodiments of the present application, the timing advance (TA) related to the present application is explained.
[0064] In the NR standard, a UE can be configured with up to 4 timing advance groups (TAGs) in a cell group (CG). Specifically, the information field for configuring the TAG through Radio Resource Control (RRC) signaling can be as follows. Generally, a CG can include multiple serving cells, and each serving cell will be assigned a TAG Identity (TAG ID). Each TAG will have a timing adjustment timer (TimeAlignmentTimer), and the UE will count the timing adjustment timer. When the timing adjustment timer times out, the UE will consider that the corresponding TAG is out of uplink synchronization. When the NW adjusts the TA value through the Media Access Control Control Element (MAC CE) or other signaling within the time when the timing adjustment timer is running, the timing adjustment timer will be reset, and the UE will consider that the TAG is in uplink synchronization state. For example, if the TimeAlignmentTimer value is configured to 500ms, the NW needs to update (adjust) the UE's TA value once within 500ms. Otherwise, the UE may consider the uplink out of synchronization and may initiate a random access channel (RACH) process when uplink data arrives.
[0065] The calculation formula for the UE timing advance is relatively simple, as shown in the following formula 1. The UE timing advance is based on the first path of the downlink channel received by the UE, that is, the first symbol of the time slot where the channel is located, as the downlink reference, and the advance transmission is performed based on this. (N TA +N TA,offset)*T C Formula 1
[0066] In a CG, each serving cell can be pre-configured with a timing advance offset (TA offset) n-TimingAdvanceOffset, which is the N in the above formula 1. TA,offset TA adjustment amount (N TA ) is performed based on the pre-configured offset. C is the minimum time unit in the NR system, T C =1 / (4096*480kHz). N TA The MAC CE of the network (NW) can provide differential adjustment, that is, the current TA adjustment (new) is based on the previous TA (old) and is adjusted forward or backward in time. The specific calculation method is shown in Formula 2.
[0067] The differential adjustment format of MAC CE's TA is shown in Figure 2, that is, adjusting T based on the previous TA A The minimum time unit is TAG, and the granularity of the TA adjustment is TAG.
[0068] Among them, TAG ID (TAG Identity) in FIG2 : This field indicates the TAG Identity of the addressing TAG, the TAG including the special cell (Special Cell, SpCell) has a TAG identity of 0, and the length of the field is 2 bits.
[0069] 2 , the TA command field indicates an index value TA (0, 1, 2 . . . 63) for controlling a timing adjustment amount that a Media Access Control (MAC) entity must apply. The field length is 6 bits.
[0070] The second method is to obtain TA, that is, NW indicates to UE the absolute value of TA for its uplink transmission. For example, NW MAC CE directly gives an absolute value N TA , its value range is 0 to 3846, and its indication range for TA is N TA =T A *16*64*2 μ , with a length of 12 bits, as shown in Figure 3. The TA command applies to the primary timing advance group (PTAG) corresponding to the MAC entity. That is, the PTAG is defined to include the SpCell. Because the MAC CE applies only to the PTAG, it does not need to include a TAG-Id.
[0071] 3 , the TA command field indicates an index value TA for controlling the timing adjustment amount that the MAC entity must apply. The field size is 12 bits.
[0072] Among them, R in Figure 3: reserved bit, the bit is set to "0".
[0073] In addition, during the initial access (cell) process, after the UE sends a Physical Random Access Channel (PRACH) to the NW, it expects the NW to provide the UE with a TA indication via a MAC Random Access Response (RAR) within a certain time window. The specific signaling is shown in Figure 4. In this way, the UE can obtain the initial TA absolute value, which is also 12 bits. As shown in Figure 4, this signaling also includes the Uplink Grant (UL Grant) field and the Cell Radio Network Temporary Identity (C-RNTI) field.
[0074] If the UE operates in a multi-transmission reception point (TRP) mode, the reference point of the UE timing advance is calculated from the downlink reception time point and is advanced forward (N TA +N TA,offset )*T C The uplink channel or signal is sent at the same time. From the UE's perspective, the relationship between the uplink and downlink frame structures can be shown in Figure 5.
[0075] In order to facilitate a better understanding of the embodiments of the present application, the uplink multi-TRP transmission related to the present application is explained.
[0076] Supports repetition of the uplink Physical Uplink Control Channel (PUCCH) / Physical Uplink Shared Channel (PUSCH) based on multiple TRPs to enhance uplink coverage and transmission reliability. The UE needs to send PUCCH / PUSCH carrying the same content to different TRPs. For PUSCH repetition, support is provided for multi-PUSCH repeated transmission based on single downlink control information (DCI) (sDCI), using a timing advance (TA) to sequentially send PUSCH to different TRPs. For multi-PUSCH transmission based on multiple DCI (mDCI), since there may not be a sufficiently ideal backhaul connection between multiple TRPs, multiple TRPs independently schedule the UE. This operation may cause PUSCH / PUCCH of different TRPs to overlap in time, so it is also necessary to support different TA updates or indications for different TRPs.
[0077] The UE's multiple antenna panels simultaneously transmit PUCCH / PUSCH to multiple TRPs. However, even with multiple uplink transmit antenna panels and multiple TRPs, the UE can only use one TA for early transmission within a serving cell. This limitation should obviously be overcome by supporting TRP-specific TA acquisition and indication.
[0078] For example, in the intra-cell mDCI-mTRP scenario, TRP #1 and TRP #2 use the same PCI, as shown in Figure 6 (mDCI-mTRP uplink and downlink scheduling scenario). Each TRP can schedule its physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) transmission through its own DCI. It is worth noting that in the operation of mDCI-mTRP, the control resource set (CORESET) is grouped according to its RRC parameter control resource set pool index (CORESETPoolIndex), that is, CORESETs with CORESETPoolIndex of "0" are grouped into one group, corresponding to one TRP; CORESETs with CORESETPoolIndex of "1" are grouped into another group, corresponding to another TRP. When the NW does not configure CORESETPoolIndex for a CORESET, its default value is "0".
[0079] In the inter-cell mDCI-mTRP scenario, TRP #1 in Figure 6 can be understood as the reference TRP, that is, the TRP that the UE accesses upon initial access. The UE has already achieved uplink and downlink synchronization and has a dedicated PCI #1. As for other TRPs, since the NW can select a TRP from up to seven TRPs to provide additional uplink transmission services for the UE, these TRPs have different physical cell identifiers (PCIs) from the serving TRP and often have not established uplink and downlink synchronization with the UE in advance. This is also the difference between inter-cell and intra-cell multi-TRP operations.
[0080] In some embodiments, the UE is assigned 2 TAGs, each TAG corresponding to a TRP.
[0081] To facilitate a better understanding of the embodiments of the present application, the TCI state and spatial relation related to the present application are explained.
[0082] The Transmission Configuration Indicator (TCI) state is used for downlink spatial domain quasi-co-located (QCL) (beam) indication and the transmission of QCL information in the time and frequency domains. Specifically, the quasi-co-located (QCL) relationship can be simply described as the relationship of large-scale fading from a source reference signal to a target reference signal. For beam indication, after the UE obtains the QCL relationship between the two source reference signals and the target reference signal from the NW, it can use the receive beam that previously received the source reference signal when receiving the target reference signal.
[0083] The TCI status indication mechanism only applies to downlink channels and signals. NR systems define the concept of spatial relation for uplink beam indication, which is also used to express the spatial relationship between two reference signals.
[0084] To provide a unified uplink and downlink beam management mechanism for the NR system, the concept of a unified TCI state is proposed based on the design of the TCI state. It adds important new functions, such as the following:
[0085] Three unified TCI state modes are designed: the joint TCI state applies to both uplink and downlink channels and signals, the downlink TCI state (DL TCI state) applies only to downlink channels and signals, and the uplink TCI state (UL TCI state) applies only to uplink channels and signals.
[0086] Downlink channels (part of the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH)) and signals (aperiodic Channel State Information Reference Signal (CSI-RS)) use the same downlink transmit indicator beam and use the downlink TCI state (DL TCI state) or joint TCI state.
[0087] Uplink channels (PUCCH, PUSCH) and signals (Sounding Reference Signal (SRS)) use the same uplink transmit beam and use the uplink TCI state (UL TCI state) or joint TCI state.
[0088] The Unified TCI state can be dynamically updated and indicated using MAC CE and / or DCI.
[0089] The Unified TCI state is applicable to carrier aggregation scenarios, and the beam indication on a single component carrier (CC) can be applicable to multiple different CCs.
[0090] The uplink beam indication can be given simultaneously with the uplink power control parameters through the UL TCI state or joint TCI state.
[0091] Unified TCI state supports inter-cell beam management.
[0092] To better understand the significance of the unified TCI state, it is helpful to refer to its RRC parameter configuration, as shown below.
[0093] In some embodiments, the TA value used by the uplink channel or signal may also be indicated while indicating the TCI state / spatial relation.
[0094] In order to facilitate a better understanding of the embodiments of the present application, the problems solved by the present application are explained.
[0095] TA acquisition based on the random access procedure was introduced for the initial access procedure of a single TRP. Because the UE does not have a UE-dedicated RRC configuration before completing the RACH procedure, the QCL indication based on the TCI state configured by the RRC configuration cannot be used. Therefore, the fixed QCL assumption used between the various steps of the random access procedure lacks flexibility.
[0096] Based on the above problems, this application proposes a TA acquisition solution, which is suitable for uplink transmission scenarios of intra-cell multi-TRP and / or inter-cell multi-TRP. During the random access process, the QCL relationship between different steps can be flexibly set to meet the uplink transmission requirements.
[0097] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.
[0098] FIG7 is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG7 , the wireless communication method 200 may include at least part of the following contents:
[0099] S210, the terminal device sends a PRACH;
[0100] S220, the first network node sends a RAR; wherein the RAR includes m TA command fields, the m TA command fields are respectively used to indicate TA values corresponding to m TAGs, m is a positive integer, and m=1 or m≥2;
[0101] S230: The terminal device receives the RAR.
[0102] It should be understood that FIG7 shows the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG7.
[0103] In the embodiments of the present application, the network node may also be referred to as a TRP or other device with similar functions (such as a micro base station), but the present application does not limit this.
[0104] In the embodiment of the present application, the network node receiving the PRACH may be the first network node or other network nodes (such as the second network node), and the embodiment of the present application is not limited to this.
[0105] For example, assuming that the network node receiving PRACH is network node x, in the first step of the random access process, the terminal device sends PRACH based on the downlink reference reception time, and the network node x measures the arrival time of the PRACH, thereby calculating the TA value of the UE for the network node x (for example, the network node x measures the correct TA value required by the terminal device through the random access preamble carried in the PRACH), and the network node x notifies the terminal device of the measured TA value in the form of MAC RAR, or the network node x notifies the network node y of the measured TA value, and then the network node y notifies the terminal device of the TA value obtained from the network node x in the form of MAC RAR.
[0106] It should be noted that MAC RAR can be understood as the media access control (MAC) layer signaling carried by the PDCCH (PDCCH RAR) and its scheduled PDSCH (PDSCH RAR). In addition, the terminal device expects the demodulation reference signal (DMRS) of the PDCCH carrying the RAR to maintain a quasi-co-located (QCL) relationship with the PDSCH DRMS.
[0107] Specifically, MAC RAR is MAC control information sent from the network to the UE. RAR transmission is derived from MAC data at the physical layer and is carried by the PDSCH scheduled by the PDCCH.
[0108] In an embodiment of the present application, one TAG may correspond to one network node (such as a TRP), that is, m TAGs may correspond to m network nodes (such as a TRP) respectively. In other words, part or all of the TA information carried in the RAR may be obtained by the first network node from one or more other network nodes.
[0109] In some embodiments, the embodiments of the present application can be applied to multiple network nodes between cells (such as inter-cell multi-TRP), or the embodiments of the present application can be applied to multiple network nodes within a cell (such as intra-cell multi-TRP). For example, the terminal device needs to initiate a random access process for different network nodes (such as TRP) to obtain a TA value exclusive to each network node (such as TRP).
[0110] In some embodiments, multiple network nodes can support the TA acquisition process of multiple DCI (M-DCI), that is, each network node sends a message to the terminal device through DCI respectively; and / or, multiple network nodes can support the TA acquisition process of single DCI (S-DCI), that is, multiple network nodes send a message to the terminal device through one DCI.
[0111] For example, multiple TRPs (multi-TRP, MTRP) support the TA acquisition process for multiple DCIs (multi-DCI, M-DCI). In this case, there may not be a good backhaul connection between the M-DCI MTRPs, and each TRP completes independent scheduling of the same UE. Each TRP can be identified by "0" or "1" in CORESETPoolIndex.
[0112] For example, multiple TRPs (multi-TRP, MTRP) support the TA acquisition process for a single DCI (single-DCI, S-DCI). In this case, the TRPs can maintain good backhaul connectivity, allowing one TRP to schedule uplink and downlink transmissions between a UE and two TRPs. However, the CORESETPoolIndex parameter is not configured, or it only has a single value, either all "0" or all "1".
[0113] In some embodiments, the embodiments of the present application can be applied to a 4-step random access process or a 2-step random access process.
[0114] In some embodiments, the maximum value of m is 4, because a terminal can be configured with a maximum of 4 TAGs.
[0115] In some embodiments, the RAR includes m TA information groups, wherein each of the m TA information groups includes a TA command field and a TAG identification field, and the TAG identification field in the i-th TA information group is used to indicate the TAG corresponding to the TA value indicated by the TA command field in the i-th TA information group, i is a positive integer, and 1≤i≤m.
[0116] For example, m=1, the RAR may be as shown in FIG8 , wherein the TA command field occupies 12 bits, the TAG identification field occupies 2 bits, and R represents a reserved or reserved field.
[0117] For another example, when m=1, the RAR can be as shown in Figure 9, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, and R represents a reserved or reserved field. Compared with Figure 8, the uplink grant (UL grant) field used to allocate uplink resources in Message 3 and the temporary C-RNTI field used to receive Message 4 are deleted. In other words, the RAR can be simplified. For the TA indication, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the Temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the content of the RAR, thereby reducing the signaling overhead of the RAR.
[0118] For another example, m=2, RAR can be as shown in Figure 10, where the TA command field occupies 12 bits, the TAG identification field occupies 2 bits, R represents a reserved or reserved field, the first TA information group includes the TA command 0 field and the TAG identification 0 field, and the second TA information group includes the TA command 1 field and the TAG identification 1 field, where the TAG identification 0 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 0 field, and the TAG identification 1 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 1 field.
[0119] For another example, if m = 2, the RAR can be as shown in Figure 11, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, and R represents a reserved or reserved field. The first TA information group includes the TA command 0 field and the TAG identifier 0 field, and the second TA information group includes the TA command 1 field and the TAG identifier 1 field. The TAG identifier 0 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 0 field, and the TAG identifier 1 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 1 field. Compared to Figure 10, the uplink grant (UL grant) field used to allocate uplink resources in Message 3 and the temporary C-RNTI field used to receive Message 4 are deleted. In other words, the RAR can be simplified. For TA indication, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the contents of the RAR, thereby reducing the signaling overhead of the RAR.
[0120] In some embodiments, the RAR includes a first information field;
[0121] The first information field is used to indicate the type of the RAR.
[0122] That is, in this embodiment, an information field indicating the RAR type may be added to the RAR, and the terminal device may learn the RAR type based on the information field, thereby obtaining information from the RAR more clearly and optimizing RAR transmission.
[0123] In some embodiments, the RAR type includes at least one of the following:
[0124] RAR is only used to obtain TA value;
[0125] Only used to obtain TA value and TAG identified RAR;
[0126] Only used to obtain TA value and uplink authorization RAR;
[0127] Only used to obtain TA value, TAG identifier and RAR for uplink authorization;
[0128] RAR is used for random access procedure.
[0129] Specifically, when the type of the RAR is a RAR for a random access procedure, the RAR is a conventional RAR (ie, an unsimplified RAR). After receiving the RAR for a random access procedure, the terminal device continues to perform the random access procedure.
[0130] In some embodiments, the terminal device ends the random access process after receiving the RAR used only to obtain the TA value.
[0131] In some embodiments, the terminal device ends the random access process after receiving the RAR used only to obtain the TA value and TAG identifier.
[0132] In some embodiments, the first information field occupies one bit.
[0133] In some embodiments, the first information field occupies two bits. Of course, the first information field may also occupy more bits.
[0134] For example, the type of RAR includes a RAR used only for obtaining a TA value. For example, the first information field occupies one bit, and a value of 0 indicates a RAR used only for obtaining a TA value, or a value of 1 indicates a RAR used only for obtaining a TA value.
[0135] For example, the RAR type includes a RAR used only for obtaining a TA value and a TAG identifier. For example, the first information field occupies one bit, and a value of 0 indicates a RAR used only for obtaining a TA value and a TAG identifier, or a value of 1 indicates a RAR used only for obtaining a TA value and a TAG identifier.
[0136] For example, the RAR type includes a RAR used only for obtaining a TA value and an uplink authorization. For example, the first information field occupies one bit, and a value of 0 indicates a RAR used only for obtaining a TA value and an uplink authorization, or a value of 1 indicates a RAR used only for obtaining a TA value and an uplink authorization.
[0137] For example, the type of RAR includes a RAR used only for obtaining a TA value, a TAG identifier, and an uplink authorization. For example, the first information field occupies one bit, and a value of 0 indicates that the RAR is used only for obtaining a TA value, a TAG identifier, and an uplink authorization, or a value of 1 indicates that the RAR is used only for obtaining a TA value, a TAG identifier, and an uplink authorization.
[0138] For example, the RAR type includes a RAR used for a random access procedure. For example, the first information field occupies one bit, and a value of 0 indicates a RAR used for a random access procedure, or a value of 1 indicates a RAR used for a random access procedure.
[0139] For example, the RAR type includes an RAR used only for obtaining the TA value and an RAR used in the random access process. For example, the first information field occupies one bit; a value of 0 indicates an RAR used only for obtaining the TA value, and a value of 1 indicates an RAR used in the random access process; or a value of 1 indicates an RAR used only for obtaining the TA value, and a value of 0 indicates an RAR used in the random access process.
[0140] For example, the types of RAR include RARs used only for obtaining the TA value and TAG identifier and RARs used in the random access process. For example, the first information field occupies one bit; a value of 0 indicates a RAR used only for obtaining the TA value and TAG identifier, and a value of 1 indicates a RAR used in the random access process; or a value of 1 indicates a RAR used only for obtaining the TA value and TAG identifier, and a value of 0 indicates a RAR used in the random access process.
[0141] For example, the types of RAR include an RAR used only for obtaining a TA value, a TAG identifier, and an uplink grant, and an RAR used in a random access process. For example, the first information field occupies one bit; a value of 0 indicates an RAR used only for obtaining a TA value, a TAG identifier, and an uplink grant, and a value of 1 indicates an RAR used in a random access process; or a value of 1 indicates an RAR used only for obtaining a TA value, a TAG identifier, and an uplink grant, and a value of 0 indicates an RAR used in a random access process.
[0142] For example, the types of RAR include RAR used only for obtaining TA value, RAR used only for obtaining TA value and TAG identifier, and RAR used for random access process. For example, the first information field occupies two bits; wherein, the value 00 represents RAR used only for obtaining TA value, the value 01 represents RAR used only for obtaining TA value and TAG identifier, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value and TAG identifier, the value 01 represents RAR used only for obtaining TA value, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value, the value 01 represents RAR used for obtaining TA value, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; For the RAR of the random access process, the value 10 indicates that the RAR is only used to obtain the TA value and the TAG identifier, and the value 11 is a reserved value; or, the value 00 indicates that the RAR is used for the random access process, the value 01 indicates that the RAR is only used to obtain the TA value, the value 10 indicates that the RAR is only used to obtain the TA value and the TAG identifier, and the value 11 is a reserved value; or, the value 00 indicates that the RAR is used for the random access process, the value 01 indicates that the RAR is only used to obtain the TA value and the TAG identifier, the value 10 indicates that the RAR is only used to obtain the TA value, and the value 11 is a reserved value.
[0143] For example, the types of RAR include RAR used only for obtaining TA value, RAR used only for obtaining TA value, TAG identifier and uplink authorization, and RAR used for random access process. For example, the first information field occupies two bits; wherein, the value 00 represents RAR used only for obtaining TA value, the value 01 represents RAR used only for obtaining TA value, TAG identifier and uplink authorization, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value, TAG identifier and uplink authorization, the value 01 represents RAR used only for obtaining TA value, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value, TAG identifier and uplink authorization, the value 01 represents RAR used only for obtaining TA value, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; The RAR of the access process, the value 10 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, and the value 11 is a reserved value; or, the value 00 indicates that it is used for the random access process, the value 01 indicates that it is only used to obtain the TA value, the value 10 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, and the value 11 is a reserved value; or, the value 00 indicates that it is used for the random access process, the value 01 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, the value 10 indicates that it is only used to obtain the TA value, and the value 11 is a reserved value.
[0144] For example, the types of RAR include RAR used only for obtaining TA value and TAG identifier, RAR used only for obtaining TA value, TAG identifier and uplink authorization, and RAR used for random access process. For example, the first information field occupies two bits; wherein, the value 00 represents RAR used only for obtaining TA value and TAG identifier, the value 01 represents RAR used only for obtaining TA value, TAG identifier and uplink authorization, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value, TAG identifier and uplink authorization, the value 01 represents RAR used only for obtaining TA value and TAG identifier, the value 10 represents RAR used for random access process, and the value 11 is a reserved value; or, the value 00 represents RAR used only for obtaining TA value and TAG identifier, and the value 01 represents RAR used for obtaining TA value and TAG identifier. For the RAR in the random access process, the value 10 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, and the value 11 is a reserved value; or, the value 00 indicates that it is used for the RAR in the random access process, the value 01 indicates that it is only used to obtain the TA value and TAG identifier, the value 10 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, and the value 11 is a reserved value; or, the value 00 indicates that it is used for the RAR in the random access process, the value 01 indicates that it is only used to obtain the TA value, TAG identifier and uplink authorization, the value 10 indicates that it is only used to obtain the TA value and TAG identifier, and the value 11 is a reserved value.
[0145] For example, the types of RAR include RAR used only for obtaining a TA value, RAR used only for obtaining a TA value and a TAG identifier, RAR used only for obtaining a TA value, a TAG identifier and an uplink grant, and RAR used for a random access process. For example, the first information field occupies two bits; the value 00 indicates a RAR used only to obtain a TA value, the value 01 indicates a RAR used only to obtain a TA value and a TAG identifier, the value 10 indicates a RAR used only to obtain a TA value, a TAG identifier, and an uplink authorization, and the value 11 indicates a RAR used for a random access process; or, the value 00 indicates a RAR used only to obtain a TA value, a TAG identifier, and an uplink authorization, the value 01 indicates a RAR used only to obtain a TA value and a TAG identifier, the value 10 indicates a RAR used only to obtain a TA value, and the value 11 indicates a RAR used for a random access process; or, the value 00 indicates a RAR used for a random access process, the value 01 indicates a RAR used only to obtain a TA value, the value 10 indicates a RAR used only to obtain a TA value and a TAG identifier, and the value 11 indicates a RAR used only to obtain a TA value, a TAG identifier, and an uplink authorization.
[0146] For example, m=1, the RAR may be as shown in FIG12 , wherein the TA command field occupies 12 bits, the TAG identification field occupies 2 bits, F represents the first information field, F occupies 1 bit, and R represents a reserved or reserved field.
[0147] For another example, when m=1, the RAR can be as shown in Figure 13, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, F represents the first information field, F occupies 1 bit, and R represents a reserved or reserved field. Compared with Figure 12, the uplink grant (UL grant) field used to allocate uplink resources in Message 3 and the temporary C-RNTI field used to receive Message 4 are deleted. In other words, the RAR can be simplified. For the TA indication, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the Temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the content of the RAR, thereby reducing the signaling overhead of the RAR.
[0148] For another example, m=2, RAR can be as shown in Figure 14, where the TA command field occupies 12 bits, the TAG identification field occupies 2 bits, F represents the first information field, F occupies 1 bit, R represents a reserved or reserved field, the first TA information group includes the TA command 0 field and the TAG identification 0 field, and the second TA information group includes the TA command 1 field and the TAG identification 1 field, where the TAG identification 0 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 0 field, and the TAG identification 1 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 1 field.
[0149] For another example, if m=2, the RAR can be as shown in Figure 15, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, F represents the first information field, F occupies 1 bit, and R represents a reserved or reserved field. The first TA information group includes the TA command 0 field and the TAG identifier 0 field, and the second TA information group includes the TA command 1 field and the TAG identifier 1 field. The TAG identifier 0 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 0 field, and the TAG identifier 1 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 1 field. Compared with Figure 14, the uplink grant (UL grant) field used to allocate uplink resources in Message 3 and the temporary C-RNTI field used to receive Message 4 are deleted. In other words, the RAR can be simplified. For TA indication, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the Temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the content of the RAR, thereby reducing the signaling overhead of the RAR.
[0150] In some embodiments, after the terminal device sends a scheduling request (SR) and a PRACH, the RAR sent to the terminal device by the first network node may include an uplink grant (UL Grant) field (which may occupy one or more bytes) and a TA command. The advantage of this is that the TA value required by the UE and the uplink transmission resources can be given in one RAR.
[0151] For example, if m = 1, the RAR can be as shown in Figure 16, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, F represents the first information field and occupies 1 bit, R represents the reserved or reserved field, and the uplink grant (UL grant) field occupies 3 bytes. In other words, the RAR can be simplified. For TA indications, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the Temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the RAR content, thereby reducing RAR signaling overhead.
[0152] For another example, if m=2, the RAR can be as shown in Figure 17, where the TA command field occupies 12 bits, the TAG identifier field occupies 2 bits, F represents the first information field and occupies 1 bit, R represents the reserved or reserved field, the uplink grant (UL grant) field occupies 3 bytes, the first TA information group includes the TA command 0 field and the TAG identifier 0 field, and the second TA information group includes the TA command 1 field and the TAG identifier 1 field. The TAG identifier 0 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 0 field, and the TAG identifier 1 field is used to indicate the TAG corresponding to the TA value indicated by the TA command 1 field. In other words, the RAR can be simplified. For TA indication, many contents are invalid, such as the UL grant used to allocate uplink resources in Message 3 and the Temporary C-RNTI used to receive Message 4. Therefore, there is room to simplify the contents of the RAR, thereby reducing the signaling overhead of the RAR.
[0153] For another example, m=1, the RAR may be as shown in FIG18 , wherein the TA command field occupies 12 bits, the TAG identification field occupies 2 bits, and F represents the first information field, which occupies 2 bits.
[0154] In some embodiments, different network nodes are configured with different target receive powers. Specifically, considering that different network nodes (such as TRPs) have different requirements for receiving PRACH power, the network device (such as NW) configures a target receive power specific to the network node (such as TRP) for the terminal device, i.e., P_PRACH,target,f,c.
[0155] In some embodiments, different network nodes are configured with different power boosting steps and / or power boosting counters. Specifically, after the terminal device sends PRACH to the network node (such as TRP), it will wait to receive RAR within a time window. If there is no RAR, the terminal device will retransmit PRACH after power ramping. For different network nodes (such as TRP), the network device (such as NW) should configure an independent power boosting step (including high priority and general priority random access processes) and an independent power boosting counter for the terminal device. The function of this counter is to stop raising the power after a certain number of times, so as to avoid excessive transmission power and interference.
[0156] For example, the RRC signaling for configuring an independent power boost step size (including high priority and general priority random access procedures) for the terminal device by the network device (such as NW) may include the following:
[0157] Power Ramping Step: the power-ramping factor; Power Ramping Step High Priority: the power-ramping factor in case of prioritized Random Access procedure.
[0158] For example, the network device (such as NW) configures an independent power boost step size for the terminal device (including high priority and normal priority random access processes) and the UE variables involved are as follows:
[0159] Random access preamble power ramping counter (PREAMBLE_POWER_RAMPING_COUNTER);
[0160] The random access preamble power ramping step size (PREAMBLE_POWER_RAMPING_STEP).
[0161] In some embodiments, before the terminal device sends the PRACH, the terminal device receives a PDCCH order (PDCCH order), wherein the PDCCH order is used to trigger the terminal device to send the PRACH.
[0162] For example, the terminal device receives a PDCCH order (PDCCH order) sent by a first network node, or the terminal device receives a PDCCH order (PDCCH order) sent by another network node (such as a second network node).
[0163] Specifically, when the network device (such as NW) believes that the terminal device needs to obtain TA from TRP, the network device (such as NW) can trigger the terminal device to send PRACH through PDCCH order. In the first step of the random access process, the terminal device sends PRACH based on the downlink reference reception time, and the network node x measures the arrival time of the PRACH to calculate the TA value of the UE for the network node x (for example, the network node x measures the correct TA value required by the terminal device through the random access preamble (Preamble) carried in the PRACH), and the network node x notifies the terminal device of the measured TA value in the form of MAC RAR, or the network node x notifies the network node y of the measured TA value, and then the network node y notifies the terminal device of the TA value obtained from the network node x in the form of MAC RAR.
[0164] Specifically, the PDCCH order (PDCCH order) can be completed through DCI format 1_0. For example, when DCI format 1_0 is scrambled by the cell radio network temporary identifier (Cell RNTI, C-RNTI) and the frequency domain resource assignment (FDRA) field is all 1, the terminal device should understand the DCI as a PDCCH order (PDCCH order). The network device (such as NW) provides some important parameters for the terminal device to send PRACH, such as the random access preamble index (Preamble index), SSB index (SSB index), PRACH mask index (PRACH mask index) (such as random access occasion (RACH occasion, RO)). When the terminal device believes that the DCI is a PDCCH order, it will send PRACH according to the following three important information indicated: Preamble index, SSB index, PRACH mask index (indicating the RO associated with the SSB). The network device (such as NW) measures the correct TA value required by the terminal device through the Preamble sent by the terminal device, and indicates the TA command to the terminal device through the RAR in the random access channel (RACH) process.
[0165] In some embodiments, the PDCCH command includes at least one of the following: a CSI-RS index, an uplink TCI state identifier (Identity, ID), and a joint TCI state ID.
[0166] Specifically, the CSI-RS index in the PDCCH command is associated with the path loss reference signal (PL RS) used to send PRACH. Since CSI-RS is the beamforming performed by the network for the UE, it has more precise spatial directionality than SSB and is a UE-specific downlink reference signal. Therefore, when the UE sends PRACH, it can also increase its uplink spatial directionality, thereby increasing the accuracy of the network's detection of PRACH.
[0167] Specifically, the uplink TCI state ID in the PDCCH command is associated with the uplink spatial filter (e.g., uplink beam) for transmitting the PRACH, and / or the downlink reference signal (DL RS) contained in the uplink TCI state ID is associated with the PL RS used to transmit the PRACH. For the uplink TCI state, in addition to the feature of including the SSB index or the CSI-RS index, the uplink TCI state can also directly include the PL RS, which can be different from the SSB index or the CSI-RS index, thereby providing more flexible uplink beamforming and power control functions.
[0168] Specifically, the joint TCI state ID in the PDCCH command is associated with the uplink spatial filter (such as an uplink beam) used to send the PRACH, and / or the DL RS included in the joint TCI state ID is associated with the PL RS used to send the PRACH.
[0169] It should be noted that the PL RS used by PRACH can be the CSI-RS index field in the PDCCH command. The CSI-RS index is different from the SSB index (cell-specific deployment) and can achieve terminal equipment (UE)-specific beamforming, thereby supporting PRACH transmission with finer spatial granularity.
[0170] Specifically, the uplink TCI state or the joint TCI state in the unified TCI state can allow the UE to refer to how to implement the uplink spatial transmission filter (beam) of the PRACH. In addition, the uplink TCI state or the DL RS contained in the joint TCI state in the unified TCI state can be used as the PL RS for sending the PRACH. For the general process of the unified TCI state, the network device (such as NW) configures a TCI state resource pool through RRC signaling, such as containing 128 TCI states, and then activates 8 TCI states or a combination thereof (including two joint TCI states or uplink TCI states) through MAC CE, and finally tells the UE which TCI state activated in the MAC CE is indicated through the TCI state indication field in the DCI, such as 3 bits.
[0171] That is, for the power control parameters in the PRACH transmission process, one of the important ones is PL RS, which is the reference signal for path loss measurement. The UE needs to use the PL RS to measure the downlink path loss. For multiple TRPs within the cell (Intra-cell), the SSB index or CSI-RS index or uplink TCI state identifier or DL RS contained in the joint TCI state indicated in the PDCCH command can be used as PL RS. The UE estimates the path loss through the SSB index or CSI-RS index or uplink TCI state identifier or DL RS in the joint TCI state of the cell indicated by the PDCCH command. This adjusts the uplink transmit power.
[0172] For example, the PDCCH command includes a CSI-RS index or an uplink TCI state ID or a joint TCI state ID.
[0173] For another example, the PDCCH command includes a CSI-RS index and an uplink TCI state ID.
[0174] For another example, the PDCCH command includes a CSI-RS index and a joint TCI state ID.
[0175] For another example, the PDCCH command includes the joint TCI state ID and the uplink TCI state ID.
[0176] For another example, the PDCCH command includes a CSI-RS index, a joint TCI state ID, and an uplink TCI state ID.
[0177] In some embodiments, the PDCCH command is associated with an activated PCI. That is, no information about the PCI is added to the PDCCH command, and the PDCCH command is limited to the additional PCI in the activated state.
[0178] For example, when this embodiment is applied to multiple network nodes between cells (e.g., multiple TRPs), the PDCCH command is associated with the activated Physical Cell Identifier (PCI). That is, no information about the PCI is added to the PDCCH command, and the PDCCH command is limited to the additional PCI in the activated state.
[0179] In some embodiments, the PDCCH command includes n bits; wherein the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0180] For example, when this embodiment is applied to multiple network nodes (such as multiple TRPs) between cells (Inter-cell), the PDCCH command includes n bits; wherein the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0181] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command, or the uplink TCI state ID, or the PCI index corresponding to the DL RS associated with the TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device. For example, n = 3. Of course, the value of n in this embodiment may also be other values, and this embodiment is not limited to this.
[0182] In some embodiments, when the n bits are used to indicate the CSI-RS index or uplink TCI state ID in the PDCCH command or the PCI corresponding to the DL RS associated with the TCI state ID, n = 10. Of course, the value of n in this embodiment may also be other values, and this embodiment is not limited to this.
[0183] Specifically, for inter-cell multi-TRPs, the PDCCH command must indicate not only the CSI-RS index but also the PCI from which the DL RS originates. Therefore, a 10-bit PCI or a 3-bit PCI index must be directly included in the PDCCH command. It should be noted that the PCI index is a re-encoding of the maximum 7 PCIs already configured for the UE, so a 3-bit PCI index is sufficient to reduce overhead.
[0184] In some embodiments, the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0185] For example, when this embodiment is applied to multiple network nodes (such as multiple TRPs) between cells (Inter-cell), the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell. For example, a value of 0 is used to indicate that the PDCCH command is associated with the activated PCI, and a value of 1 is used to indicate that the PDCCH command is associated with the PCI of the serving cell. For another example, a value of 1 is used to indicate that the PDCCH command is associated with the activated PCI, and a value of 0 is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0186] It should be noted that the activated PCI may also be referred to as additional PCI.
[0187] In some embodiments, the RAR is received by the terminal device from a first network node, the PDCCH command is received by the terminal device from a second network node, and the PRACH is sent by the terminal device to the second network node. That is, the RAR corresponds to the first network node, and the PDCCH command and the PRACH correspond to the second network node;
[0188] The first network node is configured with a Type 1 Common Search Space (CSS), and the second network node is not configured with a Type 1 CSS.
[0189] That is, the terminal device receives the RAR sent by the first network node (such as TRP#1), the terminal device receives the PDCCH command sent by the second network node (such as TRP#2), and the terminal device sends PRACH to the second network node (such as TRP#2).
[0190] Compared with the traditional single TRP RACH process, the NW can send the PDCCH command to the second network node to avoid the congestion of the downlink control channel of the first network node, so that the UE can send PRACH to the second network node that needs TA acquisition, and the second node calculates the TA value corresponding to the UE.
[0191] In some embodiments, the m TA command fields included in the RAR are used to indicate TA values from the second network node. That is, the m TA command fields included in the RAR are determined by the first network node based on TA values obtained from other network nodes.
[0192] It should be noted that RAR searches for PDCCH only from a Type 1 Common Search Space (CSS). This CSS is associated with a control resource set (CORESET), which is configured with an RRC parameter, the CORESETPoolIndex (corresponding to a TRP). In other words, a terminal device can only receive RAR from a specific network node (TRP).
[0193] For example, the flowchart of the TA acquisition process between multiple TRPs can be shown in Figure 19, where TRP #1 is the TRP that sends the RAR, and TRP #2 is the TRP that the UE needs to obtain the TA. The network device (such as NW) sends the PDCCH order (step 0) to the UE through TRP #2 to trigger the PRACH (step 1). TRP #2 measures the uplink arrival time difference of the UE by measuring the random access preamble sequence of the PRACH at the RACH opportunity (RO) and calculates the TA value that the UE should adjust. The TA value is passed to TRP #1 through the backhaul between the TRPs. The reception of RAR in step 2 can be understood as the MAC layer signaling carried by the PDCCH (PDCCH RAR) and its scheduled PDSCH (PDSCH RAR). In addition, the UE expects the DMRS of the PDCCH carrying the RAR to maintain a QCL relationship with the PDSCH DRMS.
[0194] In some embodiments, the DMRS in the PDCCH command and the PL RS of the PRACH have a QCL relationship. Since the PDCCH command and the PRACH can correspond to the same TRP, that is, as shown between steps 0 and 1 in Figure 19, the DMRS in the PDCCH command and the PL RS of the PRACH have a QCL relationship.
[0195] In some embodiments, there is no QCL relationship between the DMRS in the PDCCH command and the DMRS in the PDCCH in the RAR. That is, as shown between step 0 and step 2 in FIG19 , there is no QCL relationship between the DMRS in the PDCCH command and the DMRS in the PDCCH in the RAR.
[0196] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0197] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set (CORESET) where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 CSS associated with the RAR.
[0198] Specifically, as shown in Figure 19, for the PDCCH command in step 0, the terminal device uses the TCI state or QCL assumption indicated by the CORESET where the PDCCH corresponding to the PDCCH command is located for reception. For the PDCCH DMRS in the RAR in step 2, the terminal device uses the TCI state or QCL assumption indicated by the CORESET associated with the Type 1 CSS associated with the RAR for reception.
[0199] It should be noted that the TCI state is typically configured through the UE's dedicated RRC, activated through MAC CE, and finally dynamically indicated by the DCI. For the QCL assumption, the QCL relationship between each step can be pre-defined in the protocol. This has the advantage of being usable even when the UE does not have dedicated RRC configuration, but the disadvantage is limited flexibility.
[0200] In some embodiments, the PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions. Specifically, for example, the terminal device does not expect the PDCCH order and the PDCCH in the RAR to be received using the same TCI state or QCL assumption. That is, for the behavior of the UE, it is not expected that the PDCCH order and the subsequent RAR come from the same TRP and use the same downlink TCI state or QCL assumption. Described from another perspective, the base station will not send the PDCCH order and RAR from the same TRP.
[0201] It should be noted that the CORESET commanded by the PDCCH and the CORESET associated with the Type 1 CSS where the RAR is located come from different TRPs and may have different CORESETPoolIndex.
[0202] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH order for transmitting the PRACH. That is, as shown between steps 1 and 2 in FIG19 , there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH order for transmitting the PRACH.
[0203] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0204] Specifically, as shown in Figure 19, for the CSI-RS index or uplink TCI state ID or joint TCI state ID referenced by the UE for PRACH transmission in step 1 (i.e., the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for PRACH transmission), the UE can ignore its effect on the RAR. For the PDSCH DMRS in the RAR in step 2, the UE uses the TCI state or QCL assumption indicated in the DCI (PDCCH RAR) for reception.
[0205] In some embodiments, the RAR is received by the terminal device from a first network node, and the PRACH is sent by the terminal device to the first network node; wherein the first network node is configured with a first type 1 CSS.
[0206] Specifically, the RAR and the PRACH correspond to the same network node; wherein the network node corresponding to the RAR and the PRACH is configured with a first type 1 CSS, and the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH. Optionally, the first type 1 CSS is deactivated after the terminal device receives the RAR.
[0207] Specifically, it is allowed to configure a Type 1 CSS for each TRP to receive RAR. The NW sends the RAR from TRP #2 (not necessarily from TRP #1). In steps 0, 1, and 2, the UE's behavior is to send to or receive from TRP #2, so there is no QCL conflict. For the first Type 1 CSS, it can be pre-configured. Only after the UE receives a PDCCH order or sends a PRACH, the first Type 1 CSS is considered to be activated. The UE then searches for PDCCH on this Type 1 CSS, which schedules the PDSCH carrying the RAR.
[0208] In some embodiments, the PDCCH command and the RAR are both received by the terminal device from a first network node, and the PRACH is sent by the terminal device to a second network node. That is, the PDCCH command and the RAR correspond to the first network node, and the PRACH corresponds to the second network node.
[0209] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0210] That is, the terminal device receives the RAR and PDCCH commands sent by the first network node (such as TRP#1), and the terminal device sends PRACH to the second network node (such as TRP#2).
[0211] In this embodiment, when the second network does not have a downlink control channel, the network may use the first network node to send a PDCCH command to trigger the UE to send a PRACH to the second network node, so that the second network node obtains the TA value of the UE.
[0212] In some embodiments, the m TA command fields included in the RAR are determined by the first network node based on TA values obtained from other network nodes.
[0213] It should be noted that RAR searches for PDCCH only from a Type 1 Common Search Space (CSS). This CSS is associated with a control resource set (CORESET), which is configured with an RRC parameter, the CORESETPoolIndex (corresponding to a TRP). In other words, a terminal device can only receive RAR from a specific network node (TRP).
[0214] For example, the flowchart of the TA acquisition process between multiple TRPs can be shown in Figure 20. The network device (such as NW) sends a PDCCH command to the UE through TRP #1 (step 0) to trigger PRACH (step 1). TRP #2 performs uplink synchronization by measuring the preamble sequence of PRACH on the RACH occasion (RO) and calculates the TA value that the UE should adjust. Subsequently, the UE's TA value for TRP #2 is transmitted to TRP #1 through the backhaul link between TRP #1 and TRP #2. TRP #1 notifies the TA value through the RAR in (step 2).
[0215] In some embodiments, the DMRS in the PDCCH command does not have a QCL relationship with the PL RS used to transmit the PRACH. That is, in Figure 20, the PDCCH command and the PRACH correspond to different TRPs, and between steps 0 and 1, the DMRS in the PDCCH command does not have a QCL relationship with the PL RS of the PRACH.
[0216] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set (CORESET) in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0217] For example, the terminal device may receive the data using the TCI state or QCL assumption indicated by the CORESET where the PDCCH command is located. Furthermore, the CSI-RS index or uplink TCI state ID or joint TCI state ID contained in the PDCCH command may be from another TRP, i.e., having a CORESETPoolIndex different from that of the CORESET where the PDCCH command is located.
[0218] In some embodiments, in FIG20 , between step 0 and step 2, a QCL relationship is established between the DMRS ordered by the PDCCH and the PDCCH DMRS carrying the RAR.
[0219] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH.
[0220] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0221] It should be noted that for uplink power control, i.e., PL RS, the CSI-RS index or uplink TCI state ID or joint TCI state ID in the PDCCH command in step 0 is used as the PL RS of PRACH. The CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command and the PDCCH command come from different TRPs, i.e., different CORESETPoolIndex.
[0222] In some embodiments, the RAR and the PRACH correspond to the same network node; wherein the network node corresponding to the RAR and the PRACH is configured with a first type 1 CSS. Optionally, the first type 1 CSS is activated after the terminal device receives the PDCCH command, or after the terminal device sends the PRACH.
[0223] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0224] In some embodiments, the network node corresponding to the PDCCH command is different from the network nodes corresponding to the RAR and the PRACH.
[0225] In some embodiments, the network node corresponding to the PDCCH command is configured with a second type 1 CSS. Optionally, the second type 1 CSS is a regular type 1 CSS.
[0226] In some embodiments, the RAR is received by the terminal device from a first network node, the PRACH is sent by the terminal device to the first network node, and the PDCCH command is received by the terminal device from a second network node. That is, the RAR and the PRACH correspond to the first network node, and the PDCCH command corresponds to the second network node.
[0227] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0228] That is, the terminal device receives the RAR sent by the first network node (such as TRP#1), the terminal device sends PRACH to the first network node (such as TRP#1), and the terminal device receives the PDCCH command sent by the second network node (such as TRP#2).
[0229] In this embodiment, the network can avoid congestion of the control channel of the first network node and use the second network node to send the PDCCH command, making the coordination between network nodes more flexible.
[0230] For example, the flowchart of the TA acquisition process between multiple TRPs can be shown in Figure 21. A network device (e.g., NW) triggers the PRACH (step 1) by sending a PDCCH command to the UE via TRP #2 (step 0). TRP #2 notifies TRP #1 via the backhaul network to receive the PRACH. TRP #1 synchronizes uplink data by measuring the PRACH preamble sequence on the RACH occasion and calculates the TA value that the UE should adjust. TRP #1 then notifies the UE of this TA value via the RAR (step 2).
[0231] It should be noted that the NW sends the PDCCH order from TRP #2. The advantage is that when TRP #1 is congested in the downlink control channel, the PDCCH order can still be sent in time, so that the UE can obtain uplink synchronization as soon as possible.
[0232] In some embodiments, there is no QCL relationship between the DMRS of the PDCCH command and the PL RS used to send the PRACH. Optionally, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0233] In some embodiments, there is no QCL relationship between the DMRS ordered by the PDCCH and the DMRS of the PDCCH in the RAR.
[0234] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0235] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 CSS associated with the RAR.
[0236] In some embodiments, the PDCCH command and the PDCCH carrying the RAR are received using different TCI states or QCL assumptions. That is, the terminal device does not expect the PDCCH command and the PDCCH in the RAR to be received using the same TCI state or QCL assumption.
[0237] In some embodiments, as shown in FIG. 21 , between Step 1 and Step 2, the QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index indicated in the PDCCH order for transmitting the PRACH is determined.
[0238] In some embodiments, the RAR and the PRACH correspond to the same network node; wherein the network node corresponding to the RAR and the PRACH is configured with a first type 1 CSS. Optionally, the first type 1 CSS is activated after the terminal device receives the PDCCH command, or after the terminal device sends the PRACH.
[0239] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0240] In some embodiments, the network node corresponding to the PDCCH command is different from the network nodes corresponding to the RAR and the PRACH.
[0241] In some embodiments, the network node corresponding to the PDCCH command is configured with a second type 1 CSS. Optionally, the second type 1 CSS is a regular type 1 CSS.
[0242] In some embodiments, the above S210 may specifically include:
[0243] When the TA timer of the first TAG times out, the terminal device sends the PRACH to the network node corresponding to the first TAG, where the network node corresponding to the first TAG is different from the network node corresponding to the RAR.
[0244] That is, the embodiment of the present application triggers the terminal device to send PRACH based on the TA timer.
[0245] In some embodiments, the network node corresponding to the RAR is configured with a Type 1 CSS, and the network node corresponding to the first TAG is not configured with a Type 1 CSS.
[0246] In some embodiments, the m TA command fields included in the RAR are used to indicate a TA value from a network node receiving the PRACH. That is, the m TA command fields included in the RAR are determined by the network node corresponding to the RAR based on TA values obtained from other network nodes.
[0247] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID used to transmit the PRACH.
[0248] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0249] For example, the process of triggering a terminal device to send a PRACH based on a TA timer can be shown in Figure 22. Step 1: The terminal device sends a PRACH to TRP#2. Step 2: The terminal device receives the RAR sent by TRP#1. When the TA timer of a certain TAG expires, the UE sends a PRACH to the TRP corresponding to the TAG (TRP#2 in Figure 22). The NW then estimates the TA value and transmits it to TRP#1 via the backhaul between TRPs. TRP#1 then sends the RAR to the UE.
[0250] Therefore, in an embodiment of the present application, the terminal device can determine the TA values corresponding to m TAGs based on the m TA command fields in the RAR, so that the TA value can be obtained in the uplink transmission scenarios of intra-cell multi-TRP and inter-cell multi-TRP, thereby optimizing the uplink transmission in the multi-TRP scenario.
[0251] The embodiments of the present application solve the problem of a PDCCH command sent by the second network node conflicting with the QCL of the RAR sent by the first network node. Specifically, the terminal device uses the activated TCI state of the CORESET where the PDCCH command is located for receive beamforming to receive the PDCCH command, and uses the activated TCI state of the CORESET associated with the RAR-associated type 1 CSS to receive the RAR-associated PDCCH and PDSCH.
[0252] The embodiments of the present application solve the problem of a terminal device sending a PRACH to a second network node and a QCL conflict with a RAR sent by a first network node. The terminal device uses the CSI-RS index or downlink TCI state ID or joint TCI state ID indicated in the PDCCH command to send the PRACH, and uses the activated TCI state of the RAR-associated type 1 CSS-associated CORESET to receive the RAR-associated PDCCH and PDSCH.
[0253] The embodiments of the present application solve the problem of a QCL conflict between a terminal device sending a PRACH to a second network node and a first network node sending a PDCCH command. The terminal device uses the CSI-RS index or downlink TCI state ID or joint TCI state ID indicated in the PDCCH command to send the PRACH, and the terminal device uses the activated TCI state of the CORESET where the PDCCH command is located to perform receive beamforming to receive the PDCCH command.
[0254] The above, in combination with Figures 7 to 22, describes in detail the terminal device side and the first network node side embodiments of the present application. The following, in combination with Figure 23, describes in detail the second network node side embodiment of the present application. It should be understood that the second network node side embodiment corresponds to the terminal device side and the first network node side embodiment, and similar descriptions can refer to the terminal device side and the first network node side embodiments.
[0255] FIG23 is a schematic flowchart of a wireless communication method 300 according to an embodiment of the present application. As shown in FIG23 , the wireless communication method 300 may include at least part of the following contents:
[0256] S310, the second network node sends a PDCCH command, where the PDCCH command is used to trigger the terminal device to send a PRACH;
[0257] The PDCCH command includes at least one of the following: a CSI-RS index, an uplink TCI state ID, and a joint TCI state ID;
[0258] The CSI-RS index is associated with the PL RS used to send the PRACH;
[0259] The uplink TCI state ID is associated with an uplink spatial filter used to send the PRACH, and / or the DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH;
[0260] The joint TCI state ID is associated with the uplink spatial filter used to send the PRACH, and / or the DL RS included in the joint TCI state ID is associated with the PL RS used to send the PRACH.
[0261] It should be understood that Figure 23 shows the steps or operations of the wireless communication method 300, but these steps or operations are only examples. The embodiments of the present application can also perform other operations or variations of the various operations in Figure 23.
[0262] In the embodiments of the present application, the network node may also be referred to as a TRP or other device with similar functions (such as a micro base station), but the present application does not limit this.
[0263] In some embodiments, the embodiments of the present application can be applied to multiple network nodes between cells (such as inter-cell multi-TRP), or the embodiments of the present application can be applied to multiple network nodes within a cell (such as intra-cell multi-TRP). For example, the terminal device needs to initiate a random access process for different network nodes (such as TRP) to obtain a TA value exclusive to each network node (such as TRP).
[0264] In some embodiments, multiple network nodes can support the TA acquisition process of multiple DCI (M-DCI), that is, each network node sends a message to the terminal device through DCI respectively; and / or, multiple network nodes can support the TA acquisition process of single DCI (S-DCI), that is, multiple network nodes send a message to the terminal device through one DCI.
[0265] For example, multiple TRPs (multi-TRP, MTRP) support the TA acquisition process for multiple DCIs (multi-DCI, M-DCI). In this case, there may not be a good backhaul connection between the M-DCI MTRPs, and each TRP completes independent scheduling of the same UE. Each TRP can be identified by "0" or "1" in CORESETPoolIndex.
[0266] For example, multiple TRPs (multi-TRP, MTRP) support the TA acquisition process for a single DCI (single-DCI, S-DCI). In this case, the TRPs can maintain good backhaul connectivity, allowing one TRP to schedule uplink and downlink transmissions between a UE and two TRPs. However, the CORESETPoolIndex parameter is not configured, or it only has a single value, either all "0" or all "1".
[0267] Specifically, the CSI-RS index in the PDCCH command is associated with the path loss reference signal (PL RS) used to send PRACH. Since CSI-RS is the beamforming performed by the network for the UE, it has more precise spatial directionality than SSB and is a UE-specific downlink reference signal. Therefore, when the UE sends PRACH, it can also increase its uplink spatial directionality, thereby increasing the accuracy of the network's detection of PRACH.
[0268] Specifically, the uplink TCI state ID in the PDCCH command is associated with the uplink spatial filter (e.g., uplink beam) for transmitting the PRACH, and / or the downlink reference signal (DL RS) contained in the uplink TCI state ID is associated with the PL RS used to transmit the PRACH. For the uplink TCI state, in addition to the feature of including the SSB index or the CSI-RS index, the uplink TCI state can also directly include the PL RS, which can be different from the SSB index or the CSI-RS index, thereby providing more flexible uplink beamforming and power control functions.
[0269] In some embodiments, the embodiments of the present application can be applied to a 4-step random access process or a 2-step random access process.
[0270] Specifically, the PDCCH order (PDCCH order) can be completed through DCI format 1_0. For example, when DCI format 1_0 is scrambled by the cell radio network temporary identifier (Cell RNTI, C-RNTI) and the frequency domain resource assignment (FDRA) field is all 1, the terminal device should understand the DCI as a PDCCH order (PDCCH order). The network device (such as NW) provides some important parameters for the terminal device to send PRACH, such as the random access preamble index (Preamble index), SSB index (SSB index), PRACH mask index (PRACH mask index) (such as random access occasion (RACH occasion, RO)). When the terminal device believes that the DCI is a PDCCH order, it will send PRACH according to the following three important information indicated: Preamble index, SSB index, PRACH mask index (indicating the RO associated with the SSB). The network device (such as NW) measures the correct TA value required by the terminal device through the Preamble sent by the terminal device, and indicates the TA command to the terminal device through the RAR in the random access channel (RACH) process.
[0271] It should be noted that the PL RS used by PRACH can be the CSI-RS index field in the PDCCH command. The CSI-RS index is different from the SSB index (cell-specific deployment) and can achieve terminal equipment (UE)-specific beamforming, thereby supporting PRACH transmission with finer spatial granularity.
[0272] Specifically, the uplink TCI state or the joint TCI state in the unified TCI state can allow the UE to refer to how to implement the uplink spatial transmission filter (beam) of the PRACH. In addition, the uplink TCI state or the DL RS contained in the joint TCI state in the unified TCI state can be used as the PL RS for sending the PRACH. For the general process of the unified TCI state, the network device (such as NW) configures a TCI state resource pool through RRC signaling, such as containing 128 TCI states, and then activates 8 TCI states or a combination thereof (including two joint TCI states or uplink TCI states) through MAC CE, and finally tells the UE which TCI state activated in the MAC CE is indicated through the TCI state indication field in the DCI, such as 3 bits.
[0273] For the power control parameters in the PRACH transmission process, one of the important ones is PL RS, which is the reference signal for path loss measurement. The UE needs to use this PL RS to measure the downlink path loss. For multiple TRPs within the cell (Intra-cell), the CSI-RS index indicated in the PDCCH command or the uplink TCI state identifier or the DL RS contained in the joint TCI state can be used as the PL RS. The UE estimates the path loss through the CSI-RS index or uplink TCI state identifier or DL RS in the joint TCI state of the cell indicated by the PDCCH command. This adjusts the uplink transmit power.
[0274] For example, the PDCCH command includes a CSI-RS index or an uplink TCI state ID or a joint TCI state ID.
[0275] For another example, the PDCCH command includes a CSI-RS index and an uplink TCI state ID.
[0276] For another example, the PDCCH command includes a CSI-RS index and a joint TCI state ID.
[0277] For another example, the PDCCH command includes the joint TCI state ID and the uplink TCI state ID.
[0278] For another example, the PDCCH command includes a CSI-RS index, a joint TCI state ID, and an uplink TCI state ID.
[0279] In some embodiments, different network nodes are configured with different target receive powers. Specifically, considering that different network nodes (such as TRPs) have different requirements for receiving PRACH power, the network device (such as NW) configures a target receive power specific to the network node (such as TRP) for the terminal device, i.e., P_PRACH,target,f,c.
[0280] In some embodiments, different network nodes are configured with different power boosting steps and / or power boosting counters. Specifically, after the terminal device sends PRACH to the network node (such as TRP), it will wait to receive RAR within a time window. If there is no RAR, the terminal device will retransmit PRACH after power ramping. For different network nodes (such as TRP), the network device (such as NW) should configure an independent power boosting step (including high priority and general priority random access processes) and an independent power boosting counter for the terminal device. The function of this counter is to stop raising the power after a certain number of times, so as to avoid excessive transmission power and interference.
[0281] In some embodiments, the PDCCH command is associated with an activated Physical Cell Identifier (PCI), that is, no information about the PCI is added to the PDCCH command, and the PDCCH command is limited to the additional PCI in the activated state.
[0282] For example, when this embodiment is applied to multiple network nodes between cells (e.g., multiple TRPs), the PDCCH command is associated with the activated Physical Cell Identifier (PCI). That is, no information about the PCI is added to the PDCCH command, and the PDCCH command is limited to the additional PCI in the activated state.
[0283] In some embodiments, the PDCCH command includes n bits; wherein the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0284] For example, when this embodiment is applied to multiple network nodes (such as multiple TRPs) between cells (Inter-cell), the PDCCH command includes n bits; wherein the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID associated DL RS, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID associated DL RS, and n is a positive integer.
[0285] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command, or the uplink TCI state ID, or the PCI index corresponding to the DL RS associated with the TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device. For example, n = 3. Of course, the value of n in this embodiment may also be other values, and this embodiment is not limited to this.
[0286] In some embodiments, when the n bits are used to indicate the CSI-RS index or uplink TCI state ID in the PDCCH command or the PCI corresponding to the DL RS associated with the TCI state ID, n = 10. Of course, the value of n in this embodiment may also be other values, and this embodiment is not limited to this.
[0287] Specifically, for inter-cell multi-TRPs, the PDCCH command must indicate not only the SSB index or CSI-RS index but also the PCI from which the DL RS comes. Therefore, a 10-bit PCI or a 3-bit PCI index must be directly added to the PDCCH command. It should be noted that the PCI index is a re-encoding of the maximum 7 PCIs already configured for the UE, so a 3-bit PCI index is sufficient to reduce overhead.
[0288] In some embodiments, the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0289] For example, when this embodiment is applied to multiple network nodes (such as multiple TRPs) between cells (Inter-cell), the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell. For example, a value of 0 is used to indicate that the PDCCH command is associated with the activated PCI, and a value of 1 is used to indicate that the PDCCH command is associated with the PCI of the serving cell. For another example, a value of 1 is used to indicate that the PDCCH command is associated with the activated PCI, and a value of 0 is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0290] It should be noted that the activated PCI may also be referred to as additional PCI.
[0291] In some embodiments, the RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the second network node. That is, the RAR corresponding to the PRACH corresponds to the first network node, and the PDCCH command and the PRACH correspond to the second network node; wherein the first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0292] In some embodiments, there is no QCL relationship between the DMRS ordered by the PDCCH and the DMRS of the PDCCH in the RAR.
[0293] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0294] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 CSS associated with the RAR.
[0295] In some embodiments, the PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
[0296] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH.
[0297] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0298] In some embodiments, the RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node. That is, the RAR corresponding to the PRACH and the PRACH correspond to the first network node.
[0299] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0300] In some embodiments, there is no QCL relationship between the DMRS of the PDCCH command and the PL RS used to send the PRACH. Optionally, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0301] In some embodiments, the RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node. That is, the RAR corresponding to the PRACH and the PRACH correspond to the first network node.
[0302] The first network node is configured with a first type 1 CSS, and the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
[0303] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0304] In some embodiments, the second network node is configured with a second Type 1 CSS.
[0305] Therefore, in an embodiment of the present application, the terminal device can determine the PL RS used to send PRACH and / or the uplink spatial filter for sending PRACH based on at least one of the CSI-RS index, uplink TCI state ID, and joint TCI state ID contained in the PDCCH command, thereby optimizing PRACH transmission.
[0306] The above text, in combination with Figures 7 to 23, describes in detail the method embodiment of the present application. The following text, in combination with Figures 24 to 29, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.
[0307] FIG24 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG24 , the terminal device 400 includes:
[0308] The communication unit 410 is configured to send a physical random access channel PRACH;
[0309] The communication unit 410 is further configured to receive a random access response RAR; wherein the RAR includes m timing advance TA command fields, the m TA command fields being respectively used to indicate TA values corresponding to m timing advance groups TAG, where m is a positive integer, and m=1 or m≥2.
[0310] In some embodiments, the RAR includes m TA information groups, wherein each of the m TA information groups includes a TA command field and a TAG identification field, and the TAG identification field in the i-th TA information group is used to indicate the TAG corresponding to the TA value indicated by the TA command field in the i-th TA information group, i is a positive integer, and 1≤i≤m.
[0311] In some embodiments, the RAR includes a first information field;
[0312] The first information field is used to indicate the type of the RAR.
[0313] In some embodiments, the RAR type includes at least one of the following:
[0314] RAR is only used to obtain TA value;
[0315] Only used to obtain TA value and TAG identified RAR;
[0316] Only used to obtain TA value and uplink authorization RAR;
[0317] Only used to obtain TA value, TAG identifier and RAR for uplink authorization;
[0318] RAR is used for random access procedure.
[0319] In some embodiments, the communication unit 410 is further configured to terminate the random access procedure after receiving a RAR used only to obtain a TA value; or, the communication unit 410 is further configured to terminate the random access procedure after receiving a RAR used only to obtain a TA value and a TAG identifier.
[0320] In some embodiments, the first information field occupies one bit.
[0321] In some embodiments, the first information field occupies two bits.
[0322] In some embodiments, before the terminal device sends the PRACH, the communication unit 410 is further used to receive a physical downlink control channel PDCCH command, wherein the PDCCH command is used to trigger the terminal device to send the PRACH.
[0323] In some embodiments, the PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID;
[0324] The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH;
[0325] The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH;
[0326] The joint TCI state ID is associated with the uplink spatial filter used to send the PRACH, and / or the DL RS included in the joint TCI state ID is associated with the PL RS used to send the PRACH.
[0327] In some embodiments, the RAR is received by the terminal device from a first network node, the PDCCH command is received by the terminal device from a second network node, and the PRACH is sent by the terminal device to the second network node;
[0328] The first network node is configured with a Type 1 common search space CSS, and the second network node is not configured with a Type 1 CSS.
[0329] In some embodiments, the PDCCH command and the RAR are both received by the terminal device from a first network node, and the PRACH is sent by the terminal device to a second network node;
[0330] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0331] In some embodiments, the m TA command fields included in the RAR are used to indicate a TA value from the second network node.
[0332] In some embodiments, the RAR is received by the terminal device from a first network node, the PRACH is sent by the terminal device to the first network node, and the PDCCH command is received by the terminal device from a second network node;
[0333] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0334] In some embodiments, the demodulation reference signal DMRS ordered by the PDCCH does not have a quasi co-located QCL relationship with the DMRS of the PDCCH in the RAR.
[0335] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0336] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
[0337] In some embodiments, the PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
[0338] In some embodiments, there is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or uplink TCI state or joint TCI state indicated in the PDCCH command for sending the PRACH.
[0339] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0340] In some embodiments, there is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
[0341] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0342] In some embodiments, the RAR is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node;
[0343] The first network node is configured with a first type 1 CSS.
[0344] In some embodiments, the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
[0345] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0346] In some embodiments, the PDCCH command is received by the terminal device from the second network node.
[0347] In some embodiments, the second network node is configured with a second Type 1 CSS.
[0348] In some embodiments, the PDCCH command is associated with an activated physical cell identity PCI.
[0349] In some embodiments, the PDCCH command comprises n bits;
[0350] Among them, the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0351] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI index corresponding to the DL RS associated with the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
[0352] In some embodiments, n=3.
[0353] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
[0354] In some embodiments, the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0355] In some embodiments, the communication unit 410 is specifically configured to:
[0356] When the TA timer of the first TAG times out, the PRACH is sent to a network node corresponding to the first TAG, where the network node corresponding to the first TAG is different from the network node corresponding to the RAR.
[0357] In some embodiments, the network node corresponding to the RAR is configured with a Type 1 CSS, and the network node corresponding to the first TAG is not configured with a Type 1 CSS.
[0358] In some embodiments, the m TA command fields included in the RAR are used to indicate a TA value from a network node receiving the PRACH.
[0359] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID used to transmit the PRACH.
[0360] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0361] In some embodiments, different network nodes are configured with different target receive powers; and / or,
[0362] Different network nodes are configured with different power increase step sizes and / or power increase counters.
[0363] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0364] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 400 are respectively for realizing the corresponding processes of the terminal device in the method 200 shown in Figure 7. For the sake of brevity, they will not be repeated here.
[0365] FIG25 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. The network device 500 is a first network node. As shown in FIG25 , the network device 500 includes:
[0366] The communication unit 510 is configured to send a random access response RAR; wherein the RAR includes m timing advance TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m timing advance groups TAG, where m is a positive integer and m=1 or m≥2.
[0367] In some embodiments, the RAR includes m TA information groups, wherein each of the m TA information groups includes a TA command field and a TAG identification field, and the TAG identification field in the i-th TA information group is used to indicate the TAG corresponding to the TA value indicated by the TA command field in the i-th TA information group, i is a positive integer, and 1≤i≤m.
[0368] In some embodiments, the RAR includes a first information field;
[0369] The first information field is used to indicate the type of the RAR.
[0370] In some embodiments, the RAR type includes at least one of the following:
[0371] RAR is only used to obtain TA value;
[0372] Only used to obtain TA value and TAG identified RAR;
[0373] Only used to obtain TA value and uplink authorization RAR;
[0374] Only used to obtain TA value, TAG identifier and RAR for uplink authorization;
[0375] RAR is used for random access procedure.
[0376] In some embodiments, the first information field occupies one bit.
[0377] In some embodiments, the first information field occupies two bits.
[0378] In some embodiments, the physical random access channel PRACH corresponding to the RAR is triggered and sent by a physical downlink control channel PDCCH command.
[0379] In some embodiments, the PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID;
[0380] The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH;
[0381] The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH;
[0382] The joint TCI state ID is associated with the uplink spatial filter used to send the PRACH, and / or the DL RS included in the joint TCI state ID is associated with the PL RS used to send the PRACH.
[0383] In some embodiments, the PDCCH command is sent by the second network node to the terminal device, and the PRACH is sent by the terminal device to the second network node;
[0384] The first network node is configured with a Type 1 common search space CSS, and the second network node is not configured with a Type 1 CSS.
[0385] In some embodiments, the RAR and the PDCCH command are both sent by the first network node to the terminal device, and the PRACH is sent by the terminal device to the second network node;
[0386] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0387] In some embodiments, the m TA command fields included in the RAR are used to indicate a TA value from the second network node.
[0388] In some embodiments, the PRACH is sent by the terminal device to the first network node, and the PDCCH command is sent by the second network node to the terminal device;
[0389] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0390] In some embodiments, the demodulation reference signal DMRS ordered by the PDCCH does not have a quasi co-located QCL relationship with the DMRS of the PDCCH in the RAR.
[0391] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0392] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
[0393] In some embodiments, the PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
[0394] In some embodiments, there is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH.
[0395] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0396] In some embodiments, there is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
[0397] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0398] In some embodiments, the PRACH is sent by the terminal device to the first network node;
[0399] The first network node is configured with a first type 1 CSS.
[0400] In some embodiments, the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
[0401] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0402] In some embodiments, the PDCCH command is received by the terminal device from the second network node.
[0403] In some embodiments, the second network node is configured with a second Type 1 CSS.
[0404] In some embodiments, the PDCCH command is associated with an activated physical cell identity PCI.
[0405] In some embodiments, the PDCCH command comprises n bits;
[0406] Among them, the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0407] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI index corresponding to the DL RS associated with the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
[0408] In some embodiments, n=3.
[0409] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
[0410] In some embodiments, the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0411] In some embodiments, the PRACH corresponding to the RAR is sent to the network node corresponding to the first TAG when a TA timer of the first TAG times out, wherein the network node corresponding to the first TAG is different from the first network node.
[0412] In some embodiments, the first network node is configured with a Type 1 CSS, and the network node corresponding to the first TAG is not configured with a Type 1 CSS.
[0413] In some embodiments, the m TA command fields included in the RAR are used to indicate a TA value from a network node corresponding to the received first TAG.
[0414] In some embodiments, there is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID used to transmit the PRACH.
[0415] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0416] In some embodiments, different network nodes are configured with different target receive powers; and / or,
[0417] Different network nodes are configured with different power increase step sizes and / or power increase counters.
[0418] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0419] It should be understood that the network device 500 according to the embodiment of the present application may correspond to the first network node in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 500 are respectively for implementing the corresponding process of the first network node in the method 200 shown in Figure 7. For the sake of brevity, they will not be repeated here.
[0420] FIG26 shows a schematic block diagram of a network device 600 according to an embodiment of the present application. The network device 600 is a second network node. As shown in FIG26 , the network device 600 includes:
[0421] The communication unit 610 is configured to send a physical downlink control channel (PDCCH) command, wherein the PDCCH command is used to trigger the terminal device to send a PRACH.
[0422] The PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID;
[0423] The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH;
[0424] The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH;
[0425] The joint TCI state ID is associated with the uplink spatial filter used to send the PRACH, and / or the DL RS included in the joint TCI state ID is associated with the PL RS used to send the PRACH.
[0426] In some embodiments, the random access response RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the second network node;
[0427] The first network node is configured with a Type 1 common search space CSS, and the second network node is not configured with a Type 1 CSS.
[0428] In some embodiments, the RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node;
[0429] The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
[0430] In some embodiments, the demodulation reference signal DMRS ordered by the PDCCH does not have a quasi co-located QCL relationship with the DMRS of the PDCCH in the RAR.
[0431] In some embodiments, the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
[0432] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
[0433] In some embodiments, the PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
[0434] In some embodiments, there is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH.
[0435] In some embodiments, the PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
[0436] In some embodiments, there is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
[0437] In some embodiments, the PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set in which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set in which the PDCCH command is located.
[0438] In some embodiments, the RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node; wherein the first network node is configured with a first type 1 CSS, and the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
[0439] In some embodiments, the first Type 1 CSS is deactivated after the terminal device receives the RAR.
[0440] In some embodiments, the second network node is configured with a second Type 1 CSS.
[0441] In some embodiments, the PDCCH command is associated with an activated physical cell identity PCI.
[0442] In some embodiments, the PDCCH command comprises n bits;
[0443] Among them, the n bits are used to indicate the PCI corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the CSI-RS index in the PDCCH command or the uplink TCI state ID or the DL RS associated with the joint TCI state ID, and n is a positive integer.
[0444] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI index corresponding to the DL RS associated with the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
[0445] In some embodiments, n=3.
[0446] In some embodiments, when the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
[0447] In some embodiments, the PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
[0448] In some embodiments, different network nodes are configured with different target receive powers; and / or,
[0449] Different network nodes are configured with different power increase step sizes and / or power increase counters.
[0450] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0451] It should be understood that the network device 600 according to the embodiment of the present application may correspond to the second network node in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 600 are respectively for implementing the corresponding process of the second network node in the method 300 shown in Figure 23. For the sake of brevity, they will not be repeated here.
[0452] Figure 27 is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application. The communication device 700 shown in Figure 27 includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0453] In some embodiments, as shown in FIG27 , the communication device 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.
[0454] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .
[0455] In some embodiments, as shown in FIG. 27 , the communication device 700 may further include a transceiver 730 , and the processor 710 may control the transceiver 730 to communicate with other devices. Specifically, the transceiver 730 may send information or data to other devices, or receive information or data sent by other devices.
[0456] The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.
[0457] In some embodiments, the processor 710 can implement the functions of a processing unit in a terminal device, or the processor 710 can implement the functions of a processing unit in a network device (first network node and / or second network node), which will not be described here for the sake of brevity.
[0458] In some embodiments, the transceiver 730 may implement the functions of a communication unit in a terminal device, which will not be described in detail here for the sake of brevity.
[0459] In some embodiments, the transceiver 730 may implement the function of a communication unit in a network device (the first network node and / or the second network node), which will not be described in detail here for the sake of brevity.
[0460] In some embodiments, the communication device 700 may specifically be a network device (first network node and / or second network node) of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the network device (first network node and / or second network node) in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0461] In some embodiments, the communication device 700 may specifically be a terminal device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0462] Figure 28 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 800 shown in Figure 28 includes a processor 810, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.
[0463] In some embodiments, as shown in FIG28 , the apparatus 800 may further include a memory 820 , wherein the processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present application.
[0464] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .
[0465] In some embodiments, the processor 810 can implement the functions of a processing unit in a terminal device, or the processor 810 can implement the functions of a processing unit in a network device (first network node and / or second network node), which will not be described here for the sake of brevity.
[0466] In some embodiments, the apparatus 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips. Optionally, the processor 810 may be located inside or outside the chip.
[0467] In some embodiments, the input interface 830 may implement the function of a communication unit in a terminal device, or the input interface 830 may implement the function of a communication unit in a network device (the first network node and / or the second network node).
[0468] In some embodiments, the apparatus 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, specifically, to output information or data to other devices or chips. Optionally, the processor 810 may be located inside or outside the chip.
[0469] In some embodiments, the output interface 840 may implement the function of a communication unit in a terminal device, or the output interface 840 may implement the function of a communication unit in a network device.
[0470] In some embodiments, the device can be applied to the network device (first network node and / or second network node) in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network device (first network node and / or second network node) in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0471] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the terminal device in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0472] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, such as a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.
[0473] FIG29 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG29 , the communication system 900 includes a terminal device 910 , a first network node 920 , and a second network node 930 .
[0474] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, the first network node 920 can be used to implement the corresponding functions implemented by the first network node in the above method, and the second network node 930 can be used to implement the corresponding functions implemented by the second network node in the above method. For the sake of brevity, they will not be repeated here.
[0475] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0476] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0477] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
[0478] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0479] In some embodiments, the computer-readable storage medium can be applied to the network device (first network node and / or second network node) in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device (first network node and / or second network node) in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0480] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0481] An embodiment of the present application also provides a computer program product, including computer program instructions.
[0482] In some embodiments, the computer program product can be applied to the network device (first network node and / or second network node) in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device (first network node and / or second network node) in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0483] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0484] The embodiment of the present application also provides a computer program.
[0485] In some embodiments, the computer program can be applied to the network device (first network node and / or second network node) in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device (first network node and / or second network node) in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0486] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0487] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0488] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0489] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0490] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0491] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0492] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0493] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.
Claims
1. A wireless communication method, characterized in that: include: The terminal device sends a physical random access channel PRACH; The terminal device receives a random access response RAR; wherein the RAR includes m timing advance TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m timing advance groups TAG, m is a positive integer, and m=1 or m≥2.
2. The method according to claim 1, characterized in that The RAR includes m TA information groups, wherein each of the m TA information groups includes a TA command field and a TAG identification field, and the TAG identification field in the i-th TA information group is used to indicate the TAG corresponding to the TA value indicated by the TA command field in the i-th TA information group, i is a positive integer, and 1≤i≤m.
3. The method according to claim 1 or 2, characterized in that The RAR includes a first information field; The first information field is used to indicate the type of the RAR.
4. The method according to claim 3, characterized in that The type of the RAR includes at least one of the following: RAR is used only to obtain TA value; Only used to obtain the RAR of TA value and TAG mark; Only used to obtain TA value and uplink authorization RAR; Only used to obtain TA value, TAG identifier and RAR for uplink authorization; RAR for random access procedure.
5. The method according to claim 4, characterized in that The method further comprises: The terminal device ends the random access process after receiving the RAR used only for obtaining the TA value; or, The terminal device ends the random access process after receiving the RAR used only to obtain the TA value and TAG identifier.
6. The method according to any one of claims 3 to 5, characterized in that The first information field occupies one bit.
7. The method according to any one of claims 3 to 5, characterized in that The first information field occupies two bits.
8. The method according to any one of claims 1 to 7, characterized in that Before the terminal device sends the PRACH, the method further includes: The terminal device receives a physical downlink control channel PDCCH command, wherein the PDCCH command is used to trigger the terminal device to send a PRACH.
9. The method according to claim 8, characterized in that The PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID; The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH; The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or a downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH; The joint TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the DL RS included in the joint TCI state ID is associated with a PL RS used for sending the PRACH.
10. The method according to claim 8 or 9, characterized in that The RAR is received by the terminal device from the first network node, the PDCCH command is received by the terminal device from the second network node, and the PRACH is sent by the terminal device to the second network node; The first network node is configured with a type 1 common search space CSS, and the second network node is not configured with a type 1 CSS.
11. The method according to claim 8 or 9, characterized in that: The PDCCH command and the RAR are both received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the second network node; The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
12. The method according to claim 10 or 11, characterized in that The m TA command fields contained in the RAR are used to indicate a TA value from the second network node.
13. The method according to claim 8 or 9, characterized in that The RAR is received by the terminal device from the first network node, the PRACH is sent by the terminal device to the first network node, and the PDCCH command is received by the terminal device from the second network node; The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
14. The method according to claim 10 or 13, characterized in that There is no quasi co-location QCL relationship between the demodulation reference signal DMRS commanded by the PDCCH and the DMRS of the PDCCH carrying the RAR.
15. The method according to claim 14, characterized in that The PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
16. The method according to claim 15, characterized in that The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
17. The method according to any one of claims 14 to 16, characterized in that The PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
18. The method according to any one of claims 10 to 12, characterized in that There is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or the uplink TCI state or the joint TCI state indicated in the PDCCH command for sending the PRACH.
19. The method according to claim 18, characterized in that The PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH carrying the RAR.
20. The method according to claim 11 or 13, characterized in that There is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
21. The method of claim 20, wherein: The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set to which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set to which the PDCCH command is located.
22. The method according to claim 8 or 9, characterized in that The RAR is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node; The first network node is configured with a first type 1 CSS.
23. The method of claim 22, wherein: The first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
24. The method according to claim 22 or 23, characterized in that The first type 1 CSS is deactivated after the terminal device receives the RAR.
25. The method according to any one of claims 22 to 24, characterized in that The PDCCH command is received by the terminal device from the second network node.
26. The method of claim 25, wherein: The second network node is configured with a second Type 1 CSS.
27. The method according to any one of claims 8 to 26, characterized in that The PDCCH command is associated with the activated physical cell identity PCI.
28. The method according to any one of claims 8 to 26, characterized in that The PDCCH command comprises n bits; Among them, the n bits are used to indicate the PCI corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, and n is a positive integer.
29. The method of claim 28, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the PCI index corresponding to the DL RS associated with the uplink TCI state ID or the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
30. The method of claim 29, wherein: n=3。 31. The method of claim 28, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
32. The method according to any one of claims 8 to 26, characterized in that The PDCCH command includes one bit, wherein the value of the one bit is used to indicate the PDCCH command and the activation or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
33. The method according to any one of claims 1 to 7, characterized in that The terminal device sends a PRACH, including: When the TA timer of the first TAG times out, the terminal device sends the PRACH to the network node corresponding to the first TAG, wherein the network node corresponding to the first TAG is different from the network node corresponding to the RAR.
34. The method of claim 33, wherein: The network node corresponding to the RAR is configured with a Type 1 CSS, and the network node corresponding to the first TAG is not configured with a Type 1 CSS.
35. The method according to claim 33 or 34, characterized in that The m TA command fields included in the RAR are used to indicate a TA value from a network node receiving the PRACH.
36. The method according to any one of claims 33 to 35, characterized in that There is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID used to send the PRACH.
37. The method of claim 36, wherein: The PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH carrying the RAR.
38. A wireless communication method, characterized in that: include: The first network node sends a random access response RAR; wherein the RAR includes m timing advance TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m timing advance groups TAG, m is a positive integer, and m=1 or m≥2.
39. The method of claim 38, wherein: The RAR includes m TA information groups, wherein each of the m TA information groups includes a TA command field and a TAG identification field, and the TAG identification field in the i-th TA information group is used to indicate the TAG corresponding to the TA value indicated by the TA command field in the i-th TA information group, i is a positive integer, and 1≤i≤m.
40. The method according to claim 38 or 39, characterized in that The RAR includes a first information field; The first information field is used to indicate the type of the RAR.
41. The method of claim 40, wherein: The type of the RAR includes at least one of the following: RAR is used only to obtain TA value; Only used to obtain the RAR of TA value and TAG mark; Only used to obtain TA value and uplink authorization RAR; Only used to obtain TA value, TAG identifier and RAR for uplink authorization; RAR for random access procedure.
42. The method according to claim 40 or 41, characterized in that The first information field occupies one bit.
43. The method according to claim 40 or 41, characterized in that The first information field occupies two bits.
44. The method according to any one of claims 38 to 43, characterized in that The physical random access channel PRACH corresponding to the RAR is triggered and sent by a physical downlink control channel PDCCH command.
45. The method of claim 44, wherein: The PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID; The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH; The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or a downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH; The joint TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the DL RS included in the joint TCI state ID is associated with a PL RS used for sending the PRACH.
46. The method according to claim 44 or 45, characterized in that The PDCCH command is sent by the second network node to the terminal device, and the PRACH is sent by the terminal device to the second network node; The first network node is configured with a type 1 common search space CSS, and the second network node is not configured with a type 1 CSS.
47. The method of claim 44 or 45, wherein: The RAR and the PDCCH command are both sent by the first network node to the terminal device, and the PRACH is sent by the terminal device to the second network node; The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
48. The method according to claim 46 or 47, characterized in that The m TA command fields contained in the RAR are used to indicate a TA value from the second network node.
49. The method of claim 44 or 45, wherein: The PRACH is sent by the terminal device to the first network node, and the PDCCH command is sent by the second network node to the terminal device; The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
50. The method of claim 46 or 49, wherein: There is no quasi co-location QCL relationship between the demodulation reference signal DMRS of the PDCCH command and the DMRS of the PDCCH in the RAR.
51. The method of claim 50, wherein: The PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
52. The method of claim 51, wherein: The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
53. The method according to any one of claims 50 to 52, characterized in that The PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
54. The method according to any one of claims 46 to 48, characterized in that There is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending the PRACH.
55. The method of claim 54, wherein: The PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
56. The method of claim 47 or 49, wherein: There is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
57. The method of claim 56, wherein: The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set to which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set to which the PDCCH command is located.
58. The method of claim 44 or 45, wherein: The PRACH is sent by the terminal device to the first network node; The first network node is configured with a first type 1 CSS.
59. The method of claim 58, wherein: The first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
60. The method of claim 58 or 59, wherein: The first type 1 CSS is deactivated after the terminal device receives the RAR.
61. The method according to any one of claims 58 to 60, characterized in that The PDCCH command is received by the terminal device from the second network node.
62. The method of claim 61, wherein: The second network node is configured with a second Type 1 CSS.
63. The method according to any one of claims 44 to 62, characterized in that The PDCCH command is associated with the activated physical cell identity PCI.
64. The method of any one of claims 44 to 62, wherein: The PDCCH command comprises n bits; Among them, the n bits are used to indicate the PCI corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, and n is a positive integer.
65. The method of claim 64, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the PCI index corresponding to the DL RS associated with the uplink TCI state ID or the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
66. The method of claim 65, wherein: n=3。 67. The method of claim 64, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
68. The method of any one of claims 44 to 62, wherein: The PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
69. The method according to any one of claims 38 to 43, characterized in that The PRACH corresponding to the RAR is sent to the network node corresponding to the first TAG when the TA timer of the first TAG times out, wherein the network node corresponding to the first TAG is different from the first network node.
70. The method of claim 69, wherein: The first network node is configured with a Type 1 CSS, and the network node corresponding to the first TAG is not configured with a Type 1 CSS.
71. The method of claim 69 or 70, wherein: The m TA command fields contained in the RAR are used to indicate a TA value from a network node corresponding to the received first TAG.
72. The method according to any one of claims 69 to 71, characterized in that There is no QCL relationship between the DMRS of the PDSCH in the RAR and the CSI-RS index or uplink TCI state ID or joint TCI state ID used to send the PRACH.
73. The method of claim 72, wherein: The PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
74. The method according to any one of claims 38 to 73, characterized in that Different network nodes are configured with different target received powers; and / or, Different network nodes are configured with different power increase step sizes and / or power increase counters.
75. A method of wireless communication, characterized in that: include: The second network node sends a physical downlink control channel PDCCH command, wherein the PDCCH command is used to trigger the terminal device to send a PRACH; The PDCCH command includes at least one of the following: a channel state information reference signal CSI-RS index, an uplink transmission configuration indication TCI state identifier ID, and a joint TCI state ID; The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH; The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or a downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH; The joint TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the DL RS included in the joint TCI state ID is associated with a PL RS used for sending the PRACH.
76. The method of claim 75, wherein: The random access response RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the second network node; The first network node is configured with a type 1 common search space CSS, and the second network node is not configured with a type 1 CSS.
77. The method of claim 75, wherein: The RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node; The first network node is configured with a Type 1 CSS, and the second network node is not configured with a Type 1 CSS.
78. The method of claim 76, wherein: There is no quasi co-location QCL relationship between the demodulation reference signal DMRS of the PDCCH command and the DMRS of the PDCCH in the RAR.
79. The method of claim 78, wherein: The PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated TCI states, or the PDCCH command and the PDCCH in the RAR are respectively received using their respective configured and / or activated QCL assumptions.
80. The method of claim 79, wherein: The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set where the corresponding PDCCH is located, and / or the PDCCH in the RAR is received using the TCI state or QCL assumption indicated by the control resource set associated with the type 1 common search space CSS associated with the RAR.
81. The method of any one of claims 78 to 80, wherein: The PDCCH order and the PDCCH in the RAR are received using different TCI states or QCL assumptions.
82. The method of claim 76, wherein: There is no QCL relationship between the DMRS of the physical downlink shared channel PDSCH in the RAR and the CSI-RS index or the uplink TCI state ID or the joint TCI state ID indicated in the PDCCH command for sending the PRACH.
83. The method of claim 82, wherein: The PDSCH in the RAR is received using the TCI state or QCL assumption indicated in the PDCCH in the RAR.
84. The method of claim 77, wherein: There is no QCL relationship between the DMRS ordered by the PDCCH and the PL RS used to send the PRACH.
85. The method of claim 84, wherein: The PDCCH command is received using the TCI state or QCL assumption indicated by the control resource set to which it is located, and the CSI-RS index or uplink TCI state ID or joint TCI state ID indicated in the PDCCH command for sending PRACH has a control resource set pool index different from the control resource set to which the PDCCH command is located.
86. The method of claim 75, wherein: The RAR corresponding to the PRACH is received by the terminal device from the first network node, and the PRACH is sent by the terminal device to the first network node; wherein the first network node is configured with a first type 1 CSS, and the first type 1 CSS is activated after the terminal device receives the PDCCH command, or the first type 1 CSS is activated after the terminal device sends the PRACH.
87. The method of claim 86, wherein: The first type 1 CSS is deactivated after the terminal device receives the RAR.
88. The method of claim 86 or 87, wherein: The second network node is configured with a second Type 1 CSS.
89. The method according to any one of claims 75 to 88, characterized in that The PDCCH command is associated with the activated physical cell identity PCI.
90. The method of any one of claims 75 to 88, wherein: The PDCCH command comprises n bits; Among them, the n bits are used to indicate the PCI corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, or the n bits are used to indicate the PCI index corresponding to the DL RS associated with the CSI-RS index in the PDCCH command or the uplink TCI state ID or the joint TCI state ID, and n is a positive integer.
91. The method of claim 90, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the PCI index corresponding to the DL RS associated with the uplink TCI state ID or the joint TCI state ID, the PCI index is obtained based on further encoding of multiple PCIs configured for the terminal device.
92. The method of claim 91, wherein: n=3。 93. The method of claim 90, wherein: In the case where the n bits are used to indicate the CSI-RS index in the PDCCH command or the uplink TCI state ID or the PCI corresponding to the DL RS associated with the joint TCI state ID, n=10.
94. The method of any one of claims 75 to 90, wherein: The PDCCH command includes one bit, wherein the value of the one bit is used to indicate that the PDCCH command is associated with the activated PCI, or the value of the one bit is used to indicate that the PDCCH command is associated with the PCI of the serving cell.
95. The method of any one of claims 75 to 94, wherein: Different network nodes are configured with different target receive powers; and / or, Different network nodes are configured with different power increase step sizes and / or power increase counters.
96. A terminal device, characterized in that: include: A communication unit, configured to send a physical random access channel PRACH; The communication unit is also used to receive a random access response RAR; wherein the RAR includes m timing advance TA command fields, and the m TA command fields are respectively used to indicate TA values corresponding to m timing advance groups TAG, m is a positive integer, and m=1 or m≥2.
97. A network device, characterized in that: The network device is a first network node, and the network device includes: A communication unit, used to send a random access response RAR; wherein the RAR includes m timing advance TA command fields, and the m TA command fields are used to indicate TA values corresponding to m timing advance groups TAG respectively, m is a positive integer, and m=1 or m≥2.
98. A network device, characterized in that: The network device is a second network node, and the network device includes: A communication unit, used for sending a physical downlink control channel PDCCH command, wherein the PDCCH command is used to trigger the terminal device to send a PRACH; The PDCCH command includes at least one of the following: channel state information reference signal CSI-RS index, uplink transmission configuration Set the TCI status ID and combine it with the TCI status ID; The CSI-RS index is associated with a path loss reference signal PL RS used to send the PRACH; The uplink TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or a downlink reference signal DL RS included in the uplink TCI state ID is associated with a PL RS used to send the PRACH; The joint TCI state ID is associated with an uplink spatial filter for sending the PRACH, and / or the DL RS included in the joint TCI state ID is associated with a PL RS used for sending the PRACH.
99. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 37.
100. A network device, characterized in that: The network device is a first network node, and the network device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the method as described in any one of claims 38 to 74.
101. A network device, characterized in that: The network device is a second network node, and the network device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the method as described in any one of claims 75 to 95.
102. A base station, characterized in that: Having a first network node and / or a second network node; The first network node comprises: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first network device performs the method according to any one of claims 38 to 74; The second network node includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the second network device executes the method as described in any one of claims 75 to 95.
103. A chip, characterized in that: It comprises: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 37.
104. A chip, characterized in that: It comprises: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 38 to 74.
105. A chip, characterized in that: It comprises: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 75 to 95.
106. A computer-readable storage medium, characterized in that Used to store a computer program, when the computer program is executed, the method according to any one of claims 1 to 37 is implemented, or the method according to any one of claims 38 to 74 is implemented, or the method according to any one of claims 75 to 95 is implemented.
107. A computer program, characterized in that When the computer program is executed, the method according to any one of claims 1 to 37 is implemented, or the method according to any one of claims 38 to 74 is implemented, or the method according to any one of claims 75 to 95 is implemented.
Citation Information
Patent Citations
Initial access method, device and system under multi-timing groups
CN102892192A
Communication method and communication device
CN110475358A
Radio communication method, terminal device and network device
CN113169848A
Differential control information for multi-beam operation
US20210307049A1
Uplink timing management and uplink power control
WO2013103545A1
Cited By
Terminal, radio communication method, and base station
US20250317983A1
Multiple timing advances in multiple transmit / receive points
WO2026073477A1
