WO2020220356A1 - 一种dmrs配置方法、用户设备 - Google Patents
一种dmrs配置方法、用户设备 Download PDFInfo
- Publication number
- WO2020220356A1 WO2020220356A1 PCT/CN2019/085383 CN2019085383W WO2020220356A1 WO 2020220356 A1 WO2020220356 A1 WO 2020220356A1 CN 2019085383 W CN2019085383 W CN 2019085383W WO 2020220356 A1 WO2020220356 A1 WO 2020220356A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pusch
- dmrs
- time domain
- correspondence
- configuration information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
- H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L25/00—Baseband systems
- H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
- H04L25/0202—Channel estimation
- H04L25/0224—Channel estimation using sounding signals
- H04L25/0226—Channel estimation using sounding signals sounding signals per se
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2602—Signal structure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2602—Signal structure
- H04L27/261—Details of reference signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0078—Timing of allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0092—Indication of how the channel is divided
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0014—Three-dimensional division
- H04L5/0023—Time-frequency-space
Definitions
- the present invention relates to the field of information processing technology, in particular to a DMRS configuration method, UE, chip, computer readable storage medium, computer program product and computer program.
- NR Rel16 enhances PUSCH repetition and relaxes some restrictions. That is, there can be one or more PUSCHs in each time slot, and the time domain resources where PUSCHs are located can be different, as shown in Figure 1a and Figure 1b.
- Figure 1a contains the case where PUSCH cross-slots
- Figure 1b contains the case where multiple PUSCHs are included in one time slot. Since there are no more restrictions on application scenarios, data can be dispatched in real time, thereby reducing data transmission delay.
- DMRS is configured for the initial PUSCH.
- the length of the PUSCH will change, as shown in Figures 1a and 1b. How to configure additional DMRS for the split PUSCH needs to be resolved.
- embodiments of the present invention provide a DMRS configuration method, UE, chip, computer-readable storage medium, computer program product, and computer program.
- a DMRS configuration method is provided, which is applied to user equipment UE, including:
- the first PUSCH is obtained by splitting the second PUSCH.
- a DMRS configuration method wherein the method includes:
- the time domain positions of the M DMRS are respectively determined; M is an integer greater than or equal to 2.
- a UE including:
- the first processing unit determines the time domain position of the first DMRS according to the first PUSCH time domain length and DMRS configuration information
- the first PUSCH is obtained by splitting the second PUSCH.
- a UE including:
- the DMRS can be configured according to the number of first PUSCH symbols after splitting, so that the reconfigured first DMRS can match the first PUSCH after splitting, ensuring its tracking of the channel in the time domain, and improving the channel Estimate performance.
- Figures 1a-1b are schematic diagrams of the scene architecture
- FIG. 1c is a schematic diagram 1 of a communication system architecture provided by an embodiment of the present application.
- Figure 1d is a schematic diagram of DMRS configuration
- FIG. 2 is a first schematic diagram of a method flow provided by an embodiment of the present invention.
- Figure 3-11 is a schematic diagram of various feedback for downlink transmission
- FIG. 12 is a schematic diagram 2 of a method flow according to an embodiment of the present invention.
- 13 and 14 are schematic diagrams of the structure of UE provided by an embodiment of the present invention.
- GSM Global System of Mobile Communication
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GSM Global System of Mobile Communication
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- FDD Frequency Division Duplex
- TDD Time Division Duplex
- UMTS Universal Mobile Telecommunication System
- WiMAX Worldwide Interoperability for Microwave Access
- the communication system 100 applied in the embodiment of the present application may be as shown in FIG. 1c.
- the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a UE 120 (or called a communication terminal or a terminal).
- the network device 110 may provide communication coverage for a specific geographic area, and may communicate with UEs located in the coverage area.
- the network equipment 110 may be a network equipment (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network equipment (NodeB, NB) in a WCDMA system, or an evolution in an LTE system Type network equipment (Evolutional Node B, eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment may be a mobile switching center, a relay station, an access point, In-vehicle devices, wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
- BTS Base Transceiver Station
- NodeB, NB network equipment
- LTE system Type network equipment Evolutional Node B, eNB or eNodeB
- CRAN Cloud Radio Access Network
- the network equipment may be a mobile switching center, a relay station, an access point, In-vehicle devices, wearable
- the communication system 100 also includes at least one UE 120 located within the coverage area of the network device 110.
- UE as used herein includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another UE's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
- a UE set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a "mobile terminal”.
- direct terminal connection (Device to Device, D2D) communication may be performed between UEs 120.
- the embodiment of the present invention provides a DMRS configuration method, which is applied to a user equipment (UE) as shown in FIG. 2 and includes:
- Step 21 Determine the time domain position of the first DMRS according to the first PUSCH time domain length and DMRS configuration information
- the first PUSCH is obtained by splitting the second PUSCH.
- the DMRS configuration information includes at least one: pilot start position and pilot increase position.
- the DMRS consists of two parts.
- the figure 1 indicates the front-load DMRS and the figure 2 indicates the additional DMRS.
- the position of the pre-pilot is fixed. High-level signaling configuration or the start symbol of the data sharing channel (when the time domain resource indication mode is Type B).
- the position of the additional pilot is determined by the time domain length (number of symbols) of high-level signaling and data.
- the solution provided in this embodiment may further include: determining the second DMRS time domain position according to the second PUSCH time domain length and DMRS configuration information;
- the time domain position of the second DMRS may be determined in advance based on the second PUSCH and DMRS configuration information
- the time domain position of the first DMRS corresponding to the first PUSCH can be determined again according to the time domain length of the first PUSCH and the configuration information of the DMRS.
- the second DMRS time domain position can be truncated based on the first PUSCH time domain length.
- the time domain positions of the first DMRS and the second DMRS may be the same or different, and the first DMRS may be truncated from the second DMRS.
- the time domain position of the first DMRS is determined according to the first PUSCH time domain length and DMRS configuration information, and the second correspondence; where the second correspondence is the PUSCH time domain length, the DMRS configuration information and the DMRS time domain Correspondence of location. That is to say, there is also a situation where the time domain position of the first DMRS is re-determined, instead of being truncated by the second DMRS.
- the time domain lengths of different first PUSCHs may also be the same or different.
- the time domain position of the additional pilot (additional DMRS) in the DMRS can be updated according to the time domain length of the first PUSCH after splitting, or the additional DMRS can be truncated. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves channel estimation signaling.
- the UE receives the DMRS parameters configured on the network side; then the network side sends downlink control information (DCI) to the UE, and the DCI is used to schedule PUSCH repeated transmission; the UE sends to the network side
- DCI downlink control information
- the PUSCH is repeated with the corresponding DMRS, that is, the first DMRS corresponding to the first PUSCH is sent to the network side.
- the first PUSCH is obtained by splitting the second PUSCH at the slot boundary. Moreover, according to the PUSCH time domain length after splitting, the existing protocol is queried to determine the DMRS time domain position. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves the channel estimation performance.
- Step 1 Configure DMRS parameters on the network side, where the DMRS parameters include dmrs-AdditionalPosition for indicating the number of additional pilot groups.
- dmrs-AdditionalPosition pos1.
- dmrs-AdditionalPosition are pos0, pos1 and pos3.
- pos2 is used by default.
- pos0,1,2,3 correspond to 0,1,2,3 in Table 1.
- Step 2 The terminal side receives DMRS parameters.
- Step 3 The network side sends downlink control information for scheduling PUSCH repeated transmission.
- the network side sends a UL grant to schedule repeated PUSCH transmission.
- the time domain resource indication method adopts TypeB.
- the number of PUSCH repetitions is 4, the time domain position of the first PUSCH repetition is the 5th to the 12th symbol of the nth slot, and the subsequent PUSCH repetitions are immediately following the previous PUSCH repetition resource in the time domain. Therefore, the time domain resources for 4 PUSCH repetitions can be known, as shown in FIG. 4.
- the 4 second PUSCH repetitions are split into 5 first PUSCH repetitions.
- Step 4 The terminal side receives the downlink control information, and repeatedly transmits the first PUSCH and the corresponding DMRS according to the downlink control information.
- Step 4.1 The terminal side receives the downlink control information, and according to the downlink control information, determines the first PUSCH transmission resource to be repeatedly sent and the corresponding first DMRS time domain position, as shown in FIG. 4.
- the first corresponding relationship is predefined.
- the length of the time domain (8 symbols) look up Table 1 to determine the time domain position of its DMRS as the first and seventh symbols in the PUSCH, as shown in Figure 5.
- the second correspondence is the PUSCH time domain length, the correspondence between the DMRS configuration information and the DMRS time domain position.
- the same first correspondence or second correspondence is adopted; wherein, the PUSCH includes a split first PUSCH and an unsplit second PUSCH.
- the length of the time domain (2 symbols and 6 symbols), check Table 1 to determine the number of columns and time domain position of the DMRS are the first symbol in the PUSCH (PUSCH time domain length is 2 symbols) and the PUSCH
- the first and fifth symbols (when the PUSCH time domain length is 6 symbols) are shown in Figure 5.
- this processing method mainly focuses on the additional DMRS configuration problem caused by the change of PUSCH length, and further enhancement on this basis is not rejected.
- l 0 is the time domain position of the pre-pilot.
- l 0 is configured by high-level signaling, and configured by egdmrs-TypeA-Position.
- l 0 0 means the first symbol, and so on.
- Step 4.2 The terminal repeatedly transmits the PUSCH and the corresponding DMRS based on the repeatedly transmitted PUSCH transmission resource and the corresponding DMRS location determined in step 4.2.
- Step 5 The network side receives the repeatedly sent PUSCH and the corresponding DMRS, and demodulates the PUSCH based on the DMRS detection.
- the first PUSCH is obtained by splitting the second PUSCH at the slot boundary.
- the initially configured second DMRS is truncated according to the length of the first PUSCH time domain after splitting. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves the channel estimation performance.
- Step 1 The network side configures DMRS parameters, where the DMRS parameters include dmrs-AdditionalPosition for indicating the number of columns of additional pilots.
- Step 2 The terminal side receives DMRS parameters.
- Step 3 The network side sends downlink control information for scheduling PUSCH repeated transmission.
- the network side sends a UL grant to schedule repeated PUSCH transmission.
- the time domain resource indication method adopts TypeB.
- the number of PUSCH repetitions is 4, the time domain position of the first PUSCH repetition is the 5th to the 12th symbol of the nth slot, and the subsequent PUSCH repetitions are immediately following the previous PUSCH repetition resource in the time domain. Therefore, it can be seen that the time domain resources of 4 PUSCH repetitions are shown in Fig. 6. Due to the cross-domain slot boundary, the 4 PUSCH repetitions are split into 5 PUSCH repetitions.
- Step 4 The terminal side receives downlink control information, and repeatedly sends PUSCH and corresponding DMRS according to the downlink control information.
- Step 4.1 The terminal side receives the downlink control information, and according to the downlink control information, determines the PUSCH transmission resource to be repeatedly sent and the corresponding DMRS position, as shown in FIG. 8.
- Case 2 Determine the second DMRS time domain position according to the second PUSCH time domain length and DMRS configuration information
- the second DMRS time domain position can be truncated based on the first PUSCH time domain length.
- the determining the time domain position of the second DMRS according to the second PUSCH time domain length and DMRS configuration information further includes: determining the time domain of the second DMRS according to the second PUSCH time domain length and DMRS configuration information, and the first correspondence relationship. Domain location; where the first correspondence is the PUSCH time domain length, and the correspondence between the DMRS configuration information and the DMRS time domain location.
- dmrs-AdditionalPosition pos1 (configuration in step 1) and the time domain length of the current PUSCH (2 symbols and 6 symbols), truncate the additional DMRS other than 2 symbols and 6 symbols, and determine the time domain position of the DMRS to be the first symbol in the PUSCH (when the PUSCH time domain length is 2 symbols) and PUSCH The first symbol within (when the PUSCH time domain length is 6 symbols), as shown in Figure 8.
- the demodulation pilot is not sent accordingly.
- Step 4.2 The terminal repeatedly transmits the PUSCH and the corresponding DMRS based on the repeatedly transmitted PUSCH transmission resource and the corresponding DMRS location determined in step 4.2.
- Step 5 The network side receives the repeatedly sent PUSCH and the corresponding DMRS, and demodulates the PUSCH based on the DMRS detection.
- the method for determining the time domain position of the DMRS is the same as step 4.1.
- the same first correspondence or second correspondence is adopted; wherein, the PUSCH includes a split first PUSCH and an unsplit second PUSCH.
- the first correspondence and/or the second correspondence all use the tables in 3GPP TS 38.211 v15.4.0, as shown in Table 1.
- this embodiment also provides a processing situation in which the first PUSCH is obtained by splitting the second PUSCH based on SFI. specific:
- the first PUSCH after the split is obtained based on the SFI interrupt, if the first PUSCH after the split meets the first condition, at least two PUSCHs after the split share the DMRS.
- the first condition includes:
- the interval between split PUSCHs is less than N symbols, and N is a non-negative integer.
- the SFI interruption means that the time domain position corresponding to an initial PUSCH contains downlink symbols and/or flexible symbols, and the initial PUSCH will be split into multiple segments, as shown in FIG. 9.
- the PUSCH after the SFI interrupt is an independent PUSCH, and the determination of the DMRS time domain position of each PUSCH is the same as the several processing situations described above.
- the DMRS configuration of the initial PUSCH is adopted.
- the DMRS is discarded.
- the PUSCH after the SFI interruption does not meet the first condition, and the first PUSCH after the split is an independent PUSCH, and the DMRS configuration method refers to the several processing situations described above for processing.
- the first condition is that the interval between split PUSCHs is less than N symbols, and N is a non-negative integer, for example, N is 4.
- the DMRS is a dual-symbol DMRS
- the split first PUSCH cannot carry the dual-symbol DMRS
- the dual-symbol DMRS is discarded.
- double-symbol DMRS Double-symbol DMRS
- DMRS Double-symbol DMRS
- the set of double-symbol DMRS is discarded.
- the original PUSCH has a length of 7 symbols. Look up Table 1 to determine that its pilot time domain positions are the first, second, fifth and sixth symbols.
- the PUSCH spans a time slot, it is divided into a 5-symbol PUSCH and a 2-symbol PUSCH.
- the second group of DMRS can only be partially mapped, that is, the DMRS of one symbol is mapped to the fifth symbol, and the DMRS of the other symbol cannot be mapped. Therefore, the second group of DMRS symbols are discarded.
- the technical advantages are: It avoids invalid DMRS mapping and is used to transmit data to improve the reliability of data transmission. For the 2-symbol PUSCH, since the PUSCH resource can only carry DMRS and cannot carry data, it is directly discarded, which can save uplink resources and power. Another method is to carry a 2-symbol DMRS. Its technical advantage is to avoid transmission suspension, resulting in discontinuous transmission phase.
- double-symbol DMRS can also be restricted. This is because double-symbol DMRS is mostly used for multi-antenna port transmission, and PUSCH repetition is mostly used for small data packet (low delay) or coverage-limited transmission, which cannot support multi-antenna port transmission. Restricting double-symbol DMRS can not only reduce the complexity of standards and implementation, but also does not affect the actual use effect.
- a DMRS configuration method is provided, as shown in FIG. 12, including:
- Step 31 According to the length of the M PUSCH time domain and the DMRS configuration information, the time domain positions of the M DMRS are respectively determined; M is an integer greater than or equal to 2.
- the first PUSCH of the M PUSCHs uses the first time domain resource indication method to determine the time domain position of the DMRS.
- the first time domain resource indication mode Type A has a limited time domain start position, and the reference start point of the pilot is the slot boundary.
- the transmission resources and DMRS time domain position of the first PUSCH repetition can adopt the existing technology, but the time domain position of the second or subsequent PUSCH repetition is different from the time domain position of the first PUSCH repetition.
- the DMRS time domain position still refers to the time slot boundary and the time domain position is determined according to the initial configuration, then the DMRS is not in the PUSCH resource.
- each PUSCH repetition needs to include DMRS. Therefore, for Type A, it is necessary to determine the DMRS in the second and subsequent PUSCHs, so the following processing is provided:
- the time domain position of the DMRS in the mth PUSCH of the M PUSCHs is the same time domain position of the DMRS determined by the first time domain resource indication mode in the first PUSCH;
- n is an integer greater than or equal to 2.
- the relative time domain position of the DMRS of the second and subsequent PUSCH repetitions within each PUSCH repetition is the same as the first PUSCH repetition.
- the truncation method is adopted.
- the time domain position of the DMRS in the mth PUSCH of the M PUSCHs is determined by using the second time domain resource indication method
- M is an integer greater than or equal to 2
- m is an integer greater than or equal to 2.
- the DMRS time domain position of the second and subsequent PUSCH repetitions is understood according to the Type B model.
- the DRMS time domain position of the second PUSCH repetition is based on the resource mapping method TypeB, then the first The group DMRS is located at the first symbol of the second PUSCH repetition.
- the time domain position of the second group of DMRS is also determined according to the Type B mode. Specifically, refer to the Type B related column when looking up Table 1.
- Type B resource indication methods can cover all situations of Type A. Therefore, for PUSCH repetition, only Type B resource indication methods can be supported, which neither affects the flexibility of resource scheduling nor does it appear Type
- the DMRS time domain position determination problem corresponding to A reduces the standard complexity.
- the DMRS can be configured according to the number of first PUSCH symbols after splitting, so that the reconfigured first DMRS can match the first PUSCH after splitting, ensuring its tracking of the channel in the time domain, and improving the channel Estimate performance.
- the embodiment of the present invention provides a user equipment (UE) as shown in FIG. 13, including:
- the first processing unit 41 determines the time domain position of the first DMRS according to the first PUSCH time domain length and DMRS configuration information
- the first PUSCH is obtained by splitting the second PUSCH.
- the DMRS configuration information includes at least one: pilot start position and pilot increase position.
- the solution provided in this embodiment may further include: determining the second DMRS time domain position according to the second PUSCH time domain length and DMRS configuration information;
- the time domain position of the second DMRS may be determined in advance based on the second PUSCH and DMRS configuration information
- the time domain position of the first DMRS corresponding to the first PUSCH can be determined again according to the time domain length of the first PUSCH and the configuration information of the DMRS.
- the second DMRS time domain position can be truncated based on the first PUSCH time domain length.
- the time domain positions of the first DMRS and the second DMRS may be the same or different, and the first DMRS may be truncated from the second DMRS.
- the time domain position of the first DMRS is determined according to the first PUSCH time domain length and DMRS configuration information, and the second correspondence; where the second correspondence is the PUSCH time domain length, the DMRS configuration information and the DMRS time domain Correspondence of location. That is to say, there is also a situation where the time domain position of the first DMRS is re-determined, instead of being truncated by the second DMRS.
- the time domain lengths of different first PUSCHs may also be the same or different.
- the time domain position of the additional pilot (additional DMRS) in the DMRS can be updated according to the time domain length of the first PUSCH after splitting, or the additional DMRS can be truncated. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves channel estimation signaling.
- the UE receives the DMRS parameters configured on the network side; then the network side sends downlink control information (DCI) to the UE, and the DCI is used to schedule PUSCH repeated transmission; the UE sends to the network side
- DCI downlink control information
- the PUSCH is repeated with the corresponding DMRS, that is, the first DMRS corresponding to the first PUSCH is sent to the network side.
- the first PUSCH is obtained by splitting the second PUSCH at the slot boundary. Moreover, according to the PUSCH time domain length after splitting, the existing protocol is queried to determine the DMRS time domain position. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves the channel estimation performance.
- the first corresponding relationship is predefined.
- the length of the time domain (8 symbols) look up Table 1 to determine the time domain position of its DMRS as the first and seventh symbols in the PUSCH, as shown in Figure 5.
- the second correspondence is the PUSCH time domain length, the correspondence between the DMRS configuration information and the DMRS time domain position.
- the same first correspondence or second correspondence is adopted; wherein, the PUSCH includes a split first PUSCH and an unsplit second PUSCH.
- this processing method mainly focuses on the additional DMRS configuration problem caused by the change of PUSCH length, and further enhancement on this basis is not rejected.
- the first PUSCH is obtained by splitting the second PUSCH at the slot boundary.
- the initially configured second DMRS is truncated according to the length of the first PUSCH time domain after splitting. This enables the first DMRS to match the split first PUSCH, ensures its tracking of the channel in the time domain, and improves the channel estimation performance.
- Case 2 Determine the second DMRS time domain position according to the second PUSCH time domain length and DMRS configuration information
- the second DMRS time domain position can be truncated based on the first PUSCH time domain length.
- the determining the time domain position of the second DMRS according to the second PUSCH time domain length and DMRS configuration information further includes: determining the time domain of the second DMRS according to the second PUSCH time domain length and DMRS configuration information, and the first correspondence relationship. Domain location; where the first correspondence is the PUSCH time domain length, and the correspondence between the DMRS configuration information and the DMRS time domain location.
- dmrs-AdditionalPosition pos1 (configuration in step 1) and the time domain length of the current PUSCH (2 symbols and 6 symbols), truncate the additional DMRS other than 2 symbols and 6 symbols, and determine the time domain position of the DMRS to be the first symbol in the PUSCH (when the PUSCH time domain length is 2 symbols) and PUSCH The first symbol within (when the PUSCH time domain length is 6 symbols), as shown in Figure 8.
- the demodulation pilot is not sent accordingly.
- this embodiment also provides a processing situation in which the first PUSCH is obtained by splitting the second PUSCH based on SFI. specific:
- the first PUSCH after the split is obtained based on the SFI interrupt, if the first PUSCH after the split meets the first condition, at least two PUSCHs after the split share the DMRS.
- the first condition includes:
- the interval between split PUSCHs is less than N symbols, and N is a non-negative integer.
- the SFI interruption means that the time domain position corresponding to an initial PUSCH contains downlink symbols and/or flexible symbols, and the initial PUSCH will be split into multiple segments, as shown in FIG. 9.
- the PUSCH after the SFI interrupt is an independent PUSCH, and the DMRS time domain position of each PUSCH is determined in the same way as the several processing situations described above.
- the DMRS configuration of the initial PUSCH is adopted.
- a UE is provided, as shown in FIG. 14, including:
- the second processing unit 51 determines the time domain positions of the M DMRSs respectively according to the length of the M PUSCH time domains and the DMRS configuration information; M is an integer greater than or equal to 2.
- the first PUSCH of the M PUSCHs uses the first time domain resource indication method to determine the time domain position of the DMRS.
- the first time domain resource indication mode Type A has a limited time domain start position, and the reference start point of the pilot is the slot boundary.
- the transmission resources and DMRS time domain position of the first PUSCH repetition can adopt the existing technology, but the time domain position of the second or subsequent PUSCH repetition is different from the time domain position of the first PUSCH repetition.
- the time domain position of the DMRS still refers to the slot boundary and the time domain position is determined according to the initial configuration, then the DMRS is not in the PUSCH resource.
- each PUSCH repetition needs to include DMRS. Therefore, for Type A, it is necessary to determine the DMRS in the second and subsequent PUSCHs, so the following processing is provided:
- the time domain position of the DMRS in the mth PUSCH of the M PUSCHs is the same time domain position as the DMRS determined by the first time domain resource indication mode in the first PUSCH;
- n is an integer greater than or equal to 2.
- the truncation method is adopted.
- the second type, the second processing unit 51, the time domain position of the DMRS in the mth PUSCH of the M PUSCHs is determined by using a second time domain resource indication method
- M is an integer greater than or equal to 2
- m is an integer greater than or equal to 2.
- the DMRS can be configured according to the number of first PUSCH symbols after splitting, so that the reconfigured first DMRS can match the first PUSCH after splitting, ensuring its tracking of the channel in the time domain, and improving the channel Estimate performance.
- the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer-readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for the sake of brevity , I won’t repeat it here.
- the embodiments of the present application also provide a computer program product, including computer program instructions.
- the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
- the embodiment of the present application also provides a computer program.
- the computer program can be applied to the network device in the embodiment of the present application.
- the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- I won’t repeat it here.
- the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
- the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
- the disclosed system, device, and method may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
Abstract
Description
Claims (36)
- 一种DMRS配置方法,应用于用户设备UE,包括:根据第一PUSCH时域长度和DMRS配置信息,确定第一DMRS的时域位置;其中,所述第一PUSCH由第二PUSCH分裂得到。
- 根据权利要求1所述的方法,其中,第一PUSCH由第二PUSCH在时隙边界分裂得到。
- 根据权利要求2所述的方法,其中,所述DMRS配置信息,包括至少一个:导频起始位置和导频增加位置。
- 根据权利要求2所述的方法,其中,所述方法还包括:根据第二PUSCH时域长度和DMRS配置信息确定第二DMRS时域位置;其中,所述第二DMRS时域位置,能够基于第一PUSCH时域长度截断。
- 根据权利要求4所述的方法,其中,所述根据第二PUSCH时域长度和DMRS配置信息确定第二DMRS时域位置,还包括:根据第二PUSCH时域长度和DMRS配置信息,以及第一对应关系,确定第二DMRS的时域位置;其中,第一对应关系为PUSCH时域长度,DMRS配置信息和DMRS时域位置的对应关系。
- 根据权利要求5所述的方法,其中,所述第一对应关系是预定义的。
- 根据权利要求1所述的方法,其中,所述根据第一PUSCH时域长度和DMRS配置信息,确定第一DMRS的时域位置,还包括:所述根据第一PUSCH时域长度和DMRS配置信息,以及第二对应关系,确定第一DMRS的时域位置;其中,第二对应关系为PUSCH时域长度,DMRS配置信息和DMRS时域位置的对应关系。
- 根据权利要求7所述的方法,其中,第二对应关系是预定义的。
- 根据权利要求5所述的方法,其中,所述方法还包括:对于PUSCH重复传输,采用同一个第一对应关系或第二对应关系;其中,所述PUSCH包括分裂的第一PUSCH以及未分裂的第二PUSCH。
- 根据权利要求5-9任一项所述的方法,其中,所述第一对应关系和/或所述第二 对应关系都采用3GPP TS 38.211 v15.4.0中的表格。
- 根据权利要求1所述的方法,其中,所述方法还包括:第一PUSCH由第二PUSCH基于SFI分裂得到。
- 根据权利要求11所述的方法,其中,所述方法还包括:当基于SFI中断得到分裂后的第一PUSCH时,若分裂后的第一PUSCH满足第一条件,则分裂后的至少两个PUSCH共享DMRS。
- 根据权利要求12所述的方法,其中,所述第一条件包括:分裂的PUSCH之间的间隔小于N个符号,N为非负整数。
- 根据权利要求1所述的方法,其中,所述DMRS为双符号DMRS时,所述方法还包括:当分裂后的第一PUSCH无法承载双符号DMRS时,放弃所述双符号DMRS。
- 一种DMRS配置方法,其中,所述方法包括:根据M个PUSCH时域长度和DMRS配置信息,分别确定M个DMRS的时域位置;M为大于等于2的整数。
- 根据权利要求15所述的方法,其中,所述方法还包括:M个PUSCH中的第一个PUSCH,采用第一时域资源指示方式确定DMRS的时域位置。
- 根据权利要求15或16所述的方法,其中,所述方法还包括:M个PUSCH中的第m个PUSCH中DMRS的时域位置与第一个PUSCH中第一时域资源指示方式确定的DMRS相同的时域位置;m为大于等于2的整数。
- 根据权利要求15或16所述的方法,其中,所述方法还包括M个PUSCH中的第m个PUSCH中DMRS的时域位置采用第二时域资源指示方式确定;M为大于等于2的整数,m为大于等于2的整数。
- 一种UE,包括:第一处理单元,根据第一PUSCH时域长度和DMRS配置信息,确定第一DMRS的时域位置;其中,所述第一PUSCH由第二PUSCH分裂得到。
- 根据权利要求19所述的UE,其中,第一PUSCH由第二PUSCH在时隙边界 分裂得到。
- 根据权利要求20所述的UE,其中,所述DMRS配置信息,包括至少一个:导频起始位置和导频增加位置。
- 根据权利要求19所述的UE,其中,所述第一处理单元,根据第二PUSCH时域长度和DMRS配置信息确定第二DMRS时域位置;其中,所述第二DMRS时域位置,能够基于第一PUSCH时域长度截断。
- 根据权利要求22所述的UE,其中,所述第一处理单元,根据第二PUSCH时域长度和DMRS配置信息,以及第一对应关系,确定第二DMRS的时域位置;其中,第一对应关系为PUSCH时域长度,DMRS配置信息和DMRS时域位置的对应关系。
- 根据权利要求23所述的UE,其中,所述第一对应关系是预定义的。
- 根据权利要求19所述的UE,其中,所述第一处理单元,根据第一PUSCH时域长度和DMRS配置信息,以及第二对应关系,确定第一DMRS的时域位置;其中,第二对应关系为PUSCH时域长度,DMRS配置信息和DMRS时域位置的对应关系。
- 根据权利要求25所述的UE,其中,第二对应关系是预定义的。
- 根据权利要求24所述的UE,其中,所述第一处理单元,对于PUSCH重复传输,采用同一个第一对应关系或第二对应关系;其中,所述PUSCH包括分裂的第一PUSCH以及未分裂的第二PUSCH。
- 根据权利要求23-27任一项所述的UE,其中,所述第一对应关系和/或所述第二对应关系都采用3GPP TS 38.211 v15.4.0中的表格。
- 根据权利要求19所述的UE,其中,所述第一处理单元,第一PUSCH由第二PUSCH基于SFI分裂得到。
- 根据权利要求29所述的UE,其中,所述第一处理单元,当基于SFI中断得到分裂后的第一PUSCH时,若分裂后的第一PUSCH满足第一条件,则分裂后的至少两个PUSCH共享DMRS。
- 根据权利要求30所述的UE,其中,所述第一条件包括:分裂的PUSCH之间的间隔小于N个符号,N为非负整数。
- 根据权利要求19所述的UE,其中,所述DMRS为双符号DMRS时,所述方法还包括:当分裂后的第一PUSCH无法承载双符号DMRS时,放弃所述双符号DMRS。
- 一种UE,包括:第二处理单元,PUSCH时域长度和DMRS配置信息,分别确定M个DMRS的时域位置;M为大于等于2的整数。
- 根据权利要求33所述的UE,其中,所述第二处理单元,M个PUSCH中的第一个PUSCH,采用第一时域资源指示方式确定DMRS的时域位置。
- 根据权利要求33或34所述的UE,其中,所述第二处理单元,M个PUSCH中的第m个PUSCH中DMRS的时域位置与第一个PUSCH中第一时域资源指示方式确定的DMRS相同的时域位置;m为大于等于2的整数。
- 根据权利要求33或34所述的UE,其中,所述第二处理单元,M个PUSCH中的第m个PUSCH中DMRS的时域位置采用第二时域资源指示方式确定;M为大于等于2的整数,m为大于等于2的整数。
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2019/085383 WO2020220356A1 (zh) | 2019-04-30 | 2019-04-30 | 一种dmrs配置方法、用户设备 |
EP19927183.4A EP3952177B1 (en) | 2019-04-30 | 2019-04-30 | Dmrs configuration method, user equipment and network device |
KR1020217038892A KR20220003049A (ko) | 2019-04-30 | 2019-04-30 | Dmrs 구성 방법, 사용자 장치 |
JP2021564678A JP7302017B2 (ja) | 2019-04-30 | 2019-04-30 | Dmrs設定方法、ユーザー装置及びネットワーク装置 |
CN201980089447.1A CN113383507A (zh) | 2019-04-30 | 2019-04-30 | 一种dmrs配置方法、用户设备 |
CN202111218460.8A CN113938263B (zh) | 2019-04-30 | 2019-04-30 | 一种dmrs配置方法、用户设备以及网络设备 |
US17/452,437 US20220045814A1 (en) | 2019-04-30 | 2021-10-27 | Dmrs configuration method and user equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2019/085383 WO2020220356A1 (zh) | 2019-04-30 | 2019-04-30 | 一种dmrs配置方法、用户设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/452,437 Continuation US20220045814A1 (en) | 2019-04-30 | 2021-10-27 | Dmrs configuration method and user equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020220356A1 true WO2020220356A1 (zh) | 2020-11-05 |
Family
ID=73029657
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/085383 WO2020220356A1 (zh) | 2019-04-30 | 2019-04-30 | 一种dmrs配置方法、用户设备 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20220045814A1 (zh) |
EP (1) | EP3952177B1 (zh) |
JP (1) | JP7302017B2 (zh) |
KR (1) | KR20220003049A (zh) |
CN (2) | CN113383507A (zh) |
WO (1) | WO2020220356A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017107212A1 (en) * | 2015-12-25 | 2017-06-29 | Intel IP Corporation | System and method for pusch resource mapping in fd-mimo system |
CN107547455A (zh) * | 2016-06-29 | 2018-01-05 | 华为技术有限公司 | 一种子帧配置方法及相关设备 |
CN109274472A (zh) * | 2017-07-17 | 2019-01-25 | 华为技术有限公司 | 数据传输方法、网络设备和终端设备 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019033304A (ja) * | 2015-12-25 | 2019-02-28 | シャープ株式会社 | 基地局装置、端末装置および通信方法 |
CN107889266B (zh) * | 2016-09-30 | 2022-09-27 | 中兴通讯股份有限公司 | 物理下行共享信道pusch的传输方法及装置 |
KR101948901B1 (ko) * | 2017-05-18 | 2019-02-15 | 엘지전자 주식회사 | 무선 통신 시스템에서 상향링크 전송을 수행하는 방법 및 이를 위한 장치 |
US11212053B2 (en) * | 2017-08-11 | 2021-12-28 | Qualcomm Incorporated | Methods and apparatus related to demodulation reference signal design and related signaling |
CN111344983B (zh) * | 2017-11-13 | 2022-06-07 | Lg电子株式会社 | 在无线通信系统中发送和接收数据的方法及其装置 |
CN110035527B (zh) * | 2018-01-12 | 2023-11-10 | 华为技术有限公司 | 资源指示方法、终端设备和网络设备 |
US20210377937A1 (en) * | 2018-04-05 | 2021-12-02 | Ntt Docomo, Inc. | Transmission apparatus and reception apparatus |
CN113938264A (zh) * | 2018-05-10 | 2022-01-14 | 北京三星通信技术研究有限公司 | 一种用于发送信号的方法与设备 |
CN110474754A (zh) * | 2018-05-10 | 2019-11-19 | 北京三星通信技术研究有限公司 | 一种用于发送信号的方法与设备 |
US11791951B2 (en) * | 2018-08-09 | 2023-10-17 | Huawei Technologies Co., Ltd. | Mini-slot based repetition and frequency hopping |
EP3609104A1 (en) * | 2018-08-09 | 2020-02-12 | Panasonic Intellectual Property Corporation of America | Flexible repetition of pusch mini-slots within a slot |
WO2020047851A1 (en) * | 2018-09-07 | 2020-03-12 | Lenovo (Beijing) Limited | Method and apparatus for flexible transmission on unlicensed spectrum |
US20220132533A1 (en) * | 2019-02-13 | 2022-04-28 | Idac Holdings, Inc. | Physical uplink shared channel transmissions |
JP7447029B2 (ja) * | 2019-02-14 | 2024-03-11 | 株式会社Nttドコモ | 端末、無線通信方法及びシステム |
MX2021009775A (es) * | 2019-02-14 | 2021-09-08 | Ntt Docomo Inc | Terminal de usuario. |
EP3927047A4 (en) * | 2019-02-14 | 2022-11-30 | Ntt Docomo, Inc. | USER DEVICE |
CN111277361B (zh) * | 2019-03-28 | 2021-06-18 | 维沃移动通信有限公司 | 传输块大小确定方法和通信设备 |
CN111757487B (zh) * | 2019-03-29 | 2022-04-12 | 华为技术有限公司 | 一种通信方法及设备 |
KR20210095430A (ko) * | 2020-01-23 | 2021-08-02 | 삼성전자주식회사 | 무선통신 시스템에서 상향링크 채널 송신 방법 및 장치 |
CN111919415B (zh) * | 2020-06-28 | 2022-07-29 | 北京小米移动软件有限公司 | 数据传输方法及装置、存储介质 |
-
2019
- 2019-04-30 CN CN201980089447.1A patent/CN113383507A/zh active Pending
- 2019-04-30 EP EP19927183.4A patent/EP3952177B1/en active Active
- 2019-04-30 JP JP2021564678A patent/JP7302017B2/ja active Active
- 2019-04-30 WO PCT/CN2019/085383 patent/WO2020220356A1/zh unknown
- 2019-04-30 KR KR1020217038892A patent/KR20220003049A/ko unknown
- 2019-04-30 CN CN202111218460.8A patent/CN113938263B/zh active Active
-
2021
- 2021-10-27 US US17/452,437 patent/US20220045814A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017107212A1 (en) * | 2015-12-25 | 2017-06-29 | Intel IP Corporation | System and method for pusch resource mapping in fd-mimo system |
CN107547455A (zh) * | 2016-06-29 | 2018-01-05 | 华为技术有限公司 | 一种子帧配置方法及相关设备 |
CN109274472A (zh) * | 2017-07-17 | 2019-01-25 | 华为技术有限公司 | 数据传输方法、网络设备和终端设备 |
Non-Patent Citations (2)
Title |
---|
HUAWEI; HISILICON: "PUSCH Enhancements for URLLC", 3GPP DRAFT; R1-1812223, 16 November 2018 (2018-11-16), Spokane, USA, pages 1 - 6, XP051478379 * |
See also references of EP3952177A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN113938263A (zh) | 2022-01-14 |
CN113938263B (zh) | 2024-03-01 |
EP3952177A1 (en) | 2022-02-09 |
KR20220003049A (ko) | 2022-01-07 |
EP3952177A4 (en) | 2022-04-13 |
JP7302017B2 (ja) | 2023-07-03 |
EP3952177B1 (en) | 2023-12-06 |
JP2022532510A (ja) | 2022-07-15 |
CN113383507A (zh) | 2021-09-10 |
US20220045814A1 (en) | 2022-02-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11736250B2 (en) | Method for transmitting reference signal, and communication device | |
CA3043119C (en) | Uplink data transmission method, terminal device, and network device | |
CN107852704A (zh) | 配置信息获取的方法和装置 | |
WO2018000929A1 (zh) | 一种子帧配置方法及相关设备 | |
WO2019080107A1 (zh) | 传输物理上行控制信道pucch的方法、终端设备和网络设备 | |
CN107852703A (zh) | 配置信息获取的方法和装置 | |
US11184895B2 (en) | Information transmission method, network device, and terminal device | |
TWI759558B (zh) | 用於傳輸信號的方法、網路設備和終端設備 | |
TWI741025B (zh) | 信息傳輸方法和裝置 | |
WO2018018633A1 (zh) | 一种csi-rs传输方法及网络设备 | |
WO2020220356A1 (zh) | 一种dmrs配置方法、用户设备 | |
TWI791003B (zh) | 無線通信方法、網絡設備和終端設備 | |
JP7138177B2 (ja) | 電力制御のための方法、端末デバイス及びネットワークデバイス | |
JP7328421B2 (ja) | 電力制御のための方法、端末デバイス及びネットワークデバイス | |
WO2022241742A1 (zh) | 参数配置方法及装置、电子设备及存储介质 | |
WO2019028824A1 (zh) | 用于传输数据的方法、终端设备和网络设备 | |
CN110167065B (zh) | 一种取消上行调度请求的方法、终端设备和网络侧设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19927183 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2021564678 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019927183 Country of ref document: EP Effective date: 20211028 |
|
ENP | Entry into the national phase |
Ref document number: 20217038892 Country of ref document: KR Kind code of ref document: A |