WO2019157685A1 - 一种物理上行共享信道pusch传输方法及装置 - Google Patents

一种物理上行共享信道pusch传输方法及装置 Download PDF

Info

Publication number
WO2019157685A1
WO2019157685A1 PCT/CN2018/076781 CN2018076781W WO2019157685A1 WO 2019157685 A1 WO2019157685 A1 WO 2019157685A1 CN 2018076781 W CN2018076781 W CN 2018076781W WO 2019157685 A1 WO2019157685 A1 WO 2019157685A1
Authority
WO
WIPO (PCT)
Prior art keywords
subframe
time domain
resource unit
mpdcch
location
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/076781
Other languages
English (en)
French (fr)
Inventor
赵越
余政
程型清
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201880089003.3A priority Critical patent/CN111699744B/zh
Priority to EP18906282.1A priority patent/EP3737190A4/en
Priority to PCT/CN2018/076781 priority patent/WO2019157685A1/zh
Publication of WO2019157685A1 publication Critical patent/WO2019157685A1/zh
Priority to US16/990,581 priority patent/US11528697B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0033—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation each allocating device acting autonomously, i.e. without negotiation with other allocating devices
    • 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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • 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/0028—Variable division
    • 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—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • 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/0053—Allocation of signalling, i.e. of overhead other than pilot 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/0078—Timing of allocation
    • H04L5/0087—Timing of allocation when data requirements change
    • 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—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • 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/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • 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
    • 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/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a physical uplink shared channel PUSCH transmission method and apparatus.
  • the physical uplink shared channel (PUSCH) resource scheduling granularity of the machine type communication (MTC) system is a resource block (resource block). (RB), the number of subcarriers occupied by the PUSCH is large, and the transmission power of the terminal on each carrier is small.
  • PUSCH physical uplink shared channel
  • MTC machine type communication
  • the narrow physical uplink shared channel (NPUSCH) is defined. Similar to the resource scheduling granularity, the time domain of the first subframe in the uplink subframe corresponding to the defined resource unit may be the first one of the uplink subframes corresponding to the physical uplink shared channel (PUSCH). The time domain positions of the subframes are different, so that the uplink data occupies less subframe transmission, which not only causes poor data transmission quality, but also causes waste of resources.
  • the defined RU occupies 2 subframes in the time domain, it occupies 6 subcarriers in the frequency domain, and bears the last sub-device of the physical downlink control channel (MPDCCH).
  • the frame is the subframe 4, and the PUSCH corresponding to the MPDCCH is transmitted on the subframe 8.
  • the PUSCH corresponding to the MPDCCH can only occupy the subframe 8 transmission, as shown in FIG.
  • the present application provides a PUSCH transmission method to solve a first subframe time domain position occupied by a start subframe of a PUSCH and a resource unit in a time domain when a resource allocation granularity of a PUSCH in a TDD mode is a resource unit. Different, the quality of the uplink data transmission is not high and the resources are wasted.
  • the method includes: receiving, by the terminal, an MPDCCH sent by the PUSCH scheduling device, determining a time domain location of the first subframe according to the repeated transmission times of the MPDCCH included in the MPDCCH, and according to the timing indication information included in the MPDCCH, and the The time domain position of the one subframe is determined, and the time domain location of the second subframe is determined, and the PUSCH corresponding to the MPDCCH is sent in the second subframe according to the time domain location of the second subframe.
  • the first subframe is a last subframe that carries the MPDCCH
  • the second subframe is a starting subframe that carries a PUSCH corresponding to the MPDCCH
  • a resource allocation granularity of a PUSCH corresponding to the MPDCCH is a target resource unit, where the number of subcarriers occupied by the target resource unit in the frequency domain is less than or equal to 12.
  • the MPDCCH of the first subframe is determined according to the number of repeated transmissions of the MPDCCH, according to the time domain location of the first subframe, and the MPDCCH, which includes the MPDCCH repeated transmission times and the timing indication information.
  • the timing indication information determines a time domain location of the second subframe, so that a time domain location of the starting subframe of the PUSCH corresponding to the MPDCCH is the same as a time domain location of the first subframe occupied by the target RU in the time domain.
  • the terminal is configured to use the subframe occupied by the target RU to transmit the PUSCH corresponding to the MPDCCH, to ensure the transmission quality of data carried on the PUSCH corresponding to the MPDCCH, where the first subframe
  • the second subframe is the starting subframe of the PUSCH corresponding to the MPDCCH
  • the resource allocation granularity of the PUSCH corresponding to the MPDCCH is the target RU
  • the target RU is in the frequency.
  • the number of subcarriers occupied on the domain is less than or equal to 12.
  • the terminal determining, by the terminal, the time domain location of the second subframe according to the time domain location of the first subframe and the timing indication information, so that the time domain location of the starting subframe of the PUSCH corresponding to the MPDCCH is
  • the time domain of the first subframe occupied by the target RU in the time domain is the same, and the time domain location of the subframe carrying the MPDCCH does not need to be restricted, so that the MPDCCH sent by the PUSCH scheduling device has greater flexibility.
  • the PUSCH scheduling device is a network side device or a terminal.
  • the network side device sends an MPDCCH including the number of repeated transmissions of the MPDCCH, and the high layer signaling including the timing indication information, where the terminal receives the high layer signaling, Obtaining the timing indication information in the high-level signaling; the terminal determining a time domain location of the first subframe according to the repeated transmission times of the MPDCCH, according to the timing indication information and the first subframe The time domain location determines a time domain location of the second subframe, and the PUSCH corresponding to the MPDCCH is sent in the second subframe.
  • the terminal when the timing indication information includes the first location offset information, the terminal is configured according to the time domain location of the first subframe, the first location offset information, and the third subframe.
  • the time domain location of the frame determines the time domain location of the second subframe.
  • the first location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the third subframe; and the third subframe is a resource allocation granularity of the PUSCH.
  • the starting subframe of the transmitted PUSCH is determined according to the time domain position of the first subframe.
  • the PUSCH scheduling device determines the number according to the number of repeated transmissions of the MPDDCH before sending the MPDCCH. a time domain position of a subframe; determining a time domain location of the first subframe according to a time domain location of the first subframe, determining a time domain location of the third subframe; The first location offset information is determined by a time domain location of the frame and a time domain location of the third subframe.
  • the terminal determines, according to the time domain location of the first subframe and the second location offset. a time domain location of the second subframe, wherein the second location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the first subframe.
  • the PUSCH scheduling device determines the number of repeated transmissions of the MPDDCH before sending the MPDCCH. a time domain location of the frame; determining the second location offset information according to a time domain location of the first subframe and a time domain location of the second subframe.
  • the timing indication information may be used to indicate that the terminal determines the second subframe according to the first mapping relationship.
  • Time domain location The terminal determines a time domain location of the second subframe according to the time domain location of the first subframe and the first mapping relationship.
  • the first mapping relationship is a correspondence between a time domain position of the first subframe and a position offset when the resource allocation granularity of the PUSCH is RU, and the location offset is a time domain of the second subframe.
  • the position is offset relative to the time domain position of the first subframe.
  • the target resource unit includes one uplink subframe or a plurality of consecutive uplink subframes in the time domain, so that the subframes that transmit the PUSCH corresponding to the MPDCCH are consecutive in the time domain, and further The accuracy of the channel estimation when the resource allocation granularity of the PUSCH in the TDD mode is the resource unit can be improved.
  • the terminal and the PUSCH scheduling device are configured with a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration mode and a resource unit, where the PUSCH scheduling device is configured to send the MPDCCH. device of;
  • the target resource unit is the terminal and the PUSCH in the second mapping relationship.
  • the target resource unit is selected by the PUSCH scheduling device from the multiple resource units. And notifying a resource unit of the terminal.
  • the second mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit 0 First resource unit and/or second resource unit 1 First resource unit and/or third resource unit 2 First resource unit 3 First resource unit and/or second resource unit 4 First resource unit and/or second resource unit 5 First resource unit 6 First resource unit
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the number M of subframes occupied by the target resource unit in the time domain and the number N of subcarriers occupied by the target resource unit in the frequency domain satisfy
  • the PUSCH is transmitted with the RB (occupying 12 subcarriers in the frequency domain) as the resource allocation granularity, and the number of subframes occupied by the terminal in the time domain and the number of subcarriers occupied in the frequency domain are compared with the prior art.
  • ⁇ a transmits a PUSCH, the number of subcarriers occupied by the PUSCH is small, and thus the transmission power of the terminal on each subcarrier can be increased.
  • the target resource unit may occupy 1 subframe in the time domain and 12 subcarriers in the frequency domain.
  • the target resource unit may occupy 2 subframes in the time domain. 6 subcarriers are occupied on the domain; or the target resource unit may occupy 3 subframes in the time domain and 4 subcarriers in the frequency domain; or the target resource unit may occupy 4 subframes in the time domain. Occupying 3 subcarriers in the frequency domain; or, the target resource unit may occupy 4 subframes in the time domain and occupy 2 subcarriers in the frequency domain; or the target resource unit may occupy 6 subcarriers in the time domain.
  • the frame occupies 2 subcarriers in the frequency domain; or the target resource unit occupies 8 subframes in the time domain and 2 subcarriers in the frequency domain.
  • the terminal may also send an MPDCCH including the MPDCCH repeated transmission times and the timing indication information to other terminals that can communicate with the terminal, and schedule other terminals that can communicate with the terminal to The terminal transmits the PUSCH corresponding to the MPDCCH.
  • the present application further provides another PUSCH transmission method, which is to solve the problem that the resource allocation granularity of the PUSCH in the TDD mode is a resource unit, and the subframe discontinuity included in the resource unit causes a channel estimation performance spread.
  • the method includes: the terminal receives the resource unit type indication information sent by the PUSCH scheduling device, determines the type of the target resource unit RU that carries the PUSCH according to the resource unit type indication information, and sends the PUSCH according to the target RU type.
  • the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain includes one uplink subframe or multiple uplink subframes in the time domain. Less than or equal to 12.
  • the terminal receives the resource unit RU type indication information sent by the PUSCH scheduling device, determines the target RU type according to the resource unit RU type indication information, and sends the PUSCH according to the target RU type, where
  • the RU time domain corresponding to the target RU type includes one uplink subframe or a plurality of uplink subframes in the time domain, and the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain is less than or equal to 12:
  • the terminal is configured to send the PUSCH by using the RU corresponding to the target RU type to be mapped to one uplink subframe of the system frame or multiple uplink subframes in the time domain, and the subframes included in the resource unit are not resolved.
  • the PUSCH scheduling device is other terminal or higher layer signaling capable of communicating with the terminal.
  • the PUSCH scheduling device may send the resource unit type indication information to the terminal by using an MPDCCH.
  • the PUSCH scheduling device may send the resource unit type indication information to the terminal by using MPDCCH or high layer signaling.
  • the terminal may determine the target RU type by using the following two methods:
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner, and the terminal selects the target in the mapping relationship
  • the resource unit type corresponding to the row subframe configuration mode is determined to be the target RU type.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information
  • the resource unit type indicated by the target resource unit type indication information is determined to be the target RU type.
  • mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit type 0 First RU type and/or second RU type 1 First RU type and/or third RU type 2 First RU type 3 First RU type and/or second RU type 4 First capital type and/or second type 5 First RU type 6 First RU type
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the number of subframes M occupied by the RU corresponding to the target RU type in the time domain and the number of subcarriers occupied by the RU corresponding to the target RU type in the frequency domain satisfy
  • the PUSCH is transmitted with the RB (occupying 12 subcarriers in the frequency domain) as the resource allocation granularity, and the number of subframes occupied by the terminal in the time domain and the number of subcarriers occupied in the frequency domain are compared with the prior art.
  • ⁇ a transmits a PUSCH, the number of subcarriers occupied by the PUSCH is small, and thus the transmission power of the terminal on each subcarrier can be increased.
  • the starting subframe of the RU corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the slot.
  • the present application provides a communication device having a function of implementing terminal behavior in an example of the method of the first aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the communication device includes a receiving unit, a processing unit, and a sending unit, and the units may perform corresponding functions in the method examples of the foregoing first aspect.
  • the units may perform corresponding functions in the method examples of the foregoing first aspect. For details, refer to the detailed description in the method example. I will not repeat them here.
  • the structure of the communication device includes a transceiver, a memory, and a processor, and the processor is configured to support the terminal to perform a corresponding function in the foregoing method of the first aspect.
  • the memory is coupled to the processor, which stores program instructions and data necessary for the coordinator.
  • the present application further provides a PUSCH scheduling device, where the PUSCH scheduling device has a function of implementing the behavior of the PUSCH scheduling device in the foregoing method instance.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the PUSCH scheduling device includes a processing unit and a sending unit, and the units may perform corresponding functions in the method examples of the foregoing first aspect. For details, refer to the detailed description in the method example, where Do not repeat them.
  • the structure of the PUSCH scheduling device includes a transceiver, a memory, and a processor, and the processor is configured to support the PUSCH scheduling device to perform a corresponding function in the method example of the foregoing first aspect.
  • the memory is coupled to the processor, which stores program instructions and data necessary for the coordinator.
  • the present application further provides a communication device having a function of implementing terminal behavior in the method embodiment of the second aspect above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the communication device includes a receiving unit, a processing unit, and a sending unit, and the units may perform corresponding functions in the method examples of the foregoing second aspect.
  • the units may perform corresponding functions in the method examples of the foregoing second aspect. For details, refer to the detailed description in the method example. I will not repeat them here.
  • the present application further provides a PUSCH scheduling device, where the PUSCH scheduling device has a function of implementing the behavior of the PUSCH scheduling device in the foregoing method instance of the second aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the PUSCH scheduling device includes a processing unit and a sending unit, and the units may perform corresponding functions in the method examples of the foregoing second aspect.
  • the units may perform corresponding functions in the method examples of the foregoing second aspect. For details, refer to the detailed description in the method example, where Do not repeat them.
  • the structure of the PUSCH scheduling device includes a transceiver, a memory, and a processor, and the processor is configured to support the PUSCH scheduling device to perform a corresponding function in the method example of the second aspect above.
  • the memory is coupled to the processor, which stores program instructions and data necessary for the coordinator.
  • the present application further provides a computer storage medium having a software program stored therein, which can be implemented by any one of the aspects when read and executed by one or more processors. Methods.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the methods described above.
  • 1 is a correspondence between a subframe in which a PUSCH is transmitted and a subframe in a resource unit in the prior art
  • FIG. 2 is a schematic structural diagram of a resource unit in an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart diagram of a PUSCH transmission method according to an embodiment of the present application.
  • FIG. 5 is a corresponding relationship between a subframe in which a PUSCH is transmitted and a subframe in a resource unit in the embodiment of the present application;
  • FIG. 6 is a mapping relationship between a resource unit and a system frame in the embodiment of the present application.
  • FIG. 7 is a schematic flowchart diagram of another PUSCH transmission method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a PUSCH scheduling device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a PUSCH scheduling device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another PUSCH scheduling apparatus according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of another PUSCH scheduling device according to an embodiment of the present application.
  • the embodiment of the present application provides a physical uplink shared channel PUSCH transmission method and apparatus.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • a resource unit is a resource allocation granularity of the PUSCH, and the number of subcarriers occupied by the resource unit in the frequency domain is less than or equal to 12.
  • the resource unit may be defined by the number of subframes (or the number of slots) included in the time domain by the resource unit and the number of subcarriers included in the frequency domain of the resource unit, that is, i subcarriers ⁇ j subframes, i, j are positive integers.
  • the resource unit may include, but is not limited to, the following types of resource units: 6subcarriers ⁇ 2subframes, 4subcarriers ⁇ 3subframes, 3subcarriers ⁇ 4subframes, 12subcarriers ⁇ 1subframes, 2subcarriers ⁇ 6subframes, 2subcarriers ⁇ 4subframes, and 2subcarriers ⁇ 8subframes.
  • 6subcarriers ⁇ 2subframes 6subcarriers ⁇ 2subframes
  • 4subcarriers ⁇ 3subframes 3subcarriers ⁇ 4subframes
  • 12subcarriers ⁇ 1subframes 6subcarriers ⁇ 6subframes
  • 2subcarriers ⁇ 4subframes 2subcarriers ⁇ 8subframes.
  • a and/or B may indicate that A exists separately, and A and B exist simultaneously, and B cases exist alone.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • FIG. 3 shows a possible communication system architecture applicable to the PUSCH transmission method provided by the embodiment of the present application.
  • the communication system 300 includes: a network side device 301 and at least one terminal 302.
  • the network side device 301 is configured to send an MPDCCH to the at least one terminal 302, and the at least one terminal 302 sends the PUSCH corresponding to the MPDCCH by using the MPDCCH, where the resource allocation granularity of the PUSCH corresponding to the MPDCCH is a target.
  • the resource unit type indication information is sent to the at least one terminal 302, so that the at least one terminal 302 according to the
  • the resource unit type indication information determines a target resource unit type, and the PUSCH is sent according to the target resource unit type, where the resource unit corresponding to the target RU type includes one uplink subframe or consecutive uplink subframes in the time domain, And the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain is less than or equal to 12.
  • the terminal 302 can also schedule, by using the MPDCCH, other terminals in the communication system 300 that can communicate with the terminal to send data to the terminal through the PUSCH corresponding to the MPDCCH; or
  • the other terminal capable of communicating with the terminal transmits the resource unit type indication information to enable other terminals capable of communicating with the terminal to determine the target resource unit type according to the resource unit type indication information, and transmit the PUSCH according to the target resource unit type.
  • the communication system 300 can be a cellular mobile communication system.
  • the wireless communication system can be a 3th generation mobile communication (3G) system or a fourth generation mobile communication technology (the 4th).
  • the generation mobile communication, 4G) system also known as the long term evolution (LTE) system, or the wireless communication system may also be a 5G system, also known as a new radio (NR) system.
  • the network side device 301 may be a base station (BS) in a 3G system or an evolved base station (eNB) employed in a 4G system.
  • the network side device 101 may also be a base station (gNB) that adopts a centralized distributed architecture in a 5G system.
  • BS base station
  • eNB evolved base station
  • gNB base station
  • the terminal 302 may also be referred to as a User Equipment (UE), or may be referred to as a Terminal, a Mobile Station (MS), a Mobile Terminal, etc., and the terminal 302 may pass through a Radio Access Network (Radio Access).
  • Network referred to as RAN for short, communicates with one or more core networks.
  • terminal 102 can be a mobile phone (or "cellular" phone), a computer with a mobile terminal, etc., for example, terminal 102 can also be portable, Pocket, handheld, computer built-in or in-vehicle mobile devices that exchange data with the wireless access network.
  • the terminal in the embodiment of the present application may also be a D2D (Device to Device) terminal or an M2M (Machine to Machine) terminal.
  • a PUSCH transmission method provided by an embodiment of the present application is applicable to the communication system 300 shown in FIG. 3.
  • the specific process of the method includes the following steps:
  • the PUSCH scheduling device sends an MPDCCH.
  • the MPDCCH includes the number of repeated transmissions of the MPDCCH and timing indication information, where the first subframe is the last subframe that carries the MPDCCH.
  • the timing indication information is used to indicate information required to determine a time domain location of the second subframe based on a time domain location of the first subframe.
  • the PUSCH scheduling device is a network side device or a terminal.
  • the PUSCH scheduling device carries the repeated transmission times of the MPDCCH and the timing indication information in downlink control information (DCI) in the MPDCCH.
  • DCI downlink control information
  • the terminal receives the MPDCCH, and acquires the repeated transmission times of the MPDCCH and the timing indication information. It should be noted that when the PUSCH scheduling device is a terminal, the terminal that receives the MPDCCH is another terminal that can communicate with the terminal.
  • the time domain position of the first subframe may be represented by a subframe number of the first subframe in a system frame.
  • the system frame of the LTE TDD communication system is composed of two 5ms half frames, each of which contains five subframes of 1 ms length, and one subframe includes two slots.
  • the subframes in the system frame are classified into three types: a downlink subframe, an uplink subframe, and a special subframe.
  • the LTE TDD communication system supports seven uplink-downlink configuration modes as shown in Table 1, where U represents an uplink subframe, D represents a downlink subframe, and S represents a special subframe. For example, if the system frame in which the last subframe of the MPDCCH is located is subframe 5, the time domain position of the first subframe may be represented by subframe 5.
  • S402 The terminal determines a time domain location of the first subframe according to the repeated transmission times of the MPDCCH.
  • the terminal determines the time domain location of the first subframe according to the received first MPDCCH and the repeated transmission times of the MPDCCH.
  • the time domain location of the first subframe is a time domain location of the subframe according to the received MPDCCH by the terminal.
  • the terminal determines a time domain location of the second subframe according to the time domain location of the first subframe and the timing indication information.
  • the second subframe is a starting subframe that carries the PUSCH corresponding to the MPDCCH, and the resource allocation granularity of the PUSCH corresponding to the MPDCCH is a target resource unit, and the subcarrier occupied by the target resource unit in the frequency domain The number is less than or equal to 12.
  • the terminal may determine the time domain location of the second subframe by using, but not limited to, the following three manners:
  • the terminal determines the time domain location of the third subframe according to the time domain location of the first subframe;
  • the location offset information and the time domain location of the third subframe determine a time domain location of the second subframe.
  • the first location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the third subframe; and the third subframe is a resource allocation granularity of the PUSCH.
  • the resource block RB the starting subframe of the transmitted PUSCH determined according to the first subframe.
  • the time domain position of the first subframe and the time domain position of the third subframe are offset from the time domain position of the first subframe, that is, the PUSCH
  • the first subframe is subframe n
  • the third subframe is subframe n+k PUSCH .
  • the uplink and downlink configuration mode agreed by the terminal and the network side device is the configuration mode 0. If the first subframe is the subframe 0, the third subframe is the subframe 4.
  • the terminal allocates a PUSCH according to a time domain location of the first subframe and a resource allocation granularity of a PUSCH to a resource block RB. Timing, determining a time domain location of the third subframe, and determining a time domain location of the second subframe according to the time domain location of the third subframe and the first location offset information.
  • the first position offset information may indicate a first absolute position offset or a first relative position offset, where the first absolute position offset is from the third subframe to a number of all subframes of the second subframe, where the first relative position offset is a number of valid subframes from the third subframe to the second subframe.
  • the effective subframe is a bandwidth reduced low complexity (BL)/cover enhanced (CE) from the third subframe to the second subframe.
  • the PUSCH scheduling device determines, according to the repeated transmission times of the MPDDCH, the first subframe, before transmitting the MPDCCH. a time domain location; determining a time domain location of the third subframe according to a time domain location of the first subframe; and determining a time domain location of the second subframe according to the time domain location of the first subframe And determining, by the time domain location of the third subframe, the first location offset information.
  • the PUSCH scheduling device determines the time domain location of the second subframe according to the number of subframes occupied by the target RU in the time domain and the time domain location of the first subframe.
  • the time domain location of the second subframe is the same as the first subframe time domain location in the target resource unit.
  • the uplink and downlink configuration mode agreed by the terminal and the PUSCH scheduling device is 1, and the first subframe is subframe 4, the PUSCH scheduling device Querying the foregoing table 2 according to the time domain position of the first subframe, determining that the third subframe is the subframe 8, and because the target RU occupies 2 subframes in the time domain, the second subframe is Subframe 2 in the next system frame, such that the time domain position of the second subframe is the same as the first subframe time domain position in the target resource unit, and the first absolute position offset is 4 subframes (the first relative position offset is 1 subframe).
  • the second mode is determined by the terminal, according to the time domain location of the first subframe and the second location offset information, when the timing indication information is used to indicate the second location offset information.
  • a time domain location of the frame wherein the second location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the first subframe.
  • the second position offset information may indicate a second absolute position offset or a second relative position offset, where the second absolute position offset is from the first subframe to a number of all subframes of the second subframe, where the second relative position offset is a number of valid subframes from the first subframe to the second subframe, where the valid subframe is BL/CE sub.
  • the PUSCH scheduling device when the timing indication information is the second location offset information, the PUSCH scheduling device further determines the first subframe according to the repeated transmission times of the MPDDCH before transmitting the MPDCCH.
  • the uplink and downlink configuration mode agreed by the terminal and the PUSCH scheduling device is 1, and the first subframe is subframe 4, the PUSCH scheduling device Querying the foregoing Table 2 according to the time domain location of the first subframe, the PUSCH can be transmitted on the subframe after the subframe 8 or the subframe 8, because the target RU occupies 2 subframes in the time domain, so it is determined
  • the second subframe is the subframe 2 in the next system frame, so that the time domain location of the second subframe is the same as the first subframe time domain location in the target resource unit.
  • the two absolute position offsets are 8 subframes (the first relative position offset is 3 subframes).
  • the timing indication information may be used to indicate that the terminal determines the second subframe according to the first mapping relationship.
  • a domain location where the first mapping relationship is a correspondence between a time domain location of the first subframe and a location offset when the resource allocation granularity of the PUSCH is RU, where the location offset is the second subframe The offset of the domain location relative to the time domain location of the first subframe.
  • Determining, by the terminal, the location offset corresponding to the time domain location of the first subframe according to the time domain location of the first subframe and the first mapping relationship, according to the time domain of the first subframe The location offset corresponding to the location and the time domain location of the first subframe determine a time domain location of the second subframe.
  • the first mapping relationship is pre-configured in the terminal and the PUSCH scheduling device. And the time domain position of the first subframe in the first mapping relationship, the time domain position of the first subframe is offset from the position offset corresponding to the time domain position of the first subframe, and The time domain location of the first subframe in the target RU is the same.
  • the first mapping relationship is as shown in Table 3, where the time domain location of the first subframe is shown.
  • the second position offset is the second absolute position offset.
  • the target resource unit includes one uplink subframe in the time domain, or includes multiple uplink subframes in the time domain, that is, a subframe that carries the PUSCH corresponding to the MPDCCH. Continuous in the time domain.
  • the target resource unit structure is as shown in FIG. 2, for the uplink and downlink configuration mode 1, the target resource unit is mapped to the system frame as shown in FIG. 6.
  • the terminal and the PUSCH scheduling device are configured with a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration mode and a resource unit, where the terminal is in the second mapping relationship
  • the target resource unit is a resource unit corresponding to the uplink and downlink configuration mode of the PUSCH scheduling agreement in the second mapping relationship.
  • the second mapping relationship is as shown in Table 4:
  • the target resource unit is selected by the PUSCH scheduling device from the multiple resource units. And notifying a resource unit of the terminal.
  • the second mapping relationship is as shown in Table 5:
  • the target resource unit may be notified to the terminal by using the MPDCCH or higher layer signaling.
  • the second mapping relationship satisfies the following table:
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the uplink and downlink configuration mode of the second mapping relationship when the resource unit corresponding to the uplink and downlink configuration mode is mapped to the system frame corresponding to the uplink and downlink configuration mode, the uplink and downlink configuration mode corresponds to all the system frames.
  • the uplink subframes are included in one or more resource units corresponding to the uplink and downlink configuration mode, and the subframes included in each resource unit corresponding to the uplink and downlink configuration mode are continuous, for example, the resource unit and system shown in FIG.
  • the mapping relationship between the frames enables the terminal to effectively utilize the uplink subframe in the uplink and downlink configuration mode agreed with the PUSCH scheduling device, and allocates the PUSCH by using the resource unit as the resource allocation granularity.
  • the number of subframes occupied by the target resource unit in the time domain and the target resource unit are in the frequency.
  • the PUSCH is transmitted with the RB (occupying 12 subcarriers in the frequency domain) as the resource allocation granularity, and the number of subframes occupied by the terminal in the time domain and the number of subcarriers occupied in the frequency domain are compared with the prior art.
  • ⁇ a transmits a PUSCH, the number of subcarriers occupied by the PUSCH is small, and thus the transmission power of the terminal on each subcarrier can be increased.
  • S404 The terminal sends the PUSCH corresponding to the MPDCCH in the second subframe according to the time domain location of the second subframe.
  • the PUSCH scheduling device is configured according to the time domain location of the first subframe and the target The number of subframes occupied by the resource unit in the time domain, determining the first location offset information to determine the time domain location of the second subframe, and receiving the PUSCH corresponding to the MPDCCH in the second subframe.
  • the PUSCH scheduling device is configured according to the time domain location of the first subframe and the first Determining, by a mapping relationship, a position offset corresponding to a time domain position of the first subframe, a position offset corresponding to a time domain position of the first subframe, and a time domain position of the first subframe Determining a time domain location of the second subframe, and receiving, on the second subframe, a PUSCH corresponding to the MPDCCH.
  • the network side device when the PUSCH scheduling device is a network side device, the network side device sends an MPDCCH including a repeated number of transmissions of the MPDCCH, and a high layer signaling including the timing indication information, where the terminal receives the Determining, by the high layer signaling, the timing indication information from the high layer signaling; the terminal determining a time domain location of the first subframe according to the repeated transmission times of the MPDCCH, according to the timing indication information and The time domain position of the first subframe determines a time domain location of the second subframe, and the PUSCH corresponding to the MPDCCH is sent in the second subframe.
  • the embodiment of the present application does not send the MPDCCH including the repeated transmission times of the MPDCCH and the high layer signaling including the timing indication information to the network side device.
  • the order is limited.
  • the network side device may first send an MPDCCH that includes the number of repeated transmissions of the MPDCCH, and then send the high layer signaling that includes the timing indication information, or send the high layer signaling that includes the timing indication information to send the timing.
  • the high-level signaling indicating the information may also simultaneously transmit an MPDCCH including the number of repeated transmissions of the MPDCCH and high-level signaling including the timing indication information.
  • the terminal may also send an MPDCCH including the MPDCCH repeated transmission times and the timing indication information to other terminals that can communicate with the terminal, so that other terminals that can communicate with the terminal pass the foregoing step S302- S304: Send the PUSCH corresponding to the MPDCCH to the terminal.
  • the terminal receives the MPDCCH including the MPDCCH repeated transmission times and the timing indication information, and determines the time domain location of the first subframe according to the repeated transmission times of the MPDCCH, according to the time domain of the first subframe.
  • the location and the timing indication information determine a time domain location of the second subframe, such that a time domain location of the starting subframe carrying the PUSCH corresponding to the MPDCCH and a time domain of the first subframe occupied by the target RU in the time domain The same location, so that the terminal can fully utilize the subframe occupied by the target RU to transmit the PUSCH corresponding to the MPDCCH, so that the transmission quality of data carried on the PUSCH corresponding to the MPDCCH can be guaranteed.
  • a subframe is a last subframe that carries the MPDCCH
  • the second subframe is a start subframe of a PUSCH corresponding to the MPDCCH
  • a resource allocation granularity of a PUSCH corresponding to the MPDCCH is a target RU, and the target The number of subcarriers occupied by the RU in the frequency domain is less than or equal to 12.
  • the terminal determining, by the terminal, the time domain location of the second subframe according to the time domain location of the first subframe and the timing indication information, so that the time domain location of the starting subframe of the PUSCH corresponding to the MPDCCH is
  • the time domain of the first subframe occupied by the target RU in the time domain is the same, and the time domain location of the subframe carrying the MPDCCH does not need to be restricted, so that the MPDCCH sent by the PUSCH scheduling device has greater flexibility.
  • the embodiment of the present application further provides another PUSCH transmission method, which is applicable to the communication system 300 shown in FIG. 3.
  • the method mainly includes the following steps:
  • the PUSCH scheduling device sends the resource unit RU type indication information to the terminal.
  • the PUSCH scheduling device is a network side device or a terminal.
  • the PUSCH scheduling device may send the RU type indication information by using an MPDCCH, or send the RU type indication information by using a high layer signaling.
  • the PUSCH scheduling device may send the message through the MPDCCH.
  • different resource unit types may be represented by the number of subframes occupied by the resource unit in the time domain (or the number of slots occupied in the time domain) and the number of subcarriers occupied by the resource unit in the frequency domain. .
  • the terminal receives the resource unit RU type indication information.
  • the terminal that receives the RU type indication information is another terminal that can communicate with the terminal.
  • the terminal determines, according to the RU type indication information, a type of the target resource unit RU that carries the physical uplink shared channel PUSCH.
  • the resource unit corresponding to the target RU type includes one uplink subframe or a plurality of consecutive uplink subframes in the time domain, and the subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain The number is less than or equal to 12.
  • the terminal may determine the target RU type by using the following two methods:
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner, and the terminal selects the target in the mapping relationship
  • the resource unit type corresponding to the row subframe configuration mode is determined to be the target RU type.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information
  • the resource unit type indicated by the target resource unit type indication information is determined to be the target RU type.
  • the target resource unit type indication information may be an identifier of the target resource unit type.
  • the mapping relationship includes k types of resource unit types, and the numbers of the k resource unit types are 1, 2, ..., respectively, and the target resource unit type indication information may be a number corresponding to the target resource unit type.
  • the target uplink-downlink subframe configuration mode corresponds to two resource unit types
  • the first resource element type corresponding to the target uplink-downlink subframe configuration mode may be represented by “0”
  • “ 1′′ indicates a second resource unit type corresponding to the target uplink and downlink subframe configuration mode, where the target resource unit type indication information is “0” or “1”.
  • mapping relationship between the uplink and downlink subframe configuration mode and the resource unit type satisfies the following table:
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the uplink and downlink configuration mode corresponds to the system frame. All the uplink subframes are included in one or more resource units corresponding to the uplink and downlink configuration mode, and the subframes included in each resource unit corresponding to the uplink and downlink configuration mode are continuous, for example, the resource unit shown in FIG.
  • the mapping relationship with the system frame enables the terminal to effectively utilize the uplink subframe in the uplink and downlink configuration mode agreed with the PUSCH scheduling device, and allocates the PUSCH by using the resource unit as the resource allocation granularity.
  • the number of subframes occupied by the RU corresponding to the target RU type in the time domain and the target RU satisfies
  • the PUSCH is transmitted with a granularity of resource allocation in the RB (occupying 12 subcarriers in the frequency domain), and the terminal uses the number of subframes M occupied in the time domain and the subcarriers occupied in the frequency domain.
  • ⁇ a transmits a PUSCH
  • the number of subcarriers occupied by the PUSCH is small, and thus the transmission power of the terminal on each subcarrier can be increased.
  • S703 The terminal sends the PUSCH according to the target RU type.
  • the starting subframe of the resource unit corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the time slot, so that the resource unit corresponding to the target RU type can be
  • the mapping is performed to consecutive subframes in the time domain, so that the terminal can transmit the PUSCH on consecutive subframes in the time domain, so that the channel estimation accuracy can be ensured.
  • the terminal receives the resource unit RU type indication information, determines the target RU type according to the resource unit RU type indication information, and sends the PUSCH according to the target RU type, where the target RU type corresponds to the RU
  • the time domain includes one uplink subframe or a plurality of consecutive uplink subframes in the time domain, and the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain is less than or equal to 12, so that the terminal passes
  • the RU corresponding to the target RU type is mapped to one uplink subframe of the system frame or multiple uplink subframes in the time domain, and the PUSCH is sent, and the channel estimation result caused by the discontinuity of the subframe included in the resource unit is not solved. The exact problem.
  • the embodiment of the present application provides a communication device, which is used to implement a PUSCH transmission method as shown in FIG. 4, as shown in FIG. 8.
  • the communication device 800 includes a receiving unit 801, a processing unit 802, and a transmitting unit 803.
  • the receiving unit 801 is configured to receive a physical downlink control channel MPDCCH, where the MPDCCH includes the repeated transmission times of the MPDCCH and timing indication information.
  • the processing unit 802 is configured to determine a time domain location of the first subframe according to the repeated transmission times of the MPDCCH, and determine a second subframe according to the timing indication information and a time domain location of the first subframe.
  • a time domain location the first subframe is a last subframe that carries the MPDCCH
  • the second subframe is a start subframe that carries an uplink physical shared channel PUSCH corresponding to the MPDCCH, where the MPDCCH corresponds to
  • the resource allocation granularity of the PUSCH is a target resource unit, and the number of subcarriers occupied by the target resource unit in the frequency domain is less than or equal to 12.
  • the sending unit 803 is configured to send, according to the time domain location of the second subframe, the PUSCH corresponding to the MPDCCH in the second subframe.
  • the timing indication information includes first location offset information, where the first location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the third subframe.
  • the third subframe is a starting subframe of the transmitting PUSCH determined according to a time domain position of the first subframe when a resource allocation granularity of the PUSCH is a resource block RB;
  • the processing unit 802 determines the time domain location of the second subframe according to the timing indication information and the time domain location of the first subframe
  • the processing unit 802 is specifically configured to: according to the time domain location of the first subframe Determining a time domain location of the third subframe; determining a time domain location of the second subframe according to the first location offset information and a time domain location of the third subframe.
  • the timing indication information includes a second location offset information, where the second location offset information indicates a time domain location of the second subframe relative to a time domain of the first subframe. Offset of position;
  • the processing unit 802 determines the time domain location of the second subframe according to the timing indication information and the time domain location of the first subframe, the processing unit 802 is specifically configured to: according to the time domain location of the first subframe And the second position offset information, determining a time domain position of the second subframe.
  • the timing indication information is used to indicate that the terminal determines a time domain location of the second subframe according to the first mapping relationship, where the first mapping relationship is that the resource allocation granularity of the PUSCH is the first subframe when the RU is a correspondence between a time domain position of the frame and a position offset, wherein the position offset is an offset of a time domain position of the second subframe relative to a time domain position of the first subframe;
  • the processing unit 802 determines the time domain location of the second subframe according to the time domain location of the first subframe and the timing indication information
  • the processing unit 802 is specifically configured to: according to the time domain of the first subframe And determining the time domain location of the second subframe by the location and the first mapping relationship.
  • the target resource unit includes one uplink subframe or consecutive uplink subframes in multiple time domains.
  • the sending unit 803 is further configured to send an MPDCCH that includes the MPDCCH repeated transmission times and the timing indication information.
  • the communication device and the PUSCH scheduling device are configured with a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration mode and a resource unit, where the PUSCH scheduling device is a device that sends the MPDCCH. ;
  • the target resource unit is the communication device and the second mapping relationship.
  • the target resource unit is the PUSCH scheduling device from the multiple resource units.
  • the second mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit 0 First resource unit and/or second resource unit 1 First resource unit and/or third resource unit 2 First resource unit 3 First resource unit and/or second resource unit 4 First resource unit and/or second resource unit 5 First resource unit 6 First resource unit
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the number M of subframes occupied by the target resource unit in the time domain and the number N of subcarriers occupied by the target resource unit in the frequency domain satisfy
  • the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • the functional modules in the embodiments 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.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .
  • the embodiment of the present application provides a communication device, which is used to implement a PUSCH transmission method as shown in FIG. 4, and has the function of the communication device 800 as shown in FIG. 8.
  • the communication device 900 includes a transceiver 901 and a processor 902, and the transceiver 901 and the processor 902 are connected to each other.
  • the transceiver 901 is configured to receive a physical downlink control channel MPDCCH, where the MPDCCH includes the repeated transmission times of the MPDCCH and timing indication information.
  • the processor 902 is configured to determine a time domain position of the first subframe for the number of repeated transmissions of the MPDCCH, and determine a time of the second subframe according to the timing indication information and a time domain location of the first subframe. a domain location; and controlling the transceiver 901 to send, according to the time domain location of the second subframe, the PUSCH corresponding to the MPDCCH in the second subframe, where the first subframe is a bearer
  • the last subframe of the MPDCCH, the second subframe is a start subframe that carries the uplink physical shared channel (PUSCH) corresponding to the MPDCCH, and the resource allocation granularity of the PUSCH corresponding to the MPDCCH is a target resource unit, and the target resource
  • the number of subcarriers occupied by the unit in the frequency domain is less than or equal to 12.
  • the transceiver 901 is further configured to send, according to the second subframe, a PUSCH corresponding to the MPDCCH.
  • the processor 902 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 902 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the processor 902 and the transceiver 901 may be connected to each other through a bus 903.
  • the bus 903 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus 903 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the timing indication information includes first location offset information, where the first location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of the third subframe.
  • the third subframe is a starting subframe of the transmitting PUSCH determined according to a time domain position of the first subframe when a resource allocation granularity of the PUSCH is a resource block RB;
  • the determining, by the processor 902, the time domain location of the second subframe according to the timing indication information and the time domain location of the first subframe specifically, according to: the time domain location of the first subframe Determining a time domain location of the third subframe; determining a time domain location of the second subframe according to the first location offset information and a time domain location of the third subframe.
  • the timing indication information includes a second location offset information, where the second location offset information indicates a time domain location of the second subframe relative to a time domain of the first subframe. Offset of position;
  • the communications device further includes a memory 904, configured to save a first mapping relationship, where the first mapping relationship is a time domain location and a location offset of the first subframe when the resource allocation granularity of the PUSCH is RU Corresponding relationship, the position offset is an offset of a time domain position of the second subframe relative to a time domain position of the first subframe;
  • the processor 902 is in the time domain location according to the first subframe and the timing indication information determines the time domain location of the second subframe.
  • the method is specifically configured to: determine a time domain location of the second subframe according to the time domain location of the first subframe and the first mapping relationship .
  • the target resource unit includes one uplink subframe or consecutive uplink subframes in multiple time domains.
  • the memory 904 is further configured to store a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration manner and a resource unit.
  • the target resource unit is the communication device and the PUSCH in the second mapping relationship.
  • the target resource unit is the PUSCH scheduling device from the multiple resource units.
  • the memory 904 may include a volatile memory, such as a random-access memory (RAM); the memory 904 may also include a non-volatile memory.
  • a volatile memory such as a random-access memory (RAM); the memory 904 may also include a non-volatile memory.
  • a flash memory also called a flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 904 may also include a combination of the above types of memories.
  • the memory 904 may include a RAM, and may also include a non-volatile memory, such as at least one disk storage.
  • the second mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit 0 First resource unit and/or second resource unit 1 First resource unit and/or third resource unit 2 First resource unit 3 First resource unit and/or second resource unit 4 First resource unit and/or second resource unit
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the number M of subframes occupied by the target resource unit in the time domain and the number N of subcarriers occupied by the target resource unit in the frequency domain satisfy
  • An embodiment of the present application provides a terminal, where the terminal may determine a time domain location of a starting subframe of a PUSCH corresponding to the MPDCCH according to the received MPDCCH that includes the MPDCCH repeated transmission times and timing indication information, so that the The time domain location of the start subframe of the PUSCH corresponding to the MPDCCH is the same as the time domain location of the first subframe occupied by the target RU in the time domain, thereby enabling the terminal to fully utilize the subframe transmission occupied by the target RU.
  • the PUSCH corresponding to the MPDCCH is described, so that the transmission quality of data carried on the PUSCH corresponding to the MPDCCH can be guaranteed.
  • the embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device is configured to implement a PUSCH transmission method as shown in FIG. 4, and the PUSCH scheduling device 1000 includes: The transmitting unit 1001 and the processing unit 1002.
  • the sending unit 1001 is configured to send a machine physical downlink control channel (MPDCCH), where the MPDCCH includes the number of repeated transmissions of the MPDCCH and timing indication information, and the resource allocation granularity of the PUSCH corresponding to the MPDCCH is a target resource unit, The number of subcarriers occupied by the target resource unit in the frequency domain is less than or equal to 12.
  • MPDCCH machine physical downlink control channel
  • the processing unit 1002 is configured to control the sending unit 1001 to send the MPDCCH.
  • the PUSCH scheduling device and the terminal that receives the MPDCCH are configured with a first mapping relationship, where the first mapping relationship is a time domain location of a first subframe when a resource allocation granularity of the PUSCH is an RU a correspondence between position offsets, where the position offset is an offset of a time domain position of the second subframe relative to a time domain position of the first subframe, where the first subframe is the MPDCCH
  • the last subframe, the second subframe is a starting subframe that carries the uplink physical shared channel PUSCH corresponding to the MPDCCH;
  • the timing indication information is used to indicate that the terminal determines a time domain location of the second subframe according to the first mapping relationship.
  • the timing indication information is first location offset information
  • the first location offset information indicates an offset of a time domain location of the second subframe relative to a time domain location of a third subframe.
  • the third subframe is a starting subframe of the transmitted PUSCH determined according to the time domain position of the first subframe when the resource allocation granularity of the PUSCH is the resource block RB;
  • the processing unit 1002 is further configured to: determine, according to the repeated transmission times of the MPDCCH, a time domain location of the first subframe according to the sending, by the sending unit 1001, according to the time of the first subframe The domain location determines a time domain location of the third subframe; and the first location offset information is determined according to a time domain location of the second subframe and a time domain location of the third subframe.
  • the timing indication information includes second location offset information, where the second location offset information indicates a time domain location of the second subframe relative to a time domain location with the first subframe. Offset
  • the processing unit 1002 is further configured to: determine a time domain location of the first subframe according to the repeated transmission times of the MPDCCH; according to a time domain of the second subframe The location and the time domain location of the first subframe determine the second location offset information.
  • the PUSCH scheduling device 1000 further includes a receiving unit 1003, configured to receive a PUSCH corresponding to the MPDCCH.
  • the target resource unit includes one uplink subframe or consecutive uplink subframes in multiple time domains.
  • the PUSCH scheduling device and the terminal that receives the MPDCCH are configured with a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration mode and a resource unit.
  • the target resource unit receives the MPDCCH in the second mapping relationship.
  • the target resource unit is the PUSCH scheduling device from the multiple resources.
  • the second mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit 0 First resource unit and/or second resource unit 1 First resource unit and/or third resource unit 2 First resource unit 3 First resource unit and/or second resource unit 4 First resource unit and/or second resource unit 5 First resource unit 6 First resource unit
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the number M of subframes occupied by the target resource unit in the time domain and the number N of subcarriers occupied by the target resource unit in the frequency domain satisfy
  • the embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device is configured to implement a PUSCH sending method as shown in FIG. 4, and has the function of the PUSCH scheduling device 1100 as shown in FIG.
  • the PUSCH scheduling device 1100 includes a transceiver 1101 and a processor 1102. The transceiver 1101 and the processor 1102 are connected to each other.
  • the transceiver 1101 is configured to send a machine physical downlink control channel (MPDCCH), where the MPDCCH includes the number of repeated transmissions of the MPDCCH and timing indication information, and the resource allocation granularity of the PUSCH corresponding to the MPDCCH is a target resource unit, The number of subcarriers occupied by the target resource unit in the frequency domain is less than or equal to 12.
  • MPDCCH machine physical downlink control channel
  • the processor 1102 is configured to control the transceiver 1101 to send the MPDCCH.
  • the processor 1102 may be a CPU, an NP or a combination of a CPU and an NP.
  • the processor 1102 can also further include a hardware chip.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the processor 1102 and the transceiver 1101 may be connected to each other through a bus 1103.
  • the bus 1103 may be a PCI bus or an EISA bus or the like.
  • the bus 1103 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • the PUSCH scheduling device 1100 further includes: a memory 1104, configured to save a first mapping relationship, where the first mapping relationship is a time domain location and a location offset of the first subframe when the resource allocation granularity of the PUSCH is RU a corresponding relationship of the shift, the position offset being an offset of a time domain position of the second subframe relative to a time domain position of the first subframe, where the first subframe is the last of the MPDCCH a subframe, where the second subframe is a starting subframe that carries an uplink physical shared channel PUSCH corresponding to the MPDCCH;
  • a memory 1104 configured to save a first mapping relationship, where the first mapping relationship is a time domain location and a location offset of the first subframe when the resource allocation granularity of the PUSCH is RU a corresponding relationship of the shift, the position offset being an offset of a time domain position of the second subframe relative to a time domain position of the first subframe, where the first subframe is the last of the MPDC
  • the timing indication information is used to indicate that the terminal determines a time domain location of the second subframe according to the first mapping relationship.
  • the memory 1104 may include a volatile memory, such as a RAM; the memory 1104 may also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1104 may also include the above categories A combination of memories.
  • a volatile memory such as a RAM
  • the memory 1104 may also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1104 may also include the above categories A combination of memories.
  • the memory 1104 may include RAM, and may also include non-volatile memory, such as at least one disk storage.
  • the timing indication information includes first location offset information, where the first location offset information indicates a time domain location of the second subframe relative to a time domain location of the third subframe.
  • the third subframe is a starting subframe of a PUSCH that is determined according to a time domain position of the first subframe when a resource allocation granularity of the PUSCH is a resource block RB;
  • the processor 1102 is further configured to: determine, according to the repeated transmission times of the MPDCCH, a location of the first subframe according to the time interval of the first subframe; Determining a time domain location of the third subframe; determining the first location offset information according to a time domain location of the second subframe and a time domain location of the first subframe;
  • the timing indication information is second location offset information, where the second location offset information indicates a time domain location of the second subframe relative to a time domain location of the first subframe. Offset;
  • the processor 1102 is further configured to: before the transceiver 1101 sends the MPDCCH,
  • the target resource unit includes one uplink subframe or consecutive uplink subframes in multiple time domains.
  • the memory 1104 is further configured to: save a second mapping relationship, where the second mapping relationship is a mapping relationship between an uplink and downlink configuration mode and a resource unit;
  • the target resource unit receives the MPDCCH in the second mapping relationship.
  • the target resource unit is the PUSCH scheduling device from the multiple resources.
  • the transceiver 1101 is further configured to receive a PUSCH corresponding to the MPDCCH.
  • the second mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit 0 First resource unit and/or second resource unit 1 First resource unit and/or third resource unit
  • First resource unit 3 First resource unit and/or second resource unit 4 First resource unit and/or second resource unit 5 First resource unit 6 First resource unit
  • the first resource unit occupies 1 subframe in the time domain
  • the second resource unit occupies 3 subframes in the time domain
  • the third resource unit occupies 2 subframes in the time domain.
  • the number M of subframes occupied by the target resource unit in the time domain and the number N of subcarriers occupied by the target resource unit in the frequency domain satisfy
  • the embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device may send an MPDCCH including the MPDCCH repeated transmission times and the timing indication information to the terminal, so that the terminal can determine the start of the PUSCH corresponding to the MPDCCH according to the MPDCCH.
  • the time domain location of the subframe is such that the time domain location of the starting subframe of the PUSCH corresponding to the MPDCCH is the same as the time domain location of the first subframe occupied by the target RU in the time domain, thereby enabling the terminal to fully utilize the location
  • the subframes occupied by the target RU transmit the PUSCH corresponding to the MPDCCH, so that the transmission quality of data carried on the PUSCH corresponding to the MPDCCH can be guaranteed.
  • the embodiment of the present application provides a communication device, where the terminal is used to implement a PUSCH transmission method as shown in FIG. 7.
  • the communication device 1200 includes: a receiving unit 1201. Processing unit 1202 and transmitting unit 1203.
  • the receiving unit 1201 is configured to receive resource unit type indication information.
  • the processing unit 1202 is configured to determine, according to the resource unit type indication information, a type of a target resource unit RU that carries a physical uplink shared channel (PUSCH), where the RU time field corresponding to the target RU type includes an uplink subframe. Or a plurality of uplink subframes that are consecutive in the time domain, and the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain is less than or equal to 12.
  • PUSCH physical uplink shared channel
  • the sending unit 1203 is configured to send the PUSCH according to the target RU type.
  • mapping relationship between the uplink and downlink subframe configuration mode and the resource unit type is configured in the terminal;
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information
  • the determining, by the processing unit 1202, when determining the target resource unit RU type according to the resource unit type indication information specifically: determining, according to the target uplink and downlink subframe configuration manner and the mapping relationship, the target uplink and downlink sub The type of the RU corresponding to the frame configuration mode; the end determines the type of the RU indicated by the target resource unit type indication information in the RU type corresponding to the target uplink and downlink subframe configuration mode as the target RU type.
  • mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit type 0 First RU type and/or second RU type 1 First RU type and/or third RU type
  • First RU type 3 First RU type and/or second RU type 4 First capital type and/or second type 5 First RU type 6 First RU type
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the number of subframes M occupied by the RU corresponding to the target RU type in the time domain and the number of subcarriers occupied by the RU corresponding to the target RU type in the frequency domain satisfy
  • ⁇ a, M, N are positive integers, and a is an integer greater than or equal to 0.
  • the starting subframe of the RU corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the slot.
  • the embodiment of the present application provides a communication device, which is used to implement a PUSCH transmission method as shown in FIG. 7, and has the function of the communication device 1200 as shown in FIG.
  • the communication device 1300 includes a transceiver 1301 and a processor 1302, and the transceiver 1301 and the processor 1302 are connected to each other.
  • the transceiver 1301 is configured to receive resource unit type indication information and send a PUSCH under the control of the processor 1302.
  • the processor 1302 is configured to determine, according to the resource unit type indication information, a type of a target resource unit RU that carries a physical uplink shared channel (PUSCH), and control the transceiver 1301 to send the PUSCH according to the target RU type.
  • the RU time domain corresponding to the target RU type includes one uplink subframe or a plurality of uplink subframes consecutive in the time domain, and the subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain
  • the number is less than or equal to 12.
  • the processor 1302 may be a CPU, an NP or a combination of a CPU and an NP.
  • the processor 1302 may further include a hardware chip.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the processor 1302 and the transceiver 1301 may be connected to each other through a bus 1303.
  • the bus 1303 may be a PCI bus or an EISA bus or the like.
  • the bus 1303 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the communications device further includes a processor 1304, configured to save a mapping relationship between the pre-configured uplink and downlink subframe configuration mode and the resource unit type; if the mapping relationship is in the uplink and downlink configuration mode and the resource unit type.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner;
  • the memory 1304 can include a volatile memory, such as a RAM; the memory 1304 can also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1304 can also include the A combination of memories.
  • a volatile memory such as a RAM
  • the memory 1304 can also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1304 can also include the A combination of memories.
  • the memory 1304 may include RAM and may also include non-volatile memory, such as at least one disk storage.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information
  • the type of the RU corresponding to the frame configuration mode, and the type of the RU indicated by the target resource unit type indication information in the RU type corresponding to the target uplink and downlink subframe configuration mode is determined as the target RU type.
  • mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit type 0 First RU type and/or second RU type 1 First RU type and/or third RU type 2 First RU type 3 First RU type and/or second RU type 4 First capital type and/or second type 5 First RU type 6 First RU type
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the number of subframes M occupied by the RU corresponding to the target RU type in the time domain and the number of subcarriers occupied by the RU corresponding to the target RU type in the frequency domain satisfy
  • ⁇ a, M, N are positive integers, and a is an integer greater than or equal to 0.
  • the starting subframe of the RU corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the slot.
  • An embodiment of the present application provides a communication device, where the terminal may determine a target resource unit type according to the received resource unit type indication information, and the RU corresponding to the target RU type is mapped to an uplink subframe of the system frame or The multiple uplink subframes in the time domain are transmitted, and the PUSCH is transmitted, which can solve the problem that the channel estimation result caused by the discontinuity of the subframe included in the resource unit is inaccurate.
  • the embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device is used to implement a PUSCH transmission method as shown in FIG. 7.
  • the PUSCH scheduling device 1400 includes: The transmitting unit 1401 and the processing unit 1402.
  • the sending unit 1401 is configured to send the resource unit type indication information, where the resource unit type indication information is used to determine a type of the target resource unit RU that carries the physical uplink shared channel PUSCH, where the target RU type corresponds to the RU
  • the domain includes one uplink subframe or a plurality of uplink subframes that are consecutive in the time domain, and the number of subcarriers occupied by the resource unit corresponding to the target RU type in the frequency domain is less than or equal to 1.
  • the processing unit 1402 is configured to control the sending unit 1401 to send the resource unit type indication information.
  • the PUSCH scheduling device 1400 further includes a receiving unit 1403, configured to receive the PUSCH.
  • the PUSCH scheduling device and the terminal that receives the resource unit type indication information are configured with a mapping relationship between an uplink and downlink subframe configuration mode and a resource unit type.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information.
  • mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit type 0 First RU type and/or second RU type 1 First RU type and/or third RU type 2 First RU type 3 First RU type and/or second RU type 4 First RU type and/or second RU type 5 First RU type 6 First RU type
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the number of subframes M occupied by the RU corresponding to the target RU type in the time domain and the number of subcarriers occupied by the RU corresponding to the target RU type in the frequency domain satisfy
  • ⁇ a, M, N are positive integers, and a is an integer greater than or equal to 0.
  • the starting subframe of the RU corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the slot.
  • the embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device is configured to implement a PUSCH sending method as shown in FIG. 7, and has the function of the PUSCH scheduling device 1400 as shown in FIG. 14.
  • the PUSCH scheduling apparatus 1500 includes a transceiver 1501 and a processor 1502. The transceiver 1501 and the processor 1502 are connected to each other.
  • the transceiver 1501 is configured to send resource unit type indication information, where the resource unit type indication information is used to determine a type of a target resource unit RU that carries a physical uplink shared channel (PUSCH), where the target RU type corresponds to an RU time domain.
  • the method includes an uplink subframe or a plurality of uplink subframes that are consecutive in the time domain, and the resource unit corresponding to the target RU type occupies less than or equal to 1 in the frequency domain.
  • the processor 1502 is configured to control the transceiver 1501 to send the resource unit type indication information.
  • the processor 1502 may be a CPU, an NP or a combination of a CPU and an NP.
  • the processor 1502 may further include a hardware chip.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the processor 1502 and the transceiver 1501 may be connected to each other through a bus 1503.
  • the bus 1503 may be a PCI bus or an EISA bus or the like.
  • the bus 1503 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 15, but it does not mean that there is only one bus or one type of bus.
  • the PUSCH scheduling device further includes a memory 1504, configured to save a mapping relationship between the pre-configured uplink and downlink subframe configuration manner and the resource unit type.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner.
  • the memory 1504 may include a volatile memory, such as a RAM; the memory 1504 may also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1104 may also include the above categories A combination of memories.
  • a volatile memory such as a RAM
  • the memory 1504 may also include a non-volatile memory, such as a flash memory, HDD or SSD; the memory 1104 may also include the above categories A combination of memories.
  • the memory 1504 may include a RAM, and may also include a non-volatile memory, such as at least one disk storage.
  • the transceiver is further configured to receive the PUSCH.
  • the resource unit type indication information includes a target uplink and downlink subframe configuration manner and target resource unit type indication information.
  • mapping relationship satisfies the following table:
  • Time division duplex TDD uplink and downlink configuration mode Resource unit type 0 First RU type and/or second RU type 1 First RU type and/or third RU type 2 First RU type 3 First RU type and/or second RU type 4 First RU type and/or second RU type 5 First RU type 6 First RU type
  • the RU corresponding to the first RU type occupies 1 subframe in the time domain, and the RU corresponding to the second RU type occupies 3 subframes in the time domain, and the RU corresponding to the third RU type is in the time domain. It takes up 2 subframes.
  • the number of subframes M occupied by the RU corresponding to the target RU type in the time domain and the number of subcarriers occupied by the RU corresponding to the target RU type in the frequency domain satisfy
  • ⁇ a, M, N are positive integers, and a is an integer greater than or equal to 0.
  • the starting subframe of the RU corresponding to the target RU type is the first uplink subframe in the system frame or the first uplink subframe in the slot.
  • An embodiment of the present application provides a PUSCH scheduling device, where the PUSCH scheduling device may send resource unit type indication information to a terminal, so that the terminal determines a target resource unit type according to the received resource unit type indication information, by using the The RU corresponding to the target RU type is mapped to one uplink subframe of the system frame or multiple uplink subframes in the time domain, and the PUSCH is transmitted, which can solve the problem that the channel estimation result caused by the discontinuity of the subframe included in the resource unit is inaccurate. problem.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种物理上行共享信道PUSCH传输方法及装置，该方法包括：终端接收机器物理下行控制信道MPDCCH，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息；根据所述MPDCCH的重复发送次数确定第一子帧的时域位置，所述第一子帧为承载所述MPDCCH的最后一个子帧；根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12；在所述第二子帧上发送所述MPDCCH对应的PUSCH。

Description

一种物理上行共享信道PUSCH传输方法及装置 技术领域
本申请涉无线通信技术领域，尤其涉及一种物理上行共享信道PUSCH传输方法及装置。
背景技术
目前，通信协议中时分双工(time division duplex，TDD)模式下，机器通信(machine type communication，MTC)系统中物理上行共享信道(physical uplink shared channel，PUSCH)资源调度粒度为资源块(resource block，RB)，PUSCH传输时占用的子载波个数较多，进而使得终端在每个载波上的发射功率较小。
由于TDD模式下上行数据和下行数据在时域上占用不同的子帧传输，若定义与频分双工(frequency division duplex，FDD)模式下窄带物理上行共享信道(narrow physical uplink shared channel，NPUSCH)类似的资源调度粒度，可能会出现定义的资源单元对应的上行子帧中第一个子帧的时域位置与物理上行共享信道(physical uplink shared channel，PUSCH)对应的上行子帧中第一个子帧的时域位置不同，使得上行数据占用较少的子帧传输，这不仅会导致数据传输质量较差，还造成资源的浪费。例如，对于TDD上下行配置方式1，若定义RU在时域上占用2个子帧，在频域上占用6个子载波，当承载机器物理下行控制信道(physical downlink control channel，MPDCCH)的最后一个子帧为子帧4，该MPDCCH对应的PUSCH在子帧8上传输，此时该MPDCCH对应的PUSCH只能占用子帧8传输，如图1所示。
发明内容
第一方面，本申请提供了一种PUSCH传输方法，以解决TDD模式下PUSCH的资源分配粒度为资源单元时承载PUSCH的起始子帧与资源单元在时域上占用的首个子帧时域位置不同，造成的上行数据传输质量不高以及资源浪费的问题。该方法包括：终端接收PUSCH调度设备发送的MPDCCH，根据所述MPDCCH中包含的MPDCCH的重复发送次数确定第一子帧的时域位置，并根据所述MPDCCH中包含的定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置，根据所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。其中，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
通过上述方法，终端接收包含MPDCCH重复发送次数和所述定时指示信息的MPDCCH，根据所述MPDCCH的重复发送次数确定第一子帧的时域位置，根据所述第一子帧的时域位置以及所述定时指示信息确定第二子帧的时域位置，以使承载所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，进而使得所述终端能够充分利用所述目标RU所占用的子帧传输所述MPDCCH对应的PUSCH，以保证所述MPDCCH对应的PUSCH上承载的数据的传输质量，其中，所述 第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为所述MPDCCH对应的PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标RU，所述目标RU在频域上占用的子载波个数小于或等于12。并且，所述终端根据所述第一子帧的时域位置以及所述定时指示信息确定第二子帧的时域位置，使得承载所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，不需要限制承载所述MPDCCH的子帧的时域位置，因而使得所述PUSCH调度设备发送的MPDCCH具有较大的灵活性。
一个可能的实施方式中，所述PUSCH调度设备为网络侧设备或终端。当所述PUSCH调度设备为网络侧设备时，所述网络侧设备发送包含MPDCCH的重复发送次数的MPDCCH以及包含所述定时指示信息的高层信令，所述终端接收包含所述高层信令，从所述高层信令中获取所述定时指示信息；所述终端根据所述MPDCCH的重复发送次数确定所述第一子帧的时域位置，根据所述定时指示信息和所述第一子帧的时域位置确定所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。
一个可能的实施方式中，当所述定时指示信息中包括第一位置偏移信息时，所述终端根据所述第一子帧的时域位置、所述第一位置偏移信息和第三子帧的时域位置确定所述第二子帧的时域位置。其中，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量；所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧。
一个可能的实施方式中，当所述定时指示信息中包括所述第一位置偏移信息时，所述PUSCH调度设备在发送所述MPDCCH之前，还根据所述MPDDCH的重复发送次数确定所述第一子帧的时域位置；根据所述第一子帧的时域位置，确定所述第一子帧的时域位置，确定所述第三子帧的时域位置；根据所述第二子帧的时域位置以及所述第三子帧的时域位置，确定所述第一位置偏移信息。
一个可能的实施方式中，当所述定时指示信息中包含指示第二位置偏移信息时，所述终端根据所述第一子帧的时域位置和所述第二位置偏移量，确定所述第二子帧的时域位置，其中，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量。
一个可能的实施方式中，若所述定时指示信息中包括所述第二位置偏移信息，所述PUSCH调度设备在发送所述MPDCCH之前，还所述MPDDCH的重复发送次数确定所述第一子帧的时域位置；根据所述第一子帧的时域位置以及所述第二子帧的时域位置，确定所述第二位置偏移信息。
一个可能的实施方式中，当所述终端与所述PUSCH调度设备中配置有第一映射关系时，所述定时指示信息可以用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置。所述终端根据所述第一子帧的时域位置和所述第一映射关系，确定所述第二子帧的时域位置。其中，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量。
一个可能的实施方式中，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧，使得传输所述MPDCCH对应的PUSCH的子帧在时域上连续，进而可以提高TDD模式下PUSCH的资源分配粒度为资源单元时信道估计的准确性。
一个可能的实施方式中，所述终端以及PUSCH调度设备中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系，所述PUSCH调度设备为发送所述MPDCCH的设备；
当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述终端的一种资源单元。
一个可能的实施方式中，所述第二映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元
0 第一资源单元和/或第二资源单元
1 第一资源单元和/或第三资源单元
2 第一资源单元
3 第一资源单元和/或第二资源单元
4 第一资源单元和/或第二资源单元
5 第一资源单元
6 第一资源单元
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
一个可能的实施方式中，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数，使得M×N尽量接近12，以减少TDD模式下PUSCH以资源单元为资源分配粒度进行传输对通信息系统架构的影响。并且，相对于现有技术中以RB(在频域上占用12个子载波)为资源分配粒度传输PUSCH，终端以时域上占用的子帧个数M和在频域上占用的子载波个数N满足|M×N-12|≤a的资源单元传输PUSCH时，PUSCH占用的子载波个数较少，进而可以增加所述终端在每个子载波上的发射功率。
一个可能的实施方式中，所述目标资源单元可以在时域上占用1个子帧，在频域上占用12个子载波；或者，所述目标资源单元可以在时域上占用2个子帧，在频域上占用6个子载波；或者，所述目标资源单元可以在时域上占用3个子帧，在频域上占用4个子载波；或者，所述目标资源单元可以在时域上占用4个子帧，在频域上占用3个子载波；或者，所述目标资源单元可以在时域上占用4个子帧，在频域上占用2个子载波；或者，所述目标资源单元可以在时域上占用6个子帧，在频域上占用2个子载波；或者，所述目标资源单元可以在时域上占用8个子帧，在频域上占用2个子载波。
一个可能的实施方式中，所述终端也可以向能够与所述终端通信的其他终端发送包含MPDCCH重复发送次数和所述定时指示信息的MPDCCH，调度能够与所述终端通信的其他终端向所述终端发送该MPDCCH对应的PUSCH。
第二方面，本申请还提供了另一种PUSCH传输方法，以解决TDD模式下PUSCH的资源分配粒度为资源单元时资源单元包含的子帧不连续导致信道估计性能价差的问题。该方法包括：终端接收PUSCH调度设备发送的资源单元类型指示信息，根据所述资源单元 类型指示信息，确定承载PUSCH的目标资源单元RU的类型，根据所述目标RU类型，发送所述PUSCH。其中，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12。
通过上述方法，所述终端接收所述PUSCH调度设备发送的资源单元RU类型指示信息，根据所述资源单元RU类型指示信息确定目标RU类型，根据所述目标RU类型发送所述PUSCH，其中，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12，使得所述终端通过所述目标RU类型对应的RU映射到系统帧的一个上行子帧或时域上连续的多个上行子帧，发送所述PUSCH，能够解决资源单元包含的子帧不连续导致的信道估计结果不准确的问题。
一个可能的实施方式中，所述PUSCH调度设备为能够与终端通信的其它终端或高层信令。当所述PUSCH调度设备为能够与终端通信的其它终端时，所述PUSCH调度设备可以通过MPDCCH将所述资源单元类型指示信息发送给所述终端。当所述PUSCH调度设备为网络侧设备时，所述PUSCH调度设备可以通过MPDCCH或高层信令将所述资源单元类型指示信息发送给所述终端。
一个可能的实施方式中，当所述终端中配置有上下行子帧配置方式和资源单元类型的映射关系，所述终端可以通过以下但不限于以下两种方式确定所述目标RU类型：
方式A：若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式，所述终端将所述映射关系中所述目标上下行子帧配置方式对应的资源单元类型，确定为所述目标RU类型。
方式B：若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息；
所述终端根据所述目标上下行子帧配置方式和所述映射关系，确定所述目标上下行子帧配置方式对应的资源单元类型，将所述目标上下行子帧配置方式对应的资源单元类型中所述目标资源单元类型指示信息所指示的资源单元类型，确定为所述目标RU类型。
一个可能的实施方式中，所述映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元类型
0 第一RU类型和/或第二RU类型
1 第一RU类型和/或第三RU类型
2 第一RU类型
3 第一RU类型和/或第二RU类型
4 第一资RU类型和/或第二RU类型
5 第一RU类型
6 第一RU类型
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
一个可能的实施方式中，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N为正整数，a为大于或等于0的整数，以使M×N尽量接近12，从而可以减少TDD模式下 PUSCH以资源单元为资源分配粒度进行传输对通信息系统架构的影响。并且，相对于现有技术中以RB(在频域上占用12个子载波)为资源分配粒度传输PUSCH，终端以时域上占用的子帧个数M和在频域上占用的子载波个数N满足|M×N-12|≤a的资源单元传输PUSCH时，PUSCH占用的子载波个数较少，进而可以增加所述终端在每个子载波上的发射功率。
一个可能的实施方式中，所述目标RU类型对应的RU的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧。
第三方面，本申请提供了一种通信设备，所述通信设备具有实现上述第一方面方法实例中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实施方式中，所述通信设备的结构中包括接收单元、处理单元和发送单元，这些单元可以执行上述第一方面的方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
一种可能的实施方式中，所述通信设备的结构中包括收发器、存储器以及处理器，该处理器被配置为支持所述终端执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述协调器必要的程序指令和数据。
第四方面，本申请还提供了一种PUSCH调度设备，所述PUSCH调度设备具有实现上述第一方面方法实例中所述PUSCH调度设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实施方式中，所述PUSCH调度设备的结构中包括处理单元和发送单元，这些单元可以执行上述第一方面的方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
一种可能的实施方式中，所述PUSCH调度设备的结构中包括收发器、存储器以及处理器，该处理器被配置为支持所述PUSCH调度设备执行上述第一方面的方法示例中相应的功能。所述存储器与所述处理器耦合，其保存所述协调器必要的程序指令和数据。
第五方面，本申请还提供了一种通信设备，所述通信设备具有实现上述第二方面方法实例中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实施方式中，所述通信设备的结构中包括接收单元、处理单元和发送单元，这些单元可以执行上述第二方面的方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第六方面，本申请还提供了一种PUSCH调度设备，所述PUSCH调度设备具有实现上述第二方面方法实例中所述PUSCH调度设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实施方式中，所述PUSCH调度设备的结构中包括处理单元和发送单元，这些单元可以执行上述第二方面的方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
一种可能的实施方式中，所述PUSCH调度设备的结构中包括收发器、存储器以及处 理器，该处理器被配置为支持所述PUSCH调度设备执行上述第二方面的方法示例中相应的功能。所述存储器与所述处理器耦合，其保存所述协调器必要的程序指令和数据。
第七方面，本申请还提供一种计算机存储介质，该存储介质中存储有软件程序，该软件程序在被一个或多个处理器读取并执行时可实现任一方面的任意一种设计提供的方法。
第八方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面中的任一种方法。
附图说明
图1为现有技术中传输PUSCH的子帧与资源单元中子帧的对应关系；
图2为本申请实施例中资源单元的结构示意图；
图3为本申请实施例提供的一种通信系统结构示意图；
图4为本申请实施例提供一种PUSCH传输方法的流程示意图；
图5为本申请实施例中传输PUSCH的子帧与资源单元中子帧的对应关系；
图6为本申请实施例中资源单元与系统帧的映射关系；
图7为本申请实施例提供的另一种PUSCH传输方法的流程示意图；
图8为申请实施例提供的一种通信设备的结构示意图；
图9为申请实施例提供的一种通信设备的结构示意图；
图10为申请实施例提供的一种PUSCH调度设备的结构示意图；
图11为申请实施例提供的一种PUSCH调度设备的结构示意图；
图12为申请实施例提供的另一种通信设备的结构示意图；
图13为申请实施例提供的另一种通信设备的结构示意图；
图14为申请实施例提供的另一种PUSCH调度设备的结构示意图；
图15为申请实施例提供的另一种PUSCH调度设备的结构示意图。
具体实施方式
本申请实施例提供一种物理上行共享信道PUSCH传输方法及装置。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
以下，对本申请实施例涉及部分用语进行解释说明，以便于本领域技术人员理解。
1)资源单元(resource unite，RU)，为PUSCH的资源分配粒度，资源单元在频域上占用的子载波数小于或等于12。资源单元可以用该资源单元在时域上包括的子帧(subframe)个数(或者时隙(slot)个数)以及该资源单元在频域上包括的子载波(subcarrier)个数定义，即i subcarriers×j subframes，i，j为正整数。
TDD通信系统中，资源单元可以包括但不限于以下几种类型资源单元：6subcarriers×2subframes，4subcarriers×3subframes，3subcarriers×4subframes，12subcarriers×1subframes，2subcarriers×6subframes，2subcarriers×4subframes以及2subcarriers×8subframes。例如，当资源单元在时域上包括2个子帧，在频域上包括6个子载波时，资源单元结构如图2所示。
2)多个，是指两个或两个以上。
3)和/或，描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的PUSCH传输方法、装置及设备进行详细说明。
图3示出了本申请实施例提供的PUSCH传输方法适用的一种可能的通信系统架构，所述通信系统300包括：网络侧设备301以及至少一个终端302。其中，网络侧设备301用于向所述至少一个终端302发送MPDCCH，通过所述MPDCCH调度所述至少一个终端302发送所述MPDCCH对应的PUSCH，其中所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12；或者，向所述至少一个终端302发送资源单元类型指示信息，以使所述至少一个终端302根据所述资源单元类型指示信息确定目标资源单元类型，根据目标资源单元类型发送PUSCH，其中，所述目标RU类型对应的资源单元时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12。
另外，针对所述至少一个终端302中的任意一个，该终端302还可以通过MPDCCH调度所述通信系统300中能够与该终端通信的其它终端通过该MPDCCH对应的PUSCH向该终端发送数据；或者向能够与该终端通信的其它终端通发送资源单元类型指示信息，以使能够与该终端通信的其它终端根据所述资源单元类型指示信息确定目标资源单元类型，根据目标资源单元类型发送PUSCH。
所述通信系统300可以是蜂窝移动通信系统，比如，所述无线通信系统可以是第三代移动通信技术(the 3th generation mobile communication，3G)系统，也可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(long term evolution，LTE)系统，或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统。网络侧设备301可以是3G系统中的基站(base station，BS)或者4G系统中采用的演进型基站(eNB)。或者，网络侧设备101也可以是5G系统中采用集中分布式架构的基站(gNB)。
终端302也可称为用户设备(User Equipment，UE)，或者可称之为Terminal、移动台(Mobile Station，MS)、移动终端(Mobile Terminal)等，终端302可以经无线接入网(Radio Access Network，简称为RAN)与一个或多个核心网进行通信，例如，终端102可以是移动电话(或称为“蜂窝”电话)、具有移动终端的计算机等，例如，终端102还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换数据。本申请实施例中的终端还可以是D2D(Device to Device，设备与设备)终端或者M2M(Machine to Machine，机器与机器)终端。
本申请实施例提供的一种PUSCH传输方法，适用于如图3所示的通信系统300。参阅图4所示，该方法的具体流程包括以下步骤：
S401：PUSCH调度设备发送MPDCCH。其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息，所述第一子帧为承载所述MPDCCH的最后一个子帧。所述定时指示信息用于指示基于所述第一子帧的时域位置确定第二子帧的时域位置所需 的信息。
可选地，所述PUSCH调度设备为网络侧设备或终端。
具体实施中，所述PUSCH调度设备将所述MPDCCH的重复发送次数和所述定时指示信息携带在所述MPDCCH中的下行控制信息(downlink control information，DCI)中。
相应地，终端接收所述MPDCCH，以获取所述MPDCCH的重复发送次数和所述定时指示信息。需要说明的是，当所述PUSCH调度设备为终端时，接收所述MPDCCH的终端为能够与该终端通信的其他终端。
在具体实施中，所述第一子帧的时域位置可以用所述第一子帧在系统帧中的子帧号表示。LTE TDD通信系统的系统帧结由两个5ms半帧构成，每个半帧中包含5个1ms长度的子帧，一个子帧包括2个时隙。系统帧中的子帧分为三类：下行子帧、上行子帧和特殊子帧。LTE TDD通信系统支持如表1所示的7种上下行子帧配置(uplink-downlink configuration)方式，其中，U表示上行子帧，D表示下行子帧，S表示特殊子帧。例如，若所述MPDCCH的最后一个子帧所在的系统帧为子帧5，则所述第一子帧的时域位置可以用子帧5表示。
表1 上下行子帧配置方式
Figure PCTCN2018076781-appb-000001
S402：所述终端根据所述MPDCCH的重复发送次数，确定所述第一子帧的时域位置。
具体地，当所述MPDCCH的重复发送次数大于或等于1时，所述终端根据接收到的首个MPDCCH以及所述MPDCCH的重复发送次数，确定所述第一子帧的时域位置。当所述MPDCCH的重复发送次数为0时，所述第一子帧的时域位置为所述终端根据接收到的MPDCCH的子帧的时域位置。
S403：所述终端根据所述第一子帧的时域位置以及所述定时指示信息，确定第二子帧的时域位置。其中，所述第二子帧为承载所述MPDCCH对应的PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
实施中，所述终端可以通过但不限于以下三种方式确定所述第二子帧的时域位置：
方式一：当所述定时指示信息中包括第一位置偏移信息时，所述终端根据所述第一子帧的时域位置确定所述第三子帧的时域位置；根据所述第一位置偏移信息和第三子帧的时域位置确定所述第二子帧的时域位置。
其中，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量；所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧确定的发送PUSCH的起始子帧。
TDD模式下当PUSCH的资源分配粒度为资源块RB时，第一子帧的时域位置与第三子帧的时域位置相对于第一子帧的时域位置的偏移量，即PUSCH的调度时序如表2所示，若所述第一子帧为子帧n，则所述第三子帧为子帧n+k PUSCH。例如，所述终端与所述网络侧设备约定的上下行配置方式为配置方式0，若所述第一子帧为子帧0，则所述第三子帧为子帧4。
表2 TDD模式下不同上下行配对应的k PUSCH
Figure PCTCN2018076781-appb-000002
具体地，当所述定时指示信息中包括所述第一位置偏移信息时，所述终端根据所述第一子帧的时域位置以及在PUSCH的资源分配粒度为资源块RB时PUSCH的调度时序，确定所述第三子帧的时域位置，并根据所述第三子帧的时域位置以及所述第一位置偏移信息确定所述第二子帧的时域位置。
具体实施中，所述第一位置偏移信息可以指示第一绝对位置偏移量或者第一相对位置偏移量，其中，所述第一绝对位置偏移量为从所述第三子帧到所述第二子帧的所有子帧个数，所述第一相对位置偏移量为从所述第三子帧到所述第二子帧的有效子帧个数。所述有效子帧为从所述第三子帧到所述第二子帧的带宽降低低复杂度(bandwidth reduced low complexity，BL)/覆盖增强(cover enhanced，CE)。
具体实施中，当所述定时指示信息为所述第一位置偏移信息时，所述PUSCH调度设备在发送所述MPDCCH之前，还根据所述MPDDCH的重复发送次数确定所述第一子帧的时域位置；根据所述第一子帧的时域位置；根据所述第一子帧的时域位置确定所述第三子帧的时域位置；根据所述第二子帧的时域位置以及所述第三子帧的时域位置，确定所述第一位置偏移信息。
一个具体的实施方式中，所述PUSCH调度设备根据所述目标RU在时域上占用的子帧个数以及所述第一子帧的时域位置，确定所述第二子帧的时域位置，使得所述第二子帧的时域位置与所述目标资源单元中的首个子帧时域位置相同。
例如，当所述目标RU在时域上占用2个子帧，所述终端与所述PUSCH调度设备约定的上下行配置方式为1，所述第一子帧为子帧4时，所PUSCH调度设备根据所述第一子帧的时域位置查询上述表2，确定所述第三子帧为子帧8，由于所述目标RU在时域上占用2个子帧，因此所述第二子帧为下一个系统帧中的子帧2，以使所述第二子帧的时域位置与所述目标资源单元中的首个子帧时域位置相同，此时所述第一绝对位置偏移量为4个子帧(所述第一相对位置偏移量为1个子帧)。所述终端根据所述第一子帧的时域位置查询上述表2，确定所述第三子帧为子帧8(4+4)，所述第二子帧为8+4＝12，即下一系统帧中 的子帧2，如图5所示，所述终端在所述下一个系统帧中所述目标RU包括的子帧2和子帧3上发送所述MPDCCH对应的PUSCH。
方式二、当所述定时指示信息用于指示第二位置偏移信息时，所述终端根据所述第一子帧的时域位置和所述第二位置偏移信息，确定所述第二子帧的时域位置，其中，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量。
具体实施中，所述第二位置偏移信息可以指示第二绝对位置偏移量或者第二相对位置偏移量，其中，所述第二绝对位置偏移量为从所述第一子帧到所述第二子帧的所有子帧个数，所述第二相对位置偏移量为从所述第一子帧到所述第二子帧的有效子帧个数，所述有效子帧为BL/CE子。
具体实施中，当所述定时指示信息为所述第二位置偏移量信息时，所述PUSCH调度设备在发送所述MPDCCH之前，还根据所述MPDDCH的重复发送次数确定所述第一子帧的时域位置；根据所述第二子帧的时域位置以及所述第一子帧的时域位置，确定所述第二位置偏移信息。
例如，当所述目标RU在时域上占用2个子帧，所述终端与所述PUSCH调度设备约定的上下行配置方式为1，所述第一子帧为子帧4时，所PUSCH调度设备根据所述第一子帧的时域位置查询上述表2可知，PUSCH能够在子帧8或子帧8之后的子帧上传输，由于所述目标RU在时域上占用2个子帧，因此确定所述第二子帧为下一个系统帧中的子帧2，以使所述第二子帧的时域位置与所述目标资源单元中的首个子帧时域位置相同，此时所述第二绝对位置偏移量为8个子帧(所述第一相对位置偏移量为3个子帧)。所述终端根据所述第一子帧的时域位置和所述第二绝对位置偏移量，确定所述第二子帧为8+4＝12，即下一系统帧中的子帧2，如图5所示，所述终端在所述下一个系统帧中所述目标RU包括的子帧2和子帧3上发送所述MPDCCH对应的PUSCH。
方式三、当所述终端与所述PUSCH调度设备中配置有第一映射关系时，所述定时指示信息可以用于指示所述终端根据所述第一映射关系确定所述第二子帧的时域位置，其中，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量。
所述终端根据所述第一子帧的时域位置和所述第一映射关系，确定所述第一子帧的时域位置对应的位置偏移量，根据所述第一子帧的时域位置对应的位置偏移量以及所述第一子帧的时域位置确定所述第二子帧的时域位置。
具体实施中，所述第一映射关系预先配置在所述终端和所述PUSCH调度设备中。针对所述第一映射关系中任意一个第一子帧的时域位置，该第一子帧的时域位置偏移该第一子帧的时域位置对应的位置偏移量后，与所述目标RU中首个子帧的时域位置相同。
例如，当所述目标RU在时域上占用2个子帧，在频域上占用6个子载波时，所述第一映射关系如表3所示，其中，所示第一子帧的时域位置用所述第一子载波在系统帧中的子帧号，所述第二位置偏移量为所述第二绝对位置偏移量。
表3 第一映射关系
Figure PCTCN2018076781-appb-000003
为了保证信道估计结果的准确性，具体实施中所述目标资源单元时域上包含一个上行子帧，或者包含多个时域上连续的上行子帧，即承载所述MPDCCH对应的PUSCH的子帧在时域上连续。例如，所述目标资源单元结构如图2所示时，针对上下行配置方式1，所述目标资源单元映射到系统帧上如图6所示。
实施中，所述终端以及所述PUSCH调度设备中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的对应关系，当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述终端与所述PUSCH调度约定的上下行配置方式对应的资源单元。例如，所述第二映射关系如表4所示：
表4 第二映射关系
Figure PCTCN2018076781-appb-000004
当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述终端的一种资源单元。例如，所述第二映射关系如表5所示：
表5 第二映射关系
Figure PCTCN2018076781-appb-000005
Figure PCTCN2018076781-appb-000006
具体实施中，当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，若所述PUSCH调度设备为网络侧设备，所述网络侧设备从所述多种资源单元中选择一种资源单元作为所述目标资源单元，可以通过所述MPDCCH或高层信令将所述目标资源单元通知给所述终端。
一个具体的实施方式中，针对如上述表1所示的7中上下行配置方式，所述第二映射关系满足如下表格：
Figure PCTCN2018076781-appb-000007
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
针对所述第二映射关系中的任意一种上下行配置方式，该上下行配置方式对应的资源单元映射到该上下行配置方式对应的系统帧上时，该上下行配置方式对应系统帧中所有的上行子帧包括在一个或多个该上下行配置方式对应的资源单元中，且每个该上下行配置方式对应的资源单元中包含的子帧连续，例如图2所示的资源单元与系统帧的映射关系，使得所述终端能够有效利用与所述PUSCH调度设备约定的上下行配置方式中的上行子帧，以资源单元为资源分配粒度传输PUSCH。
实施中，为了减少TDD模式下PUSCH以资源单元为资源分配粒度进行传输对通信息系统架构的影响，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数，以使M×N尽量接近12。并且，相对于现有技术中以RB(在频域上占用12个子载波)为资源分配粒度传输PUSCH，终端以时域上占用的子帧个数M和在频域上占用的子载波个数N满足|M×N-12|≤a的资源单元传输PUSCH时，PUSCH占用的子载波个数较少，进而可以增加所述终端在每个子载波上的发射功率。
S404：所述终端根据所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。
相应地，当所述定时指示信息中包括所述第一位置偏移信息或所述第二位置偏移信息时，所述PUSCH调度设备根据所述第一子帧的时域位置以及所述目标资源单元在时域上占用的子帧个数，确定第一位置偏移信息确定所述第二子帧的时域位置，在所述第二子帧上接收所述MPDCCH对应的PUSCH。
当所述定时指示信息用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置时，所述PUSCH调度设备根据所述第一子帧的时域位置和所述第一映射关系，确定所述第一子帧的时域位置对应的位置偏移量，根据所述第一子帧的时域位置对应的位置偏移量以及所述第一子帧的时域位置，确定所述第二子帧的时域位置，在所述第二子帧上接收所述MPDCCH对应的PUSCH。
一个具体的实施例中，当所述PUSCH调度设备为网络侧设备时，所述网络侧设备发送包含MPDCCH的重复发送次数的MPDCCH以及包含所述定时指示信息的高层信令，所述终端接收包含所述高层信令，从所述高层信令中获取所述定时指示信息；所述终端根据所述MPDCCH的重复发送次数确定所述第一子帧的时域位置，根据所述定时指示信息和所述第一子帧的时域位置确定所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。其中，所述终端根据所述定时指示信息和所述第一子帧的时域位置确定所述第二子帧的时域位置的具体方法参见上述步骤S303中的相关描述，此处不再赘述。
需要说明的是，当所述PUSCH调度设备为网络侧设备时，本申请实施例并不对所述网络侧设备发送包含MPDCCH的重复发送次数的MPDCCH以及包含所述定时指示信息的高层信令的先后顺序进行限定。所述网络侧设备可以先发送包含MPDCCH的重复发送次数的MPDCCH，再发送包含所述定时指示信息的高层信令，也可以先发送包含所述定时指示信息的高层信令再发送包含所述定时指示信息的高层信令，还可以同时发送包含MPDCCH的重复发送次数的MPDCCH以及包含所述定时指示信息的高层信令。
可选地，所述终端也可以向能够与所述终端通信的其他终端发送包含MPDCCH重复发送次数和所述定时指示信息的MPDCCH，以使能够与所述终端通信的其他终端通过上述步骤S302-S304向所述终端发送该MPDCCH对应的PUSCH。
通过上述方法，所述终端接收包含MPDCCH重复发送次数和所述定时指示信息的MPDCCH，根据所述MPDCCH的重复发送次数确定第一子帧的时域位置，根据所述第一子帧的时域位置以及所述定时指示信息确定第二子帧的时域位置，以使承载所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，进而使得所述终端能够充分利用所述目标RU所占用的子帧传输所述MPDCCH对应的PUSCH，从而可以保证所述MPDCCH对应的PUSCH上承载的数据的传输质量，其中，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为所述MPDCCH对应的PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标RU，所述目标RU在频域上占用的子载波个数小于或等于12。并且，所述终端根据所述第一子帧的时域位置以及所述定时指示信息确定第二子帧的时域位置，使得承载所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，不需要限制承载所述MPDCCH的子帧的时域位置，因而使得所述PUSCH调度设备发送的MPDCCH具有较大的灵活性。
参阅图7所示，本申请实施例还提供了另一种PUSCH传输方法，适用于如图3所示的通信系统300。该方法主要包括以下步骤：
S701：PUSCH调度设备向终端发送资源单元RU类型指示信息。
其中，所述PUSCH调度设备为网络侧设备或终端。当所述PUSCH调度设备为网络侧设备时，所述PUSCH调度设备可以通过MPDCCH发送所述RU类型指示信息，或者通过 高层信令发送所述RU类型指示信息。当所述PUSCH调度设备为终端时，所述PUSCH调度设备可以通过MPDCCH发送所述。
具体实施中，不同资源单元类型可以用资源单元在时域上占用的子帧个数(或者在时域上占用的时隙个数)和该资源单元在频域上占用的子载波个数表征。
相应地，所述终端接收所述资源单元RU类型指示信息。需要说明的是，当所述PUSCH调度设备为终端时，接收所述RU类型指示信息的终端为能够与该终端通信的其他终端。
S702：所述终端根据所述RU类型指示信息，确定承载物理上行共享信道PUSCH的目标资源单元RU的类型。其中，所述目标RU类型对应的资源单元时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12。
具体实施中，当所述终端中配置有上下行子帧配置方式和资源单元类型的映射关系，所述终端可以通过以下但不限于以下两种方式确定所述目标RU类型：
方式A：若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式，所述终端将所述映射关系中所述目标上下行子帧配置方式对应的资源单元类型，确定为所述目标RU类型。
方式B：若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息；
所述终端根据所述目标上下行子帧配置方式和所述映射关系，确定所述目标上下行子帧配置方式对应的资源单元类型，将所述目标上下行子帧配置方式对应的资源单元类型中所述目标资源单元类型指示信息所指示的资源单元类型，确定为所述目标RU类型。
其中，所述目标资源单元类型指示信息可以为所述目标资源单元类型的标识。例如，所述映射关系中包括k种资源单元类型，所述k种资源单元类型的编号分别为1,2...k，所述目标资源单元类型指示信息可以为目标资源单元类型对应的编号。又如，所述映射关系中所述目标上下行子帧配置方式对应2种资源单元类型，可以用“0”表示所述目标上下行子帧配置方式对应的第一种资源单元类型，用“1”表示所述目标上下行子帧配置方式对应的第二种资源单元类型，此时所述目标资源单元类型指示信息为“0”或“1”。
具体实施中，所述上下行子帧配置方式和资源单元类型的映射关系满足如下表格：
Figure PCTCN2018076781-appb-000008
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
针对所述映射关系中的任意一种上下行配置方式对应的资源单元类型，该资源单元类型对应的资源单元映射到该上下行配置方式对应的系统帧上时，该上下行配置方式对应系 统帧中所有的上行子帧包括在一个或多个该上下行配置方式对应的资源单元中，且每个该上下行配置方式对应的资源单元中包含的子帧连续，例如图2所示的资源单元与系统帧的映射关系，使得所述终端能够有效利用与所述PUSCH调度设备约定的上下行配置方式中的上行子帧，以资源单元为资源分配粒度传输PUSCH。
实施中，为了减少TDD模式下PUSCH以资源单元为资源分配粒度进行传输对通信息系统架构的影响，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数，以使M×N尽量接近12。并且，相对于现有技术中以RB(在频域上占用12个子载波)为资源分配粒度传输PUSCH，所述终端以时域上占用的子帧个数M和在频域上占用的子载波个数N满足|M×N-12|≤a的资源单元传输PUSCH时，PUSCH占用的子载波个数较少，进而可以增加所述终端在每个子载波上的发射功率。
S703：所述终端根据所述目标RU类型，发送所述PUSCH。
具体实施中，所述目标RU类型对应的资源单元的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧，使得目标RU类型对应的资源单元可以映射到时域上连续的子帧，进而使得所述终端可以在所述时域上连续的子帧上传输PUSCH，从而可以保证信道估计的准确性。
通过上述方法，所述终端接收资源单元RU类型指示信息，根据所述资源单元RU类型指示信息确定目标RU类型，根据所述目标RU类型发送所述PUSCH，其中，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12，使得所述终端通过所述目标RU类型对应的RU映射到系统帧的一个上行子帧或时域上连续的多个上行子帧，发送所述PUSCH，能够解决资源单元包含的子帧不连续导致的信道估计结果不准确的问题。
基于以上实施例，本申请实施例提供了一种通信设备，所述通信设备用于实现如图4所示的PUSCH传输方法，参阅图8所示。所述通信设备800中包括：接收单元801、处理单元802和发送单元803。
所述接收单元801，用于接收机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息。
所述处理单元802，用于根据所述MPDCCH的重复发送次数确定第一子帧的时域位置，以及根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置；所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
所述发送单元803，用于根据所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。
可选地，所述定时指示信息中包括第一位置偏移信息，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
所述处理单元802在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置确定所述第三子帧的时域位 置；根据所述第一位置偏移信息和所述第三子帧的时域位置确定所述第二子帧的时域位置。
可选地，所述定时指示信息中包含指示第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
所述处理单元802在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第二位置偏移信息，确定所述第二子帧的时域位置。
可选地，所述定时指示信息用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量；
所述处理单元802在根据所述第一子帧的时域位置和所述定时指示信息确定所述第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第一映射关系，确定所述第二子帧的时域位置。
可选地，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
可选地，所述发送单元803，还用于发送包含MPDCCH重复发送次数以及所述定时指示信息的MPDCCH。
可选地，所述通信设备以及PUSCH调度设备中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系，所述PUSCH调度设备为发送所述MPDCCH的设备；
当所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
当所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述通信设备的一种资源单元。
可选地，所述第二映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元
0 第一资源单元和/或第二资源单元
1 第一资源单元和/或第三资源单元
2 第一资源单元
3 第一资源单元和/或第二资源单元
4 第一资源单元和/或第二资源单元
5 第一资源单元
6 第一资源单元
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
可选地，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例提供了一种通信设备，所述通信设备用于实现如图4所示的PUSCH发送方法，具有如图8所示的通信设备800的功能。参阅图9所示，所述通信设备900包括：收发器901和处理器902，收发器901和处理器902之间相互连接。
所述收发器901，用于接收机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息。
所述处理器902，用于所述MPDCCH的重复发送次数确定第一子帧的时域位置；根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置；以及根据所述第二子帧的时域位置，控制所述收发器901在所述第二子帧上发送所述MPDCCH对应的PUSCH；其中，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
所述收发器901，还用于在所述第二子帧上发送所述MPDCCH对应的PUSCH。
可选地，所述处理器902可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器902还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
可选地，所述处理器902与收发器901可以通过总线903相互连接。所述总线903可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线903可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选地，所述定时指示信息中包括第一位置偏移信息，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
所述处理器902在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置确定所述第三子帧的时域位置；根据所述第一位置偏移信息和所述第三子帧的时域位置确定所述第二子帧的时域位置。
可选地，所述定时指示信息中包含指示第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
所述处理器902在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第二位置偏移信息，确定所述第二子帧的时域位置。
可选地，所述通信设备还包括存储器904，用于保存第一映射关系，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量；
若所述定时指示信息用于指示所述通信设备根据第一映射关系确定所述第二子帧的时域位置，所述处理器902在根据所述第一子帧的时域位置和所述定时指示信息确定所述第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第一映射关系，确定所述第二子帧的时域位置。
可选地，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
可选地，所述存储器904还用于存储第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系；
当所述第二映射关系中所述通信设备与PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应的资源单元，所述PUSCH调度设备为发送所述MPDCCH的设备；
当所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述通信设备的一种资源单元。
可选地，所述存储器904可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；所述存储器904也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory，也称闪存)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；所述存储器904还可以包括上述种类的存储器的组合。
可选地，所述存储器904可能包含RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
可选地，所述第二映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元
0 第一资源单元和/或第二资源单元
1 第一资源单元和/或第三资源单元
2 第一资源单元
3 第一资源单元和/或第二资源单元
4 第一资源单元和/或第二资源单元
5 第一资源单元
6 第一资源单元
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
可选地，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
本申请实施例提供了一种终端，所述终端可以根据接收到的包含MPDCCH重复发送次数以及定时指示信息的MPDCCH，确定所述MPDCCH对应的PUSCH的起始子帧的时域位置，使得所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，进而使得所述终端能够充分利用所述目标RU所占用的子帧传输所述MPDCCH对应的PUSCH，从而可以保证所述MPDCCH对应的PUSCH上承载的数据的传输质量。
基于以上实施例，本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备用于实现如图4所示的PUSCH传输方法，参阅图10所示，所述PUSCH调度设备1000中包括：发送单元1001和处理单元1002。
所述发送单元1001，用于发送机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
所述处理单元1002，用于控制所述发送单元1001发送所述MPDCCH。
可选地，所述PUSCH调度设备以及接收所述MPDCCH的终端中配置有第一映射关系；其中，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
所述定时指示信息用于指示所述终端根据所述第一映射关系确定所述第二子帧的时域位置。
可选地，所述定时指示信息为第一位置偏移信息，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
所述处理单元1002在所述发送单元1001发送所述MPDCCH之前，还用于：根据所述MPDCCH的重复发送次数确定所述第一子帧的时域位置；根据所述第一子帧的时域位置确定所述第三子帧的时域位置；根据所述第二子帧的时域位置以及所述第三子帧的时域位置，确定所述第一位置偏移信息。
可选地，所述定时指示信息中包含第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
所述发送单元1001发送所述MPDCCH之前，所述处理单元1002还用于：根据所述MPDCCH的重复发送次数确定所述第一子帧的时域位置；根据所述第二子帧的时域位置以及所述第一子帧的时域位置，确定所述第二位置偏移信息。
可选地，所述PUSCH调度设备1000还包括接收单元1003，用于接收所述MPDCCH对应的PUSCH。
可选地，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
可选地，所述PUSCH调度设备以及接收所述MPDCCH的终端中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系；
当所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
当所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给接收所述MPDCCH的终端的一种资源单元。
可选地，所述第二映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元
0 第一资源单元和/或第二资源单元
1 第一资源单元和/或第三资源单元
2 第一资源单元
3 第一资源单元和/或第二资源单元
4 第一资源单元和/或第二资源单元
5 第一资源单元
6 第一资源单元
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
可选地，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
基于以上实施例，本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备用于实现如图4所示的PUSCH发送方法，具有如图10所示的PUSCH调度设备1100的功能。参阅图11所示，所述PUSCH调度设备1100包括：收发器1101和处理器1102，收发器1101和处理器1102之间相互连接。
所述收发器1101，用于发送机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
所述处理器1102，用于控制所述收发器1101发送所述MPDCCH。
可选地，所述处理器1102可以是CPU，NP或者CPU和NP的组合。所述处理器1102还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
可选地，所述处理器1102与收发器1101可以通过总线1103相互连接。所述总线1103可以是PCI总线或EISA总线等。所述总线1103可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选地，所述PUSCH调度设备1100还包括：存储器1104，用于保存第一映射关系，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
所述定时指示信息用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置。
可选地，所述存储器1104可以包括易失性存储器，例如RAM；所述存储器1104也可以包括非易失性存储器，例如快闪存储器，HDD或SSD；所述存储器1104还可以包括上述种类的存储器的组合。
可选地，所述存储器1104可能包含RAM，也可能还包括非易失性存储器，例如至少一个磁盘存储器。
可选地，所述定时指示信息中包括第一位置偏移信息，其中，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
所述处理器1102在所述收发器1101发送所述MPDCCH之前，还用于：根据所述MPDCCH的重复发送次数确定所述第一子帧的位置；根据所述第一子帧的时域位置，确定第三子帧的时域位置；根据所述第二子帧的时域位置以及所述第一子帧的时域位置，确定所述第一位置偏移信息；
可选地，所述定时指示信息为第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
所述处理器1102在所述收发器1101发送所述MPDCCH之前，还用于：
若根据所述MPDCCH的重复发送次数确定所述第一子帧的位置；根据所述第二子帧的时域位置以及所述第一子帧的时域位置，确定所述第二位置偏移信息。
可选地，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
可选地，存储器1104还用于：保存第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系；
当所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
当所述第二映射关系中接收所述MPDCCH的终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给接收所述MPDCCH的终端的一种资源单元。
可选地，所述收发器1101还用于接收所述MPDCCH对应的PUSCH。
可选地，所述第二映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元
0 第一资源单元和/或第二资源单元
1 第一资源单元和/或第三资源单元
2 第一资源单元
3 第一资源单元和/或第二资源单元
4 第一资源单元和/或第二资源单元
5 第一资源单元
6 第一资源单元
其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
可选地，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备可以向终端发送包含MPDCCH重复发送次数以及定时指示信息的MPDCCH，使得终端能够根据所述MPDCCH确定所述MPDCCH对应的PUSCH的起始子帧的时域位置，使得所述MPDCCH对应的PUSCH的起始子帧的时域位置与目标RU在时域上占用的首个子帧的时域位置相同，进而使得所述终端能够充分利用所述目标RU所占用的子帧传输所述MPDCCH对应的PUSCH，从而可以保证所述MPDCCH对应的PUSCH上承载的数据的传输质量。
基于以上实施例，本申请实施例提供了一种通信设备，所述终端用于实现如图7所示的PUSCH传输方法，参阅图12所示，所述通信设备1200中包括：接收单元1201、处理单元1202和发送单元1203。
所述接收单元1201，用于接收资源单元类型指示信息。
所述处理单元1202，用于根据所述资源单元类型指示信息，确定承载物理上行共享信道PUSCH的目标资源单元RU的类型，其中，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12。
所述发送单元1203，用于根据所述目标RU类型，发送所述PUSCH。
可选地，所述终端中配置有上下行子帧配置方式和资源单元类型的映射关系；
若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式；
所述处理单元1202在根据所述资源单元类型指示信息，确定目标资源单元RU类型时，具体用于：将所述映射关系中所述目标上下行子帧配置方式对应的资源单元类型，确定为所述目标RU类型。
可选地，若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息；
所述处理单元1202在根据所述资源单元类型指示信息，确定目标资源单元RU类型时，具体用于：根据所述目标上下行子帧配置方式和所述映射关系，确定所述目标上下行子帧配置方式对应的RU类型；端将所述目标上下行子帧配置方式对应的RU类型中所述目标资源单元类型指示信息所指示的RU类型，确定为所述目标RU类型。
可选地，所述映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元类型
0 第一RU类型和/或第二RU类型
1 第一RU类型和/或第三RU类型
2 第一RU类型
3 第一RU类型和/或第二RU类型
4 第一资RU类型和/或第二RU类型
5 第一RU类型
6 第一RU类型
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
可选地，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N为正整数，a为大于或等于0的整数。
可选地，所述目标RU类型对应的RU的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧。
基于以上实施例，本申请实施例提供了一种通信设备，所述通信设备用于实现如图7所示的PUSCH发送方法，具有如图12所示的通信设备1200的功能。参阅图13所示，所述通信设备1300包括：收发器1301和处理器1302，收发器1301和处理器1302之间相互连接。
所述收发器1301，用于在所述处理器1302的控制下接收资源单元类型指示信息以及发送PUSCH。
所述处理器1302，用于根据所述资源单元类型指示信息，确定承载物理上行共享信道PUSCH的目标资源单元RU的类型，以及根据所述目标RU类型，控制所述收发器1301发送所述PUSCH；其中，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于12。
可选地，所述处理器1302可以是CPU，NP或者CPU和NP的组合。所述处理器1302还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
可选地，所述处理器1302与收发器1301可以通过总线1303相互连接。所述总线1303可以是PCI总线或EISA总线等。所述总线1303可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选地，所述通信设备还包括处理器1304，用于保存预先配置的上下行子帧配置方式和资源单元类型的映射关系；若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式；
所述处理器1302在根据所述资源单元类型指示信息，确定目标资源单元RU类型时，具体用于：将所述映射关系中所述目标上下行子帧配置方式对应的资源单元类型，确定为所述目标RU类型。
可选地，所述存储器1304可以包括易失性存储器，例如RAM；所述存储器1304也可以包括非易失性存储器，例如快闪存储器，HDD或SSD；所述存储器1304还可以包括上述种类的存储器的组合。
可选地，所述存储器1304可能包含RAM，也可能还包括非易失性存储器，例如至少 一个磁盘存储器。
可选地，若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息；
所述处理器1302在根据所述资源单元类型指示信息，确定目标资源单元RU类型时，具体用于：根据所述目标上下行子帧配置方式和所述映射关系，确定所述目标上下行子帧配置方式对应的RU类型；将所述目标上下行子帧配置方式对应的RU类型中所述目标资源单元类型指示信息所指示的RU类型，确定为所述目标RU类型。
可选地，所述映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元类型
0 第一RU类型和/或第二RU类型
1 第一RU类型和/或第三RU类型
2 第一RU类型
3 第一RU类型和/或第二RU类型
4 第一资RU类型和/或第二RU类型
5 第一RU类型
6 第一RU类型
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
可选地，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N为正整数，a为大于或等于0的整数。
可选地，所述目标RU类型对应的RU的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧。
本申请实施例提供了一种通信设备，所述终端可以根据接收到的资源单元类型指示信息，确定目标资源单元类型，通过所述目标RU类型对应的RU映射到系统帧的一个上行子帧或时域上连续的多个上行子帧，发送所述PUSCH，能够解决资源单元包含的子帧不连续导致的信道估计结果不准确的问题。
基于以上实施例，本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备用于实现如图7所示的PUSCH传输方法，参阅图14所示，所述PUSCH调度设备1400中包括：发送单元1401和处理单元1402。
所述发送单元1401，用于发送资源单元类型指示信息；其中，所述资源单元类型指示信息用于确定承载物理上行共享信道PUSCH的目标资源单元RU的类型，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于1。
所述处理单元1402，用于控制所述发送单元1401发送所述资源单元类型指示信息。
所述可选地，所述PUSCH调度设备1400还包括接收单元1403，用于接收所述PUSCH。
可选地，所述PUSCH调度设备以及接收所述资源单元类型指示信息的终端中配置有上下行子帧配置方式和资源单元类型的映射关系；
若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式。
可选地，若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息。
可选地，所述映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元类型
0 第一RU类型和/或第二RU类型
1 第一RU类型和/或第三RU类型
2 第一RU类型
3 第一RU类型和/或第二RU类型
4 第一RU类型和/或第二RU类型
5 第一RU类型
6 第一RU类型
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
可选地，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N为正整数，a为大于或等于0的整数。
可选地，所述目标RU类型对应的RU的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧。
基于以上实施例，本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备用于实现如图7所示的PUSCH发送方法，具有如图14所示的PUSCH调度设备1400的功能。参阅图15所示，所述PUSCH调度设备1500包括：收发器1501和处理器1502，收发器1501和处理器1502之间相互连接。
所述收发器1501，用于发送资源单元类型指示信息；所述资源单元类型指示信息用于确定承载物理上行共享信道PUSCH的目标资源单元RU的类型，所述目标RU类型对应的RU时域上包含一个上行子帧或者时域上连续的多个上行子帧，且所述目标RU类型对应的资源单元在频域上占用的子载波个数小于或等于1。
所述处理器1502，用于控制所述收发器1501发送所述资源单元类型指示信息。
可选地，所述处理器1502可以是CPU，NP或者CPU和NP的组合。所述处理器1502还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
可选地，所述处理器1502与收发器1501可以通过总线1503相互连接。所述总线1503可以是PCI总线或EISA总线等。所述总线1503可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选地，所述PUSCH调度设备还包括存储器1504，用于保存预先配置的上下行子帧配置方式和资源单元类型的映射关系；
若所述映射关系中上下行配置方式与资源单元类型一一对应，所述资源单元类型指示信息包含目标上下行子帧配置方式。
可选地，所述存储器1504可以包括易失性存储器，例如RAM；所述存储器1504也可以包括非易失性存储器，例如快闪存储器，HDD或SSD；所述存储器1104还可以包括 上述种类的存储器的组合。
可选地，所述存储器1504可能包含RAM，也可能还包括非易失性存储器，例如至少一个磁盘存储器。
可选地，收发器还用于接收所述PUSCH。
可选地，若所述映射关系中任意一个上下行配置方式对应多个资源单元类型，所述资源单元类型指示信息中包含目标上下行子帧配置方式和目标资源单元类型指示信息。
可选地，所述映射关系满足如下表格：
时分双工TDD上下行配置方式 资源单元类型
0 第一RU类型和/或第二RU类型
1 第一RU类型和/或第三RU类型
2 第一RU类型
3 第一RU类型和/或第二RU类型
4 第一RU类型和/或第二RU类型
5 第一RU类型
6 第一RU类型
其中，所述第一RU类型对应的RU在时域上占用1个子帧，所述第二RU类型对应的RU在时域上占用3个子帧，所述第三RU类型对应的RU在时域上占用2个子帧。
可选地，所述目标RU类型对应的RU在时域上占用的子帧个数M和所述目标RU类型对应的RU在频域上占用的子载波个数N满足|M×N-12|≤a，M、N为正整数，a为大于或等于0的整数。
可选地，所述目标RU类型对应的RU的起始子帧为系统帧中的第一个上行子帧或者时隙中的第一个上行子帧。
本申请实施例提供了一种PUSCH调度设备，所述PUSCH调度设备可以向终端发送资源单元类型指示信息，使得所述终端根据接收到的资源单元类型指示信息，确定目标资源单元类型，通过所述目标RU类型对应的RU映射到系统帧的一个上行子帧或时域上连续的多个上行子帧，发送所述PUSCH，能够解决资源单元包含的子帧不连续导致的信道估计结果不准确的问题。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (32)

  1. 一种物理上行共享信道PUSCH传输方法，其特征在于，包括：
    终端接收机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息；
    所述终端根据所述MPDCCH的重复发送次数确定第一子帧的时域位置；所述第一子帧为承载所述MPDCCH的最后一个子帧；
    所述终端根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置；其中，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12；
    所述终端根据所述第二子帧的时域位置，在所述第二子帧上发送所述MPDCCH对应的PUSCH。
  2. 如权利要求1所述的方法，其特征在于，所述定时指示信息中包括第一位置偏移信息，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
    所述终端根据所述定时指示信息所述第一子帧的时域位置，确定第二子帧的时域位置，包括：
    所述终端根据所述第一子帧的时域位置确定所述第三子帧的时域位置；
    所述终端根据所述第一位置偏移信息和所述第三子帧的时域位置确定所述第二子帧的时域位置。
  3. 如权利要求1所述的方法，其特征在于，所述定时指示信息中包含指示第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
    所述终端根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置，包括：
    所述终端根据所述第一子帧的时域位置和所述第二位置偏移信息，确定所述第二子帧的时域位置。
  4. 如权利要求1所述的方法，其特征在于，所述定时指示信息用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量；
    所述终端根据所述第一子帧的时域位置和所述定时指示信息确定所述第二子帧的时域位置，包括：
    所述终端根据所述第一子帧的时域位置和所述第一映射关系，确定所述第二子帧的时域位置。
  5. 如权利要求1-4任意一项所述的方法，其特征在于，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
  6. 如权利要求1-5任意一项所述的方法，其特征在于，所述方法还包括：所述终端以 及PUSCH调度设备中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系，所述PUSCH调度设备为发送所述MPDCCH的设备；
    当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
    当所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述终端的一种资源单元。
  7. 如权利要求6所述的方法，其特征在于，所述第二映射关系满足如下表格：
    时分双工TDD上下行配置方式 资源单元 0 第一资源单元和/或第二资源单元 1 第一资源单元和/或第三资源单元 2 第一资源单元 3 第一资源单元和/或第二资源单元 4 第一资源单元和/或第二资源单元 5 第一资源单元 6 第一资源单元
    其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
  8. 如权利要求1-7任意一项所述的方法，其特征在于，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
  9. 一种物理上行共享信道PUSCH的传输方法，其特征在于，包括：
    物理上行共享信道PUSCH调度设备发送机器物理下行控制信道MPDCCH；
    其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12。
  10. 如权利要求9所述的方法，其特征在于，还包括：所述PUSCH调度设备以及接收所述MPDCCH的终端中配置有第一映射关系；其中，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述定时指示信息用于指示所述终端根据所述第一映射关系确定所述第二子帧的时域位置。
  11. 如权利要求9所述的方法，其特征在于，所述定时指示信息为第一位置偏移信息，所述第一位置偏移信息指示第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为PUSCH的资源分配粒度为资源块RB时根据第一子帧的时域位置确定的发送PUSCH的起始子帧，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述PUSCH调度设备发送所述MPDCCH之前，还包括：
    所述PUSCH调度设备根据所述MPDCCH的重复发送次数，确定所述第一子帧的时域位置；
    所述PUSCH调度设备根据所述第一子帧的时域位置，确定所述第三子帧的时域位置；
    所述PUSCH调度设备根据所述第三子帧的时域位置以及所述第二子帧的时域位置，确定所述第一位置偏移信息。
  12. 如权利要求9所述的方法，其特征在于，所述定时指示信息为第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述PUSCH调度设备发送所述MPDCCH之前，还包括：
    所述PUSCH调度设备根据所述MPDCCH的重复发送次数，确定所述第一子帧的时域位置；
    所述PUSCH调度设备根据所述第二子帧的时域位置以及所述第一子帧的时域位置，确定所述第二位置偏移信息。
  13. 如权利要求9-12任意一项所述的方法，其特征在于，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
  14. 如权利要求9-13任意一项所述的方法，其特征在于，还包括：所述PUSCH调度设备以及接收所述MPDCCH的终端中配置有第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系，所述PUSCH调度设备为发送所述MPDCCH的设备；
    当所述第二映射关系中所述PUSCH调度设备以及接收所述MPDCCH的终端约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述终端与所述PUSCH调度设备约定的上下行配置方式对应的资源单元；
    当所述第二映射关系中所述PUSCH调度设备以及接收所述MPDCCH的终端约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给接收所述MPDCCH的终端的一种资源单元。
  15. 如权利要求14所述的方法，其特征在于，所述第二映射关系满足如下表格：
    时分双工TDD上下行配置方式 资源单元 0 第一资源单元和/或第二资源单元 1 第一资源单元和/或第三资源单元 2 第一资源单元 3 第一资源单元和/或第二资源单元 4 第一资源单元和/或第二资源单元 5 第一资源单元 6 第一资源单元
    其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
  16. 如权利要求9-15任意一项所述的方法，其特征在于，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
  17. 一种通信设备，其特征在于，包括：收发器和处理器；
    所述收发器，用于在所述处理器的控制下收机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息；
    所述处理器，用于根据所述MPDCCH的重复发送次数确定第一子帧的时域位置，根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置，以及根据所述第二子帧的时域位置，控制所述收发器在所述第二子帧上发送所述MPDCCH对应的PUSCH；其中，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12；
    所述收发器还用于：在所述第二子帧上发送所述MPDCCH对应的PUSCH。
  18. 如权利要求17所述的设备，其特征在于，所述定时指示信息中包括第一位置偏移信息，所述第一位置偏移信息指示所述第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据所述第一子帧的时域位置确定的发送PUSCH的起始子帧；
    所述处理器在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：
    根据所述第一子帧的时域位置确定所述第三子帧的时域位置；
    根据所述第一位置偏移信息和所述第三子帧的时域位置，确定所述第二子帧的时域位置。
  19. 如权利要求17所述的设备，其特征在于，所述定时指示信息中包含指示第二位置偏移信息，所述第二位置偏移信息指示所述第二子帧的时域位置相对于与所述第一子帧的时域位置的偏移量；
    所述处理器在根据所述定时指示信息以及所述第一子帧的时域位置，确定第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第二位置偏移信息，确定所述第二子帧的时域位置。
  20. 如权利要求17所述的设备，其特征在于，所述通信设备还包括：存储器，用于保存第一映射关系，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量；
    若所述定时指示信息用于指示所述通信设备根据第一映射关系确定所述第二子帧的时域位置，所述处理器在根据所述第一子帧的时域位置和所述定时指示信息确定所述第二子帧的时域位置时，具体用于：根据所述第一子帧的时域位置和所述第一映射关系，确定所述第二子帧的时域位置。
  21. 如权利要求17-20任意一项所述的设备，其特征在于，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
  22. 如权利要求17-21任意一项所述的设备，其特征在于，还包括：存储器，用于保存第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系；
    当所述第二映射关系中所述通信设备与PUSCH调度设备约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述通信设备与PUSCH设备约定的上下行配置方式对应的资源单元，所述PUSCH调度设备为发送所述MPDCCH的设 备；
    当所述第二映射关系中所述通信设备与所述PUSCH调度设备约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给所述通信设备的一种资源单元。
  23. 如权利要求22所述的设备，其特征在于，所述第二映射关系满足如下表格：
    时分双工TDD上下行配置方式 资源单元 0 第一资源单元和/或第二资源单元 1 第一资源单元和/或第三资源单元 2 第一资源单元 3 第一资源单元和/或第二资源单元 4 第一资源单元和/或第二资源单元 5 第一资源单元 6 第一资源单元
    其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
  24. 如权利要求17-23任意一项所述的设备，其特征在于，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
  25. 一种物理上行共享信道PUSCH调度设备，其特征在于，包括：收发器和处理器；
    所述收发器，用于发送机器物理下行控制信道MPDCCH；其中，所述MPDCCH中包含所述MPDCCH的重复发送次数和定时指示信息，所述MPDCCH对应的PUSCH的资源分配粒度为目标资源单元，所述目标资源单元在频域上占用的子载波个数小于或等于12；
    所述处理器，用于控制所述收发器发送所述MPDCCH。
  26. 如权利要求25所述的设备，其特征在于，所述设备还包括：存储器，用于保存第一映射关系，所述第一映射关系为PUSCH的资源分配粒度为RU时第一子帧的时域位置与位置偏移量的对应关系，所述位置偏移量为第二子帧的时域位置相对于与第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述定时指示信息用于指示所述终端根据第一映射关系确定所述第二子帧的时域位置。
  27. 如权利要求25所述的设备，其特征在于，所述定时指示信息为第一位置偏移信息；其中，所述第一位置偏移信息指示第二子帧的时域位置相对于第三子帧的时域位置的偏移量，所述第三子帧为在PUSCH的资源分配粒度为资源块RB时，根据第一子帧的时域位置确定的发送PUSCH的起始子帧，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述处理器在所述收发器发送所述MPDCCH之前，还用于：
    根据所述MPDCCH的重复发送次数，确定第一子帧的时域位置；
    根据所述第一子帧的时域位置确定所述第三子帧的时域位置；
    根据所述第二子帧的时域位置以及所述第三子帧的时域位置确定所述第一位置偏移信息。
  28. 如权利要求25所述的设备，其特征在于，所述定时指示信息为第二位置偏移信息，所述第二位置偏移信息指示第二子帧的时域位置相对于与第一子帧的时域位置的偏移量，所述第一子帧为承载所述MPDCCH的最后一个子帧，所述第二子帧为承载所述MPDCCH对应的上行物理共享信道PUSCH的起始子帧；
    所述处理器在所述收发器发送所述MPDCCH之前，还用于：
    根据所述MPDCCH的重复发送次数，确定第一子帧的时域位置；
    根据所述第二子帧的时域位置以及所述第一子帧的时域位置确定所述第二位置偏移信息。
  29. 如权利要求25-28任意一项所述的设备，其特征在于，所述目标资源单元时域上包含一个上行子帧或者多个时域上连续的上行子帧。
  30. 如权利要求25-29任意一项所述的设备，其特征在于，还包括：存储器，用于保存第二映射关系，所述第二映射关系为上下行配置方式与资源单元的映射关系；
    当所述第二映射关系中所述PUSCH调度设备以及接收所述MPDCCH的终端约定的上下行配置方式对应一种资源单元时，所述目标资源单元为所述第二映射关系中所述终端与所述通信设备约定的上下行配置方式对应的资源单元；
    当所述第二映射关系中所述PUSCH调度设备终端以及接收所述MPDCCH的终端约定的上下行配置方式对应多种资源单元时，所述目标资源单元为所述PUSCH调度设备从所述多种资源单元中选择并通知给接收所述MPDCCH的终端的一种资源单元。
  31. 如权利要求30所述的设备，其特征在于，所述第二映射关系满足如下表格：
    时分双工TDD上下行配置方式 资源单元 0 第一资源单元和/或第二资源单元 1 第一资源单元和/或第三资源单元 2 第一资源单元 3 第一资源单元和/或第二资源单元 4 第一资源单元和/或第二资源单元 5 第一资源单元 6 第一资源单元
    其中，所述第一资源单元在时域上占用1个子帧，所述第二资源单元在时域上占用3个子帧，所述第三资源单元在时域上占用2个子帧。
  32. 如权利要求25-32任意一项所述的设备，其特征在于，所述目标资源单元在时域上占用的子帧个数M和所述目标资源单元在频域上占用的子载波个数N满足|M×N-12|≤a，M、N、为正整数，a为大于或等于0的整数。
PCT/CN2018/076781 2018-02-13 2018-02-13 一种物理上行共享信道pusch传输方法及装置 Ceased WO2019157685A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201880089003.3A CN111699744B (zh) 2018-02-13 2018-02-13 一种物理上行共享信道pusch传输方法及装置
EP18906282.1A EP3737190A4 (en) 2018-02-13 2018-02-13 TRANSMISSION METHOD AND DEVICE FOR PHYSICAL UPLINK SHARED CHANNEL (PUSCH)
PCT/CN2018/076781 WO2019157685A1 (zh) 2018-02-13 2018-02-13 一种物理上行共享信道pusch传输方法及装置
US16/990,581 US11528697B2 (en) 2018-02-13 2020-08-11 Physical uplink shared channel PUSCH transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/076781 WO2019157685A1 (zh) 2018-02-13 2018-02-13 一种物理上行共享信道pusch传输方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/990,581 Continuation US11528697B2 (en) 2018-02-13 2020-08-11 Physical uplink shared channel PUSCH transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2019157685A1 true WO2019157685A1 (zh) 2019-08-22

Family

ID=67620095

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076781 Ceased WO2019157685A1 (zh) 2018-02-13 2018-02-13 一种物理上行共享信道pusch传输方法及装置

Country Status (4)

Country Link
US (1) US11528697B2 (zh)
EP (1) EP3737190A4 (zh)
CN (1) CN111699744B (zh)
WO (1) WO2019157685A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12408166B2 (en) * 2020-09-30 2025-09-02 Beijing Xiaomi Mobile Software Co., Ltd. Channel transmission method and apparatus, and storage medium
US12538326B2 (en) 2020-09-09 2026-01-27 Beijing Xiaomi Mobile Software Co., Ltd. Downlink transmission method and device, and storage medium

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3843488B1 (en) * 2018-09-14 2026-01-21 Huawei Technologies Co., Ltd. Method for transmitting data, and method and device for sending control information
US11778607B2 (en) * 2021-04-01 2023-10-03 Nokia Technologies Oy Using relative transmission occasion delay indexing
CN116471688B (zh) * 2022-01-11 2025-12-23 大唐移动通信设备有限公司 一种时域资源确定方法、终端设备及存储介质
CN120786203A (zh) * 2024-04-02 2025-10-14 华为技术有限公司 点到多点的通信方法、装置、系统、设备和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017026548A1 (ja) * 2015-08-13 2017-02-16 株式会社Ｎｔｔドコモ ユーザ端末、無線基地局及び無線通信方法
CN106559188A (zh) * 2015-09-25 2017-04-05 华为技术有限公司 一种数据传输的方法及基站

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9485763B2 (en) * 2013-01-14 2016-11-01 Lg Electronics Inc. Method and user equipment for receiving downlink signal and method and base station for transmitting downlink signal
US10142064B2 (en) * 2013-09-17 2018-11-27 Intel IP Corporation Techniques and configurations associated with machine type communication in enhanced coverage mode
EP3913844B1 (en) * 2014-08-15 2025-05-14 InterDigital Patent Holdings, Inc. Method and apparatus for supporting uplink transmission and mbms for a wtru with reduced bandwidth
EP3525384B1 (en) * 2014-10-30 2021-03-24 LG Electronics Inc. Pucch transmission method by wireless device
CN106160978B (zh) * 2015-04-10 2021-05-07 夏普株式会社 物理下行控制信道的资源配置方法以及基站和用户设备
CN106160979B (zh) * 2015-04-10 2020-11-10 夏普株式会社 物理下行控制信道的传输方法以及基站和用户设备
RU2693269C1 (ru) * 2015-09-25 2019-07-01 Телефонактиеболагет Лм Эрикссон (Пабл) Способы, обеспечивающие предоставления восходящего канала, в том числе конфигурацию во временной области, и соответствующие беспроводные терминалы и сетевые узлы
WO2017121416A1 (zh) * 2016-01-11 2017-07-20 中兴通讯股份有限公司 上行控制信息的发送方法及装置
CN111510954B (zh) * 2016-02-05 2021-12-31 中兴通讯股份有限公司 调度定时间隔的确定方法及装置
US11259269B2 (en) * 2017-03-17 2022-02-22 Lg Electronics Inc. Method and base station for performing paging, and method and network entity for supporting paging
US11252696B2 (en) * 2017-09-12 2022-02-15 Lg Electronics Inc. Method and device for performing sidelink communication in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017026548A1 (ja) * 2015-08-13 2017-02-16 株式会社Ｎｔｔドコモ ユーザ端末、無線基地局及び無線通信方法
CN106559188A (zh) * 2015-09-25 2017-04-05 华为技术有限公司 一种数据传输的方法及基站

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Correction on higher layer parameter for eVoLTE", 3GPP TSG RAN WG1 MEETING#91, R1-1719507, 17 November 2017 (2017-11-17), XP051368814 *
See also references of EP3737190A4 *
ZTE: "Remaining issues on VoLTE enhancement for FeMTC", 3GPP TSG RAN WG1 MEETING#88, R1-1701905, 12 February 2017 (2017-02-12), XP051209068 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12538326B2 (en) 2020-09-09 2026-01-27 Beijing Xiaomi Mobile Software Co., Ltd. Downlink transmission method and device, and storage medium
US12408166B2 (en) * 2020-09-30 2025-09-02 Beijing Xiaomi Mobile Software Co., Ltd. Channel transmission method and apparatus, and storage medium

Also Published As

Publication number Publication date
US20200374846A1 (en) 2020-11-26
US11528697B2 (en) 2022-12-13
CN111699744B (zh) 2022-04-12
CN111699744A (zh) 2020-09-22
EP3737190A1 (en) 2020-11-11
EP3737190A4 (en) 2021-05-19

Similar Documents

Publication Publication Date Title
CN109152072B (zh) 一种调度信息传输方法及装置
CN109699054B (zh) 一种检测下行控制信息的方法、终端设备和网络设备
US11246142B2 (en) Control channel transmission method, network device, network controller, and terminal device
WO2020143750A1 (zh) 侧行参考信号的传输方法和通信装置
RU2693288C2 (ru) Первое устройство связи, второе устройство связи и осуществляемые на них способы отправки и приема, соответственно, указания типа подкадра
WO2019157685A1 (zh) 一种物理上行共享信道pusch传输方法及装置
EP3883320A1 (en) Feedback channel transmitting method, feedback channel receiving method, and apparatus
TW201826824A (zh) 上行傳輸方法、終端與網路設備
WO2017025066A1 (zh) 一种数据传输方法及装置
WO2020221326A1 (zh) 一种资源调度的方法及通信装置
WO2019141146A1 (zh) 一种波束配置方法和装置
CN112449425B (zh) 一种通信方法和装置
WO2016045564A1 (en) A method and device of resource allocations for scheduling assignments in device to device communications
WO2019029731A1 (zh) 一种资源配置方法及设备
WO2019047632A1 (zh) 用于传输下行数据的资源的确定和配置方法、终端和基站
WO2019051802A1 (zh) 传输数据的方法、网络设备和终端设备
WO2016138841A1 (zh) 数据传输的方法、反馈信息传输方法及相关设备
WO2020143689A1 (zh) 一种参考信号传输方法及装置
WO2017133479A1 (zh) 一种下行控制信息传输方法及装置
CN110971362B (zh) 一种发现参考信号发送方法及装置
CN112673655B (zh) 一种tdd系统中的资源分配方法和设备
TW201904322A (zh) 無線通信方法和設備
CN106982465B (zh) 一种无线帧的传输方法以及无线网络设备
CN107277920B (zh) 一种信息传输方法及装置
WO2019023912A1 (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: 18906282

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018906282

Country of ref document: EP

Effective date: 20200806

NENP Non-entry into the national phase

Ref country code: DE