WO2019024891A1 - Urllc中上行免授权传输的方法、用户侧设备和网络侧设备 - Google Patents

Urllc中上行免授权传输的方法、用户侧设备和网络侧设备 Download PDF

Info

Publication number
WO2019024891A1
WO2019024891A1 PCT/CN2018/098301 CN2018098301W WO2019024891A1 WO 2019024891 A1 WO2019024891 A1 WO 2019024891A1 CN 2018098301 W CN2018098301 W CN 2018098301W WO 2019024891 A1 WO2019024891 A1 WO 2019024891A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq process
data
urllc
time domain
domain resource
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/098301
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.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication 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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to EP18842295.0A priority Critical patent/EP3661290B1/en
Priority to US16/631,648 priority patent/US11357027B2/en
Priority to ES18842295T priority patent/ES2941834T3/es
Publication of WO2019024891A1 publication Critical patent/WO2019024891A1/zh
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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • 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
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • 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
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • 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
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • 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
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • 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
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present application relates to the field of communications, and in particular, to a method for uplink and unlicensed transmission in a URLLC, a user side device, and a network side device.
  • 5G 5th generation mobile networks
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra Reliable & Low Latency Communication
  • mMTC Massive Machine Type Communication
  • the 5G base station configures some resources or parameters. Once the user equipment (User Equipment, UE) arrives, the configured resources can be transmitted, saving the delay of the authorized scheduling. .
  • UE User Equipment
  • the configured resources can be transmitted, saving the delay of the authorized scheduling.
  • HARQ Hybrid Automatic Repeat Request
  • multiple Hybrid Automatic Repeat Request (HARQ) processes can be supported, but due to the randomness of the URLLC service arrival, the gNB cannot know which HARQ process the UE uses.
  • an uplink grant-free transmission method of a URLLC service is proposed, which is performed by a user-side device, and the method includes:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between a URLLC uplink transmission time domain resource and a HARQ process identifier;
  • the time domain resource transmits the data of the URLLC service by using the corresponding HARQ process in the available URLLC uplink transmission.
  • a user side device comprising:
  • the receiving unit receives the configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier;
  • the sending unit sends the data of the URLLC service by using the corresponding HARQ process in the available URLLC uplink transmission when the URLLC service arrives.
  • a user side device where the user side device includes:
  • a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the following operations:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier; when the URLLC service arrives, the available URLLC uplink transmission time domain resource usage corresponds to The HARQ process sends the data of the URLLC service.
  • a computer readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of applications, cause The electronic device performs the following operations:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier; when the URLLC service arrives, the available URLLC uplink transmission time domain resource usage corresponds to The HARQ process sends the data of the URLLC service.
  • an uplink grant-free transmission method in a URLLC is proposed, which is applied to a network side device, and the method includes:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between a URLLC uplink transmission time domain resource and a HARQ process identifier;
  • the data of the URLLC service is cached by using the corresponding HARQ process on the URLLC uplink transmission time domain resource of the data receiving the URLLC service.
  • a network side device comprising:
  • the sending unit sends a configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier;
  • the receiving unit when receiving the data of the URLLC service, caches the data of the URLLC service by using the corresponding HARQ process on the URLLC uplink transmission time domain resource of the data receiving the URLLC service.
  • a network side device where the network side device includes:
  • a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the following operations:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between a URLLC uplink transmission time domain resource and a HARQ process identifier;
  • the data of the URLLC service is cached by using the corresponding HARQ process on the URLLC uplink transmission time domain resource of the data receiving the URLLC service.
  • a computer readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of applications, cause The electronic device performs the following operations:
  • the configuration parameter includes first indication information, where the first indication information indicates a correspondence between a URLLC uplink transmission time domain resource and a HARQ process identifier;
  • the data of the URLLC service is cached by using the corresponding HARQ process on the URLLC uplink transmission time domain resource of the data receiving the URLLC service.
  • FIG. 1 is a flowchart of an uplink grant-free transmission method in a URLLC according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of correspondence between a time domain resource of a URLLC uplink transmission and a HARQ process according to an embodiment of the present application;
  • FIG. 3 is a schematic diagram of a method for uplink unlicensed transmission in a URLLC according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a method for uplink unlicensed transmission in a URLLC according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application
  • FIG. 7 is a flowchart of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application
  • FIG. 8 is a schematic structural diagram of a user side device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a user side device according to still another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network side device according to still another embodiment of the present application.
  • the embodiment of the present application provides an uplink grant-free transmission method, a user-side device, and a network-side device in a URLLC.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-advanced
  • NR New Radio
  • a user equipment which may also be called a mobile terminal (Mobile Terminal), a mobile user equipment, etc., may communicate with one or more core networks via a Radio Access Network (RAN).
  • the device may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket, handheld, computer built-in or in-vehicle mobile device that is connected to the wireless device.
  • Network exchange language and / or data.
  • the base station may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station (eNB or e-NodeB (Evolved Node B)) in LTE.
  • BTS Base Transceiver Station
  • NodeB base station
  • eNB evolved base station
  • gNB 5G base station
  • the present application is not limited, but for convenience of description, the following embodiments are described by taking gNB as an example.
  • FIG. 1 is a flowchart of an uplink grant-free transmission method in a URLLC according to an embodiment of the present application.
  • the method of Figure 1 is performed by a user side device.
  • the user side device may be a device such as a UE.
  • the method can include:
  • S101 Receive a configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between a URLLC uplink transmission time domain resource and a HARQ process identifier.
  • the correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier may be a pre-configured table.
  • the configuration parameter may specify that multiple URLLC uplink transmission time domain resources belong to one HARQ process. Wherein, the time domain resource is transmitted in each URLLC uplink, and information transmission can be performed once.
  • FIG. 2 is a schematic diagram of correspondence between a time domain resource of a URLLC uplink transmission and a HARQ process according to an embodiment of the present application.
  • one HARQ process corresponds to four URLLC uplink transmission time domain resources.
  • the HARQ process 1 corresponds to the URLLC uplink transmission time domain resource t1-t4
  • the HARQ process 2 corresponds to the URLLC uplink transmission time domain resource t5-t8
  • the HARQ process 3 corresponds to the URLLC uplink transmission time domain resource t9-t12. ,and many more.
  • the correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier may also be expressed in other manners, which is not limited in this embodiment of the present application.
  • the configuration parameter further includes second indication information, where the second indication information indicates the number of transmissions.
  • the number of times the same transport block (TB) is sent by one HARQ process is the number of transmissions of the TB.
  • this article uses the URLLC corresponding to a HARQ process to transmit the number of time domain resources, which is the number of transmissions. For example, in the application scenario shown in FIG. 2, the number of transmissions is four.
  • the configuration parameter further includes fourth indication information.
  • the fourth indication information indicates a transmission order of the redundancy version and the redundancy version that are sent each time the data of the URLLC service is transmitted in the number of transmissions.
  • the fourth indication information may indicate a total of four redundancy versions of the redundancy version Rv0-Rv3, and indicate that the transmission order is Rv0, Rv2, Rv3, and Rv1.
  • the fourth indication information indicates that the data of the URLLC service is used to transmit a redundant version of the time domain resource in the URLLC corresponding to the HARQ process.
  • the fourth indication information may indicate that the redundancy versions corresponding to t1, t2, t3, and t4 are Rv0, Rv2, Rv3, and Rv1, respectively.
  • the time domain resource transmits the data of the URLLC service by using the corresponding HARQ process in the available URLLC uplink transmission.
  • the network side device can know which HARQ process is used by the UE side. No. so that the UE side and the network side can maintain the same understanding of the HARQ process used to transmit the URLLC service.
  • the network side device when the mapping between the HARQ process and the time domain resource is configured, so that the user side device transmits the time domain resource to the network side device during the URLLC uplink transmission, the network side device can accurately obtain the HARQ used by the user side device to transmit. Process to ensure uplink and unlicensed transmission of URLLC services.
  • step S102 is specifically implemented to: when the URLLC service arrives, use the first URL LC to transmit the first HARQ process corresponding to the time domain resource on the first URLLC uplink transmission time domain resource that is available. Sending data of the first transport block, where the first transport block belongs to the data of the URLLC service;
  • the method further comprises:
  • the scheduling information is used to indicate that the data of the first transport block sent by the first HARQ process is retransmitted on the second URLLC uplink transmission time domain resource.
  • the recently available first URLLC uplink transmission time domain resource refers to the most recently available URLLC uplink transmission time domain resource after the current time of arrival of the URLLC service, or the next available URLLC after the current time of arrival of the URLLC service. Uplink transmission time domain resources.
  • the recently available first URLLC uplink transmission time domain resource mentioned below is similar to this and will not be described again.
  • the second URLLC uplink transmission time domain resource may be different from the uplink transmission time domain resource corresponding to the second HARQ process.
  • the data of the first transport block is sent by using the first HARQ process on the recently available first URLLC uplink transmission time domain resource, and then, if the network side device receives the first transmission according to the first transmission
  • the scheduling information sent after the block is retransmitted according to the scheduling information.
  • FIG. 3 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application.
  • the URLLC service arrives between time t2 and time t3, and the user side device, such as the UE, uses the most recent available time domain resource, ie, t3, to transmit a transport block (TB).
  • the TB belongs to the data of the URLLC service.
  • the time domain resources that the HARQ process 1 can use include t3 and t4, that is, the number of repeated transmissions is 2.
  • the reliability of the data of the URLLC service can be ensured according to the scheduling of the network side device. That is, after receiving the transport block, the network side device may send scheduling information to the user side device, instructing the user side device to send data of the same transport block on the time domain resource indicated by the scheduling information.
  • data for the same transport block generally refers to the same or a different redundancy version of the same transport block.
  • the scheduling information sent by the network side device may also carry the redundancy version of the identifier information.
  • the network side device may schedule the user side device to send a redundant version of the same transport block.
  • the network side device schedules the user side device to send multiple redundant versions of the same transport block in one scheduling.
  • the network side device sends the scheduling information to schedule the number of times that the UE side device sends the transport block, which may be equal to the number of transmissions indicated by the configuration parameter, or is not equal to the number of transmissions indicated by the configuration parameter.
  • step S102 is specifically implemented to: when the URLLC service arrives, use the first URLLC to uplink on the most recently available first URLLC uplink transmission time domain resource.
  • the first HARQ process corresponding to the transmission time domain resource sends the data of the first transport block, where the first transport block belongs to the data of the URLLC service, and the data sent by the first HARQ process further carries the third indication information, where the third indication information is used. Whether the first HARQ process indicating the data of the URLLC service is sent and the subsequent second HARQ process are used to transmit data of the same transport block.
  • the method further includes: when the third indication information is used to indicate that the first HARQ process and the second HARQ process are used to send the same transport block. And transmitting, by using the first HARQ process, the data of the first transport block, according to the remaining number of transmissions, on the URLLC uplink transmission time domain resource corresponding to the second HARQ process, where the remaining transmission times is the number of transmissions indicated by the second indication information minus use The number of times that the uplink transmission time domain resource corresponding to the first HARQ process transmits the first transport block.
  • FIG. 4 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application. Similar to FIG. 3, assuming that the URLLC service arrives between times t2 and t3, the user side device, such as the UE, etc., uses the most recent available time domain resource, ie, t3, to transmit the transport block. The TB belongs to the data of the URLLC service. At this time, the time domain resources that the HARQ process 1 can use include t3 and t4, that is, the number of repeated transmissions is 2.
  • the data sent by the HARQ process 1 may include, in addition to the data of the TB, an indication information, which is used to indicate the neighboring HARQ process after the HARQ process 1, that is, the HARQ process 2, and the HARQ process 1 Whether to send data of the same transport block.
  • an indication information which is used to indicate the neighboring HARQ process after the HARQ process 1, that is, the HARQ process 2, and the HARQ process 1 Whether to send data of the same transport block.
  • a Demodulation Reference Signal (DMRS) sequence or an Uplink Control Information may be used to carry the indication in an uplink transmission time domain resource for transmitting data.
  • the indication information may use 1 bit of DMRS or 1 bit of Uplink Control Information (UCI).
  • the user equipment may send the HARQ process 1 in the uplink transmission time domain resource corresponding to the HARQ process 2
  • the data of the transport block, the number of times the HARQ process 1 and the same transport block sent in the HARQ process 2 are equal to the number of transmissions. For example, in the scenario shown in FIG. 4, two uplink transmission time domain resources may be transmitted at t5 and t6 using HARQ process 1 to transmit other redundant versions of the same transport block.
  • the method further includes: when the third indication information is used to indicate that the first HARQ process and the second HARQ process are used to send the same transmission.
  • the data of the block is used, the data of the first transport block sent by the first HARQ process is used on all URLLC uplink transmission time domain resources corresponding to the second HARQ process.
  • FIG. 5 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application. Similar to FIG. 3, assuming that the URLLC service arrives between times t2 and t3, the user side device, such as the UE, etc., uses the most recent available time domain resource, ie, t3, to transmit the transport block. The TB belongs to the data of the URLLC service. At this time, the time domain resources that the HARQ process 1 can use include t3 and t4, that is, the number of repeated transmissions is 2.
  • the data sent by the HARQ process 1 may include an indication information indicating the adjacent HARQ process, that is, the HARQ process after the HARQ process 1, in addition to the data of the TB. 2. Whether the HARQ process 1 is used to transmit data of the same transport block.
  • the user side device may send the HARQ process on all corresponding uplink transmission time domain resources of the HARQ process 2. 1 The data of the transmitted block. For example, in the scenario shown in FIG. 5, the user side device may transmit the redundancy version of the same transport block using the HARQ process 1 for a total of four uplink transmission time domain resources at t5-t8.
  • the DMRS sequence or the UCI may also be used to carry an indication information, indicating whether the current HARQ process and the current HARQ process of the current HARQ process corresponding to the current uplink transmission time domain resource are used for sending. Data of the same transport block.
  • step S102 is specifically implemented to: when the URLLC service arrives, use the subsequent neighbor on the URLLC uplink transmission time domain resource corresponding to the subsequent HARQ process corresponding to the HARQ process at the current time.
  • the HARQ process sends the data of the URLLC service.
  • FIG. 6 is a schematic diagram of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application. Similar to Figure 3, it is assumed that the URLLC service arrives between times t2 and t3.
  • the user side device may send a transport block by using a subsequent HARQ process of the HARQ process corresponding to the URLLC service arrival time.
  • the user equipment can transmit all the redundancy versions of the transport block using the HARQ process 2 by transmitting four time uplink resources, that is, the configured number of transmissions, at t5-t8.
  • FIG. 7 is a flow chart of a method for uplink grant-free transmission in a URLLC according to an embodiment of the present application.
  • the method of Figure 7 is performed by a network side device. It should be understood that, in this embodiment of the present application, the network side device may be a device such as a base station.
  • the method includes:
  • S701 Send a configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier.
  • the configuration parameter further includes second indication information, where the second indication information indicates the number of transmissions.
  • the configuration parameter further includes fourth indication information.
  • the fourth indication information indicates a transmission order of the redundancy version and the redundancy version that are sent each time the data of the URLLC service is transmitted in the number of transmissions.
  • the fourth indication information indicates that the data of the URLLC service is used to transmit a redundant version of the time domain resource in the URLLC corresponding to the HARQ process.
  • the URL resource uplink data transmission time domain resource of the URL LC service receives the data of the URLLC service by using a corresponding HARQ process.
  • the network side device when the mapping between the HARQ process and the time domain resource is configured, so that the user side device transmits the time domain resource to the network side device during the URLLC uplink transmission, the network side device can accurately obtain the HARQ used by the user side device to transmit. Process to ensure uplink and unlicensed transmission of URLLC services.
  • the step S702 is specifically implemented to: when the data of the URLLC service to be received exists on the domain resource when the first URLLC uplink transmission is detected, use the first URLLC to transmit the first corresponding to the time domain resource.
  • the HARQ process caches the data of the first transport block received by the first URLLC uplink time domain resource, and the first transport block belongs to the data of the URLLC service.
  • the network block device detects a URLLC uplink transmission.
  • the HARQ process corresponding to the time domain resource of the URLLC uplink transmission may be used to cache the data of the transport block received by the URLLC uplink transmission time domain resource.
  • the method further includes: sending scheduling information, where the scheduling information is used to indicate that the user equipment retransmits the first time domain resource in the second URLLC uplink transmission.
  • the data of the first transport block buffered by the HARQ process is not correctly received.
  • a user side device such as a UE transmits a transport block using the HARQ process 1 on the uplink transmission time domain resources t3 and t4.
  • the network side device for example, the base station, and the like, may use the HARQ process 1 corresponding to the uplink transmission time domain resources t3 and t4 to buffer the data of the transport block after the uplink transmission time domain resources t3 and t4 detect that the data of the URLLC service arrives.
  • the network side device such as the base station, may send scheduling information to the user side device according to the uplink transmission time domain resource usage situation, where the scheduling information indicates that the user side device uploads data of the same transport block in a different uplink time domain resource than the configured uplink transmission time domain resource.
  • the network side device such as the base station uses the HARQ process 1 to buffer the redundancy version of the same transport block.
  • the number of times that the network side device sends the scheduling information to schedule the UE side device to perform the upload may be equal to the number of transmissions indicated by the configuration parameter, or is not equal to the number of transmissions indicated by the configuration parameter.
  • the network side device may use the first HARQ process to buffer the data of the first transport block received by the second URLLC uplink transmission time domain resource on the second URLLC uplink transmission time domain resource.
  • the data that is buffered by the first HARQ process further carries third indication information, where the third indication information is used to indicate whether the first HARQ process and the subsequent second HARQ process are used.
  • the data of the same transport block is cached.
  • step S702 is specifically implemented as:
  • the first HARQ process corresponding to the first URLLC uplink transmission time domain resource is used to buffer data of the first transport block received by the first URLLC uplink transmission time domain resource, where the first transport block belongs to the data of the URLLC service;
  • the data buffered by the first HARQ process further carries the third indication information, and the third indication information indicates that the first HARQ process and the second HARQ process are used to buffer data of the same transport block, all URLLCs corresponding to the second HARQ process
  • the data of the first transmission block is buffered by using the first HARQ process according to the remaining transmission times, and the remaining transmission times is the number of transmissions indicated by the second indication information minus the uplink transmission time domain corresponding to the first HARQ process. The number of times the first transport block of the resource was transmitted.
  • the network side device caches the data of the transport block by using the HARQ process 1 at t3 and t4, it can also determine that the HARQ process 2 and the HARQ process 1 are used to send the data of the same transport block according to the indication information carried in the buffered data, and then Two uplink transmission time domain resources, t5 and t6, use HARQ process 1 to buffer other redundant versions of the same transport block.
  • whether the current HARQ process and the current HARQ process are currently indicated by the current HARQ process corresponding to the current uplink transmission time domain resource may be indicated by the received DMRS sequence or the indication information carried in the UCI. Used to send data for the same transport block.
  • step S702 is specifically implemented as:
  • the first HARQ process corresponding to the first URLLC uplink transmission time domain resource is used to buffer data of the first transport block received by the first URLLC uplink transmission time domain resource, where the first transport block belongs to the data of the URLLC service;
  • the data buffered by the first HARQ process further carries the third indication information, and the third indication information indicates that the first HARQ process and the second HARQ process are used to buffer data of the same transport block, all URLLCs corresponding to the second HARQ process On the uplink transmission time domain resource, the data of the first transport block is buffered by using the second HARQ process.
  • the network side device caches the data of the transport block by using the HARQ process 1 at t3 and t4, it may also determine, according to the indication information carried in the buffered data, that the HARQ process 2 and the HARQ process 1 are used to send data of the same transport block, and T5-t8 A total of four uplink transmission time domain resources use HARQ process 1 to buffer the redundancy version of the same transport block.
  • whether the current HARQ process and the current HARQ process are currently indicated by the current HARQ process corresponding to the current uplink transmission time domain resource may be indicated by the received DMRS sequence or the indication information carried in the UCI. Used to send data for the same transport block.
  • FIG. 8 is a schematic structural diagram of a user side device 800 according to an embodiment of the present application. As shown in FIG. 8, the user side device may include:
  • the receiving unit 801 receives the configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier.
  • the sending unit 802 when the URLLC service arrives, transmits the time domain resource in the available URLLC uplink using the corresponding HARQ process, and sends the data of the URLLC service.
  • the network side device when the mapping between the HARQ process and the time domain resource is configured, so that the user side device transmits the time domain resource to the network side device during the URLLC uplink transmission, the network side device can accurately obtain the HARQ used by the user side device to transmit. Process to ensure uplink and unlicensed transmission of URLLC services.
  • the configuration parameter further includes second indication information, where the second indication information indicates the number of transmissions.
  • the configuration parameter further includes fourth indication information.
  • the fourth indication information indicates a sequence of sending the redundancy version and the redundancy version of the data of the URLLC service in the transmission times, or indicating that the data of the URLLC service is uplinked by the URLLC corresponding to the HARQ process. A redundant version of the domain resource.
  • the sending unit 802 is specifically configured to: when the URLLC service arrives, send the first transport block by using the first URL LC uplink transmission time domain corresponding to the first HARQ process on the recently available first URL LC uplink transmission time domain resource. Data, the first transport block belongs to the data of the URLLC service;
  • the receiving unit 801 further receives scheduling information, where the scheduling information is used to indicate that the data of the first transport block sent by the first HARQ process is retransmitted on the second URLLC uplink transmission time domain resource;
  • the sending unit 802 is further configured to: retransmit the data of the first transport block by using the first HARQ process according to the gNB scheduling on the second URLLC uplink transmission time domain resource.
  • the sending unit 802 is specifically configured to: when the URLLC service arrives, use the first URLLC to transmit the first corresponding to the time domain resource on the first available URLLC uplink transmission time domain resource.
  • the HARQ process sends the data of the first transport block, where the first transport block belongs to the data of the URLLC service, and the data sent by the first HARQ process further carries the third indication information, where the third indication information is used to indicate the data of the URLLC service. Whether the first HARQ process and the subsequent adjacent second HARQ process are used to transmit data of the same transport block.
  • the sending unit 802 is further configured to: when the third indication information is used to indicate that the first HARQ process and the second HARQ process are used to send data of the same transport block. And transmitting data of the first transport block by using the first HARQ process on all URLLC uplink transmission time domain resources corresponding to the second HARQ process.
  • the sending unit 802 is further configured to: when the third indication information is used to indicate that the first HARQ process and the second HARQ process are used to send the same transport block. And transmitting, by the second HARQ process, the data of the first transport block by using the second HARQ process, where the number of remaining transmissions is less than the number of transmissions indicated by the second indication information, on the URLLC uplink transmission time domain resource corresponding to the second HARQ process. The number of times the first transport block is transmitted by using the uplink transmission time domain resource corresponding to the first HARQ process.
  • the sending unit 802 is specifically configured to: when the URLLC service arrives, use the URLLC uplink transmission time domain resource corresponding to a subsequent adjacent HARQ process of the HARQ process corresponding to the current time.
  • the subsequent adjacent HARQ process sends the data of the URLLC service.
  • the user-side device 800 can also perform the method shown in FIG. 1 and implement the functions of the user-side device in the embodiment shown in FIG. 1.
  • the embodiments of the present application are not described herein again.
  • FIG. 9 is a schematic structural diagram of a user side device 900 according to still another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a user side device 900 according to an embodiment of the present application.
  • a schematic diagram of a physical device structure of the user side device 900 may be as shown in FIG. 9, and includes a processor 902, a memory 903, a transmitter 901, and a receiver 904.
  • transmitter 901 and receiver 904 can be coupled to antenna 905.
  • the memory 903 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 903 can include read only memory and random access memory and provides instructions and data to processor 902.
  • the memory 903 may include a high speed random access memory (RAM) memory, and may also include a non-volatile memory such as at least one disk memory.
  • RAM high speed random access memory
  • the processor 902 executes the program stored in the memory 903.
  • the processor 902 can perform the following methods through the receiver 904 and the transmitter 901:
  • the time domain resource transmits the data of the URLLC service by using the corresponding HARQ process in the available URLLC uplink transmission.
  • Processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 902 or an instruction in a form of software.
  • the processor 902 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., or a digital signal processor (DSP), dedicated.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 903, and the processor 902 reads the information in the memory 903 and completes the steps of the above method in combination with its hardware.
  • the user side device 900 can also perform the method shown in FIG. 1 and implement the functions of the user side device in the embodiment shown in FIG. 1.
  • the embodiments of the present application are not described herein again.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be configured to perform the method of the embodiment shown in FIG. 1 and specifically for performing the following operations:
  • the time domain resource transmits the data of the URLLC service by using the corresponding HARQ process in the available URLLC uplink transmission.
  • FIG. 10 is a schematic structural diagram of a network side device 1000 according to an embodiment of the present application. As shown in FIG. 10, the network side device 1000 may include:
  • the sending unit 1001 sends a configuration parameter, where the configuration parameter includes first indication information, where the first indication information indicates a correspondence between the URLLC uplink transmission time domain resource and the HARQ process identifier.
  • the receiving unit 1002 when receiving the data of the URLLC service, transmits the data of the URLLC service by using the corresponding HARQ process in the URL LC uplink transmission of the data of the URLLC service.
  • the network side device when the mapping between the HARQ process and the time domain resource is configured, so that the user side device transmits the time domain resource to the network side device during the URLLC uplink transmission, the network side device can accurately obtain the HARQ used by the user side device to transmit. Process to ensure uplink and unlicensed transmission of URLLC services.
  • the configuration parameter further includes second indication information, where the second indication information indicates the number of transmissions.
  • the configuration parameter further includes fourth indication information.
  • the fourth indication information indicates a sequence of sending the redundancy version and the redundancy version of the data of the URLLC service in the transmission times, or indicating that the data of the URLLC service is uplinked by the URLLC corresponding to the HARQ process. A redundant version of the domain resource.
  • the receiving unit 1002 is specifically configured to: when the data of the URLLC service to be received exists on the domain resource when the first URLLC uplink transmission is detected, use the first URLLC to transmit the time domain resource corresponding to the uplink
  • a HARQ process buffers data of the first transport block received by the first URLLC uplink time domain resource, and the first transport block belongs to data of the URLLC service.
  • the sending unit 1001 is further configured to send scheduling information, where the scheduling information is used to indicate that the user side device retransmits the data of the first transport block buffered by the first HARQ process in the second URLLC uplink transmission time domain resource.
  • the receiving unit 1002 is specifically configured to:
  • the first HARQ process corresponding to the first URLLC uplink transmission time domain resource is used to cache data of the first transport block received by the first URLLC uplink transmission time domain resource, where the first transport block belongs to the data of the URLLC service, and the first HARQ process
  • the buffered data further carries third indication information, where the third indication information is used to indicate whether the first HARQ process and the subsequent second HARQ process are used to buffer data of the same transport block.
  • the receiving unit 1002 is further specifically configured to:
  • the first HARQ process caches the first on all URLLC uplink transmission time domain resources corresponding to the second HARQ process. Transfer block data.
  • the receiving unit 1002 is further specifically configured to:
  • the first HARQ is used according to the remaining transmission times on all URLLC uplink transmission time domain resources corresponding to the second HARQ process.
  • the process buffers the data of the first transport block, where the number of remaining transmissions is the number of transmissions indicated by the second indication information minus the number of times the first transport block is transmitted by using the uplink transmission time domain resource corresponding to the first HARQ process.
  • the network side device 1000 can also perform the method shown in FIG. 7 and implement the functions of the network side device in the embodiment shown in FIG. 7.
  • the embodiments of the present application are not described herein again.
  • FIG. 11 is a schematic structural diagram of a network side device 1100 according to still another embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network side device 1100 according to an embodiment of the present application.
  • a schematic diagram of a physical device structure of the network side device 1100 may be as shown in FIG. 11, and includes a processor 1102, a memory 1103, a transmitter 1101, and a receiver 1104.
  • transmitter 1101 and receiver 1104 can be coupled to antenna 1105.
  • the memory 1103 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1103 can include read only memory and random access memory and provides instructions and data to processor 1102.
  • the memory 1103 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1102 executes the program stored in the memory 1103.
  • the processor 1102 can perform the following methods through the receiver 1104 and the transmitter 1101:
  • the URL LC uplink transmission time domain resource When receiving the data of the URLLC service, the URL LC uplink transmission time domain resource receives the data of the URLLC service using the corresponding HARQ process.
  • Processor 1102 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1102 or an instruction in a form of software.
  • the processor 1102 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; or may be a digital signal processor (DSP) or an application specific integrated circuit (ASIC). ), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1103, and the processor 1102 reads the information in the memory 1103 and completes the steps of the above method in combination with its hardware.
  • the network side device can also perform the method shown in FIG. 7 and implement the functions of the network side device in the embodiment shown in FIG. 7.
  • the embodiments of the present application are not described herein again.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be caused to perform the method of the embodiment shown in FIG. 7 and specifically for performing the following operations:
  • the URL LC uplink transmission time domain resource When receiving the data of the URLLC service, the URL LC uplink transmission time domain resource receives the data of the URLLC service using the corresponding HARQ process.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, Phase-Change Memory (PCM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), and other types of Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable ROM (EEPROM), Flash Memory or other memory technology, CD-ROM Read Disc ROM (CD-ROM), Digital Video Disc (DVD) or other optical storage, magnetic cassette, magnetic tape storage or other magnetic storage device or any other non-transport medium, Can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Landscapes

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

Abstract

本申请实施例公开了一种URLLC中上行免授权传输的方法、用户侧设备、网络侧设备，该方法包括：接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；在URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，传输该URLLC业务的数据。

Description

URLLC中上行免授权传输的方法、用户侧设备和网络侧设备
相关申请的交叉引用
本申请主张在2017年8月3日在中国提交的中国专利申请号No.201710656316.X的优先权，其全部内容通过引用包含于此。
技术领域
本申请涉及通信领域，尤其涉及一种URLLC中上行免授权传输的方法、用户侧设备和网络侧设备。
背景技术
与以往的移动通信系统相比，第五代移动网络(5th generation mobile networks，5G)需要适应更加多样化的场景和业务需求。5G的主要业务场景包括增强型移动宽带(Enhance Mobile Broadband，eMBB)，超高可靠性与超低时延通信(Ultra Reliable&Low Latency Communication，URLLC)以及海量机器类通信(Massive Machine Type Communication，mMTC)。这些场景对通信系统提出了高可靠，低时延，大带宽，广覆盖等要求。
对于某些场景的业务，要求低延时和高可靠的传输。为保证低时延要求，缩小符号持续时间(duration)的长度，降低环回延时是有效的手段；为保证高可靠性传输，需要考虑一些分集传输机制，例如时间分集、空间分集，码域分集等。
相关技术中，对于URLLC上行免授权传输，5G基站(gNB)会配置一些资源或参数，一旦用户端(User Equipment，UE)业务到达，即可在配置的资源进行传输，节省授权调度的时延。对于URLLC上行免授权传输可以支持多个混合自动重传(Hybrid automatic repeat request，HARQ)进程，但是由于URLLC业务到达的随机性，gNB无法知道UE使用哪个HARQ进程。
发明内容
第一方面，提出了一种URLLC业务的上行免授权传输方法，由用户侧 设备执行，该方法包括：
接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
第二方面，提出了一种用户侧设备，该装置包括：
接收单元，接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
发送单元，当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
第三方面，提出了一种用户侧设备，该用户侧设备包括：
处理器；以及
被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行以下操作：
接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
第四方面，提出了一种计算机可读存储介质，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行以下操作：
接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
第五方面，提出了一种URLLC中上行免授权传输方法，应用于网络侧设备，该方法包括：
发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存该URLLC业务的数据。
第六方面，提出了一种网络侧设备，该装置包括：
发送单元，发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
接收单元，当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存该URLLC业务的数据。
第七方面，提出了一种网络侧设备，该网络侧设备包括：
处理器；以及
被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行以下操作：
发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存该URLLC业务的数据。
第八方面，提出了一种计算机可读存储介质，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行以下操作：
发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存该URLLC业务的数据。
附图说明
为了更清楚地说明本申请实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附 图。
图1是本申请的一个实施例URLLC中上行免授权传输方法流程图；
图2是本申请的一个实施例URLLC上行传输时域资源与HARQ进程的对应关系示意图；
图3是本申请的一个实施例URLLC中上行免授权传输的方法示意图；
图4是本申请的一个实施例URLLC中上行免授权传输的方法示意图；
图5是本申请的一个实施例URLLC中上行免授权传输的方法示意图；
图6是本申请的一个实施例URLLC中上行免授权传输的方法示意图；
图7是本申请的一个实施例URLLC中上行免授权传输的方法流程图；
图8是本申请的一个实施例用户侧设备的结构示意图；
图9是本申请的再一个实施例用户侧设备的结构示意图；
图10是本申请的一个实施例网络侧设备的结构示意图；
图11是本申请的再一个实施例网络侧设备的结构示意图。
具体实施方式
本申请实施例提供一种URLLC中上行免授权传输方法、用户侧设备、网络侧设备。
为了使本技术领域的人员更好地理解本申请中的技术方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有付出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
本申请的技术方案，可以应用于各种通信系统，例如：全球移动通讯系统(Global System of Mobile communication，GSM)，码分多址(Code Division Multiple Access，CDMA)系统，宽带码分多址(Wideband Code Division Multiple Access，WCDMA)，通用分组无线业务(General Packet Radio Service，GPRS)，长期演进(Long Term Evolution，LTE)/增强长期演进(Long Term Evolution-advanced，LTE-A)，NR(New Radio)等。
用户端(User Equipment，UE)，也可称之为移动终端(Mobile Terminal)、 移动用户设备等，可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，用户设备可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。
基站，可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(eNB或e-NodeB(Evolved Node B))及5G基站(gNB)，本申请并不限定，但为描述方便，下述实施例以gNB为例进行说明。
图1是本申请的一个实施例URLLC中上行免授权传输方法流程图。图1的方法由用户侧设备执行。应理解，在本申请实施例中，用户侧设备可以是UE等设备。该方法可包括：
S101，接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系。
应理解，在本申请实施例中，URLLC上行传输时域资源与HARQ进程标识的对应关系，可以是预配置的表格。
例如，配置参数中可以规定多个URLLC上行传输时域资源属于一个HARQ进程。其中，在每个URLLC上行传输时域资源，可以进行一次信息传输。
图2是本申请的一个实施例URLLC上行传输时域资源与HARQ进程的对应关系示意图。在图2所示的应用场景中，一个HARQ进程对应于4个URLLC上行传输时域资源。如图2所示，HARQ进程1对应于URLLC上行传输时域资源t1-t4，HARQ进程2对应于URLLC上行传输时域资源t5-t8，HARQ进程3对应于URLLC上行传输时域资源t9-t12，等等。
当然，在具体的应用中，URLLC上行传输时域资源与HARQ进程标识的对应关系也可以采用其它方式表示，本申请实施例对此不做限制。
可选地，该配置参数还包括第二指示信息，该第二指示信息指示传输次数。应理解，一般情况下，使用一个HARQ进程发送相同传输块(transport block，TB)的次数，为该TB的传输次数。为简化描述，本文使用一个HARQ进程 所对应的URLLC上行传输时域资源的个数，即为传输次数。例如，在图2所示的应用场景中，传输次数为4次。
可选地，该配置参数还包括第四指示信息。
可选地，该第四指示信息指示该URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序。例如，在图2所示的应用场景中，第四指示信息可指示冗余版本Rv0-Rv3共4个冗余版本，并指示其发送顺序为Rv0、Rv2、Rv3、Rv1。
或者，可选地，该第四指示信息指示该URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。例如，在图2所示的应用场景中，第四指示信息可指示t1、t2、t3、t4对应的冗余版本分别为Rv0、Rv2、Rv3、Rv1。
S102，当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
应理解，根据第一指示信息指示的URLLC上行传输时域资源与HARQ进程标识的对应关系，结合UE发送URLLC业务所使用的URLLC上行传输时域资源，网络侧设备可以知道UE侧使用哪个HARQ进程号，从而使得UE侧和网络侧能够对传输URLLC业务所使用的HARQ进程保持相同的理解。
本申请实施例中，通过配置HARQ进程与时域资源的对应关系，以便用户侧设备在URLLC上行传输时域资源向网络侧设备传输时，网络侧设备可以准确得到用户侧设备传输所使用的HARQ进程，从而保证URLLC业务的上行免授权传输。
可选地，作为一个实施例，步骤S102具体实现为：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源上，使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于该URLLC业务的数据；
其中，该方法还包括：
接收调度信息，该调度信息用于指示在第二URLLC上行传输时域资源上重传第一HARQ进程发送的第一传输块的数据。
应理解，最近可用的第一URLLC上行传输时域资源，是指该URLLC业 务到达的当前时刻之后最近可用的URLLC上行传输时域资源，或者说该URLLC业务到达的当前时刻之后下一个可用的URLLC上行传输时域资源。下面提到的最近可用的第一URLLC上行传输时域资源与此类似，不再赘述。
应理解，第二URLLC上行传输时域资源可以与第二HARQ进程对应的上行传输时域资源不同。
本申请实施例中，当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源上，使用第一HARQ进程发送第一传输块的数据，然后如果接收到网络侧设备根据第一传输块后发送的调度信息，则根据调度信息进行重传。
图3是本申请的一个实施例URLLC中上行免授权传输的方法示意图。如图3所示，假设URLLC业务在t2和t3时刻之间到达，用户侧设备，例如UE等，UE使用最近的可用时域资源，即t3，以发送传输块(Transport block，TB)。其中，该TB属于URLLC业务的数据。此时，HARQ进程1能够使用的时域资源包括t3和t4，即重复传输次数为2。
同时，为保证URLLC业务的可靠性，后续可根据网络侧设备的调度来保证URLLC业务的数据的可靠性。即，当网络侧设备接收到传输块后，可向用户侧设备发送调度信息，指示用户侧设备在调度信息所指示的时域资源上发送相同传输块的数据。
应理解，相同传输块的数据，一般指相同传输块的相同或不同的冗余版本。当然，网络侧设备发送的调度信息中，还可携带冗余版本的标识信息。
应理解，一般情况下，网络侧设备在一次调度中，可调度用户侧设备发送相同传输块的一个冗余版本。当然，也不排除网络侧设备在一次调度中调度用户侧设备发送相同传输块的多个冗余版本的情况。
应理解，在本申请实施例中，网络侧设备发送调度信息以调度UE侧设备发送传输块的次数，可以等于配置参数所指示的传输次数，或者不等于配置参数所指示的传输次数。
可选地，作为另一个实施例，可选地，作为一个实施例，步骤S102具体实现为：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源上，使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一 传输块的数据，第一传输块属于该URLLC业务的数据，第一HARQ进程发送的数据中还携带第三指示信息，该第三指示信息用于指示发送该URLLC业务的数据的第一HARQ进程与后续相邻的第二HARQ进程是否用于发送相同传输块的数据。
进一步地，在本申请实施例的一种实现方式中，在步骤S102之后，该方法还包括：当该第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块时，在第二HARQ进程对应的URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程发送第一传输块的数据，该剩余传输次数为该第二指示信息指示的传输次数减去使用第一HARQ进程对应的上行传输时域资源发送第一传输块的次数。
图4是本申请的一个实施例URLLC中上行免授权传输的方法示意图。与图3类似，假设URLLC业务在t2和t3时刻之间到达，用户侧设备，例如UE等，使用最近的可用时域资源，即t3，以发送传输块。其中，该TB属于URLLC业务的数据。此时，HARQ进程1能够使用的时域资源包括t3和t4，即重复传输次数为2。
此外，在本申请实施例中，HARQ进程1发送的数据中除了TB的数据外，还可包括一个指示信息，用于指示HARQ进程1之后的相邻HARQ进程即HARQ进程2，与HARQ进程1是否用于发送相同传输块的数据。当然，应理解，在本申请实施例中，可以在用于发送数据的上行传输时域资源中使用解调参考信号(Demodulation Reference Signal，DMRS)序列或上行控制信息(Uplink Control Information)承载该指示信息。该指示信息可以使用DMRS的1比特(bit)或占用上行控制信息(Uplink Control Information，UCI)的1bit。
当HARQ进程1发送的数据中的指示信息指示HARQ进程1与HARQ进程2用于发送相同传输块的数据，则用户侧设备可在HARQ进程2对应的上行传输时域资源发送HARQ进程1所发送的传输块的数据，HARQ进程1与HARQ进程2中所发送的同一传输块的次数等于传输次数。例如，在图4所示场景中，可在t5和t6两个上行传输时域资源使用HARQ进程1发送该相同传输块的其它冗余版本。
或者，进一步地，在本申请实施例的另一种实现方式中，步骤S102之后，该方法还包括：当该第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上使用第一HARQ进程发送的第一传输块的数据。
图5是本申请的一个实施例URLLC中上行免授权传输的方法示意图。与图3类似，假设URLLC业务在t2和t3时刻之间到达，用户侧设备，例如UE等，使用最近的可用时域资源，即t3，以发送传输块。其中，该TB属于URLLC业务的数据。此时，HARQ进程1能够使用的时域资源包括t3和t4，即重复传输次数为2。
与图4的应用场景类似，在本申请实施例中，HARQ进程1发送的数据中除了TB的数据外，还可包括一个指示信息，用于指示HARQ进程1之后的相邻HARQ进程即HARQ进程2，与HARQ进程1是否用于发送相同传输块的数据。
当HARQ进程1发送的数据中的指示信息指示HARQ进程1与HARQ进程2用于发送相同传输块的数据，则用户侧设备可在HARQ进程2的所有对应的上行传输时域资源上发送HARQ进程1所发送的传输块的数据。例如，在图5所示场景中，用户侧设备可在t5-t8共四个上行传输时域资源使用HARQ进程1发送该相同传输块的冗余版本。
当然，应理解，在本申请实施例中，也可以使用DMRS序列或UCI携带一个指示信息，指示当前上行传输时域资源对应的当前HARQ进程后续相邻的HARQ进程与当前HARQ进程是否用于发送相同传输块的数据。
可选地，作为再一个实施例，步骤S102具体实现为：当URLLC业务到达后，在当前时刻对应的HARQ进程后续相邻的HARQ进程对应的URLLC上行传输时域资源上，使用该后续相邻的HARQ进程，发送该URLLC业务的数据。
图6是本申请的一个实施例URLLC中上行免授权传输的方法示意图。与图3类似，假设URLLC业务在t2和t3时刻之间到达。在图6所示的应用场景中，用户侧设备可使用URLLC业务到达时刻对应的HARQ进程后续相邻的HARQ进程发送传输块。具体的，在图6中，用户侧设备可在t5-t8共 四个上行传输时域资源，即配置的传输次数，使用HARQ进程2发送传输块的所有冗余版本。
图7是本申请的一个实施例URLLC中上行免授权传输的方法流程图。图7的方法由网络侧设备执行。应理解，在本申请实施例中，网络侧设备可以是基站等设备。该方法包括：
S701，发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系。
可选地，该配置参数还包括第二指示信息，该第二指示信息指示传输次数。
可选地，该配置参数还包括第四指示信息。可选地，该第四指示信息指示该URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序。或者，可选地，该第四指示信息指示该URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。
配置参数的具体形式可参考图1的步骤S101中的配置参数，不再赘述。
S702，当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源使用对应的HARQ进程缓存该URLLC业务的数据。
本申请实施例中，通过配置HARQ进程与时域资源的对应关系，以便用户侧设备在URLLC上行传输时域资源向网络侧设备传输时，网络侧设备可以准确得到用户侧设备传输所使用的HARQ进程，从而保证URLLC业务的上行免授权传输。
可选地，作为一个实施例，步骤S702具体实现为：当检测到第一URLLC上行传输时域资源上存在待接收的URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于该URLLC业务的数据。
应理解，不管用户侧设备在URLLC业务到达时刻对应的HARQ进程发送传输块，还是在URLLC业务到达时刻对应的HARQ进程后续相邻的HARQ进程发送传输块，当网络侧设备检测到一个URLLC上行传输时域资源上存在待接收的URLLC业务的数据时，即可使用该URLLC上行传输时域资源对应的HARQ进程缓存该URLLC上行传输时域资源所接收的传输块的数据。
进一步地，如果第一HARQ进程缓存的第一传输块未正确接收，该方法还包括：发送调度信息，该调度信息用于指示用户侧设备在第二URLLC上行传输时域资源重传该第一HARQ进程所缓存的第一传输块的数据。
以图3所示的应用场景为例，假设URLLC业务在t2和t3时刻之间到达。用户侧设备，例如UE等，在上行传输时域资源t3和t4上使用HARQ进程1发送传输块。网络侧设备，例如基站等，在上行传输时域资源t3和t4检测到有URLLC业务的数据到达后，可使用上行传输时域资源t3和t4对应的HARQ进程1缓存传输块的数据。然后，基站等网络侧设备可根据上行传输时域资源使用情况，向用户侧设备发送调度信息，该调度信息指示用户侧设备在不同于配置的上行传输时域资源上传相同传输块的数据。在该调度的上行传输时域资源上，基站等网络侧设备使用HARQ进程1缓存相同传输块的冗余版本。
应理解，在本申请实施例中，网络侧设备发送调度信息以调度UE侧设备进行上传的次数，可以等于配置参数所指示的传输次数，或者不等于配置参数所指示的传输次数。
当然，应理解，相应的，网络侧设备可在第二URLLC上行传输时域资源上使用第一HARQ进程缓存第二URLLC上行传输时域资源所接收的第一传输块的数据。
可选地，作为另一个实施例，该第一HARQ进程所缓存的数据中还携带第三指示信息，该第三指示信息用于指示第一HARQ进程与后续相邻的第二HARQ进程是否用于缓存相同传输块的数据。
进一步地，在本申请实施例的一种实现方式中，步骤S702具体实现为：
使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于该URLLC业务的数据；
当第一HARQ进程缓存的数据还携带第三指示信息，且该第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程缓存第一传输块的数据，该剩余传输次数为该第二指示信 息指示的传输次数减去使用第一HARQ进程对应上行传输时域资源传输的第一传输块的次数。
以图4所示的应用场景为例。当网络侧设备在t3、t4通过HARQ进程1缓存传输块的数据后，还可根据缓存的数据中携带的指示信息，确定HARQ进程2与HARQ进程1用于发送相同传输块的数据，然后在t5和t6两个上行传输时域资源使用HARQ进程1缓存该相同传输块的其它冗余版本。
当然，应理解，在本申请实施例中，还可以通过接收的DMRS序列或UCI中携带的指示信息，指示当前上行传输时域资源对应的当前HARQ进程后续相邻的HARQ进程与当前HARQ进程是否用于发送相同传输块的数据。
可选地，作为再一个实施例，步骤S702具体实现为：
使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于该URLLC业务的数据；
当第一HARQ进程缓存的数据还携带第三指示信息，且该第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，使用第二HARQ进程缓存第一传输块的数据。
以图5所示的应用场景为例。当网络侧设备在t3、t4通过HARQ进程1缓存传输块的数据后，还可根据缓存的数据中携带的指示信息，确定HARQ进程2与HARQ进程1用于发送相同传输块的数据，并在t5-t8共四个上行传输时域资源使用HARQ进程1缓存该相同传输块的冗余版本。
当然，应理解，在本申请实施例中，也可以通过接收的DMRS序列或UCI中携带的指示信息，指示当前上行传输时域资源对应的当前HARQ进程后续相邻的HARQ进程与当前HARQ进程是否用于发送相同传输块的数据。
图8是本申请的一个实施例用户侧设备800的结构示意图。如图8所示，用户侧设备可包括：
接收单元801，接收配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
发送单元802，当URLLC业务到达后，在可用的URLLC上行传输时域 资源使用对应的HARQ进程，发送该URLLC业务的数据。
本申请实施例中，通过配置HARQ进程与时域资源的对应关系，以便用户侧设备在URLLC上行传输时域资源向网络侧设备传输时，网络侧设备可以准确得到用户侧设备传输所使用的HARQ进程，从而保证URLLC业务的上行免授权传输。
可选地，该配置参数还包括第二指示信息，该第二指示信息指示传输次数。
可选地，该配置参数还包括第四指示信息。可选地，该第四指示信息指示该URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示该URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。
进一步地，发送单元802具体用于：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源上，使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于该URLLC业务的数据；
接收单元801，还接收调度信息，该调度信息用于指示在第二URLLC上行传输时域资源上重传第一HARQ进程发送的第一传输块的数据；
发送单元802具体还用于：在第二URLLC上行传输时域资源上根据gNB调度使用第一HARQ进程重传第一传输块的数据。
可选地，作为另一个实施例，发送单元802具体用于：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源上，使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于该URLLC业务的数据，第一HARQ进程发送的数据中还携带第三指示信息，该第三指示信息用于指示发送该URLLC业务的数据的第一HARQ进程与后续相邻的第二HARQ进程是否用于发送相同传输块的数据。
进一步地，在本申请实施例的一种实现方式中，发送单元802具体还用于：当该第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上使用第一HARQ进程发送第一传输块的数据。
或者，进一步地，在本申请实施例的另一种实现方式中，发送单元802具体还用于：当该第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块时，在第二HARQ进程对应的URLLC上行传输时域资源上，按剩余传输次数使用第二HARQ进程发送第一传输块的数据，该剩余传输次数为该第二指示信息指示的传输次数减去使用第一HARQ进程对应的上行传输时域资源发送第一传输块的次数。
可选地，作为再一种实施例，发送单元802具体用于：当URLLC业务到达后，在当前时刻对应的HARQ进程的后续相邻的HARQ进程对应的URLLC上行传输时域资源上，使用该后续相邻的HARQ进程，发送该URLLC业务的数据。
用户侧设备800还可执行图1所示的方法，并实现用户侧设备在图1所示实施例的功能，本申请实施例在此不再赘述。
图9是本申请的再一个实施例用户侧设备900的结构示意图。图9是本申请的一个实施例用户侧设备900的结构示意图。用户侧设备900的实体装置结构示意图可如图9所示，包括处理器902、存储器903、发射机901和接收机904。具体的应用中，发射机901和接收机904可以耦合到天线905。
存储器903，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器903可以包括只读存储器和随机存取存储器，并向处理器902提供指令和数据。存储器903可能包含高速随机存取存储器(Random Access Memory，RAM)存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少1个磁盘存储器。
处理器902，执行存储器903所存放的程序。
具体地，在用户侧设备900中，处理器902可通过接收机904和发射机901执行以下方法：
接收配置参数，该配置参数指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
上述如本申请图1所示实施例揭示的用户侧设备执行的方法可以应用于 处理器902中，或者由处理器902实现。处理器902可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器902中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器902可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器903，处理器902读取存储器903中的信息，结合其硬件完成上述方法的步骤。
用户侧设备900还可执行图1所示的方法，并实现用户侧设备在图1所示实施例的功能，本申请实施例在此不再赘述。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图1所示实施例的方法，并具体用于执行以下操作：
接收配置参数，该配置参数指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送该URLLC业务的数据。
图10是本申请的一个实施例网络侧设备1000的结构示意图。如图10所示，网络侧设备1000可包括：
发送单元1001，发送配置参数，该配置参数包括第一指示信息，该第一指示信息指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
接收单元1002，当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源使用对应的HARQ进程缓存该URLLC业务的数据。
本申请实施例中，通过配置HARQ进程与时域资源的对应关系，以便用户侧设备在URLLC上行传输时域资源向网络侧设备传输时，网络侧设备可以准确得到用户侧设备传输所使用的HARQ进程，从而保证URLLC业务的上行免授权传输。
可选的，该配置参数还包括第二指示信息，该第二指示信息指示传输次数。
可选地，该配置参数还包括第四指示信息。可选地，该第四指示信息指示该URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示该URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。
可选地，作为一个实施例，接收单元1002具体用于：当检测到第一URLLC上行传输时域资源上存在待接收的URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于该URLLC业务的数据。
进一步地，发送单元1001还用于发送调度信息，该调度信息用于指示用户侧设备在第二URLLC上行传输时域资源重传该第一HARQ进程所缓存的第一传输块的数据。
可选地，作为另一个实施例，接收单元1002具体用于：
使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于该URLLC业务的数据，该第一HARQ进程所缓存的数据中还携带第三指示信息，该第三指示信息用于指示第一HARQ进程与后续相邻的第二HARQ进程是否用于缓存相同传输块的数据。
进一步地，在本实施例的一种实现方式中，接收单元1002具体还用于：
当该第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源 上，使用第一HARQ进程缓存第一传输块的数据。
或者，进一步地，在本实施例的另一种实现方式中，接收单元1002具体还用于：
当该第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程缓存第一传输块的数据，该剩余传输次数为该第二指示信息指示的传输次数减去使用第一HARQ进程对应的上行传输时域资源传输第一传输块的次数。
网络侧设备1000还可执行图7所示的方法，并实现网络侧设备在图7所示实施例的功能，本申请实施例在此不再赘述。
图11是本申请的再一个实施例网络侧设备1100的结构示意图。图11是本申请的一个实施例网络侧设备1100的结构示意图。网络侧设备1100的实体装置结构示意图可如图11所示，包括处理器1102、存储器1103、发射机1101和接收机1104。具体的应用中，发射机1101和接收机1104可以耦合到天线1105。
存储器1103，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1103可以包括只读存储器和随机存取存储器，并向处理器1102提供指令和数据。存储器1103可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少1个磁盘存储器。
处理器1102，执行存储器1103所存放的程序。
具体地，在网络侧设备1100中，处理器1102可通过接收机1104和发射机1101执行以下方法：
发送配置参数，该配置参数指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源使用对应的HARQ进程缓存该URLLC业务的数据。
上述如本申请图7所示实施例揭示的网络侧设备执行的方法可以应用于处理器1102中，或者由处理器1102实现。处理器1102可能是一种集成电路 芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1102中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1102可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1103，处理器1102读取存储器1103中的信息，结合其硬件完成上述方法的步骤。
网络侧设备还可执行图7所示的方法，并实现网络侧设备在图7所示实施例的功能，本申请实施例在此不再赘述。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图7所示实施例的方法，并具体用于执行以下操作：
发送配置参数，该配置参数指示URLLC上行传输时域资源与HARQ进程标识的对应关系；
当接收URLLC业务的数据时，在接收该URLLC业务的数据的URLLC上行传输时域资源使用对应的HARQ进程缓存该URLLC业务的数据。
总之，以上所述仅为本申请的可选实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相 机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(Phase-Change Memory，PCM)、静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(Read-Only Memory，ROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable ROM，EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(Compact Disc ROM，CD-ROM)、数字多功能光盘(Digital Video Disc，DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。

Claims (36)

  1. 一种超高可靠性与超低时延通信URLLC中上行免授权传输的方法，由用户侧设备执行，包括：
    接收配置参数，所述配置参数包括第一指示信息，所述第一指示信息指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
    当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据。
  2. 如权利要求1所述的方法，其中，
    所述配置参数还包括第二指示信息，所述第二指示信息指示传输次数。
  3. 如权利要求2所述的方法，其中，
    当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据，包括：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于所述URLLC业务的数据；
    所述方法还包括：
    接收调度信息，所述调度信息用于指示在第二URLLC上行传输时域资源上重传第一HARQ进程发送的第一传输块的数据。
  4. 如权利要求2所述的方法，其中，
    当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据，包括：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于所述URLLC业务的数据，第一HARQ进程发送的数据中还携带第三指示信息，所述第三指示信息用于指示发送所述URLLC业务的数据的第一HARQ进程与后续相邻的第二HARQ进程是否用于发送相同传输块的数据。
  5. 如权利要求4所述的方法，还包括，
    在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述 URLLC业务的数据之后，
    当所述第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上使用第一HARQ进程发送所述第一HARQ进程所发送的第一传输块的数据。
  6. 如权利要求4所述的方法，还包括，
    在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据之后，
    当所述第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块时，在第二HARQ进程对应的URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程发送第一传输块的数据，所述剩余传输次数为所述第二指示信息指示的传输次数减去使用第一HARQ进程对应的URLLC上行传输时域资源发送第一传输块的次数。
  7. 如权利要求1或2所述的方法，其中，
    当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据，包括：
    当URLLC业务到达后，如果当前时刻对应的该进程的一个传输块的传输次数小于配置的传输次数，在当前时刻对应的HARQ进程后续相邻的HARQ进程对应的URLLC上行传输时域资源上，使用所述后续相邻的HARQ进程，发送所述URLLC业务的数据。
  8. 如权利要求2所述的方法，其中，
    所述配置参数还包括第四指示信息，所述第四指示信息指示所述URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示所述URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源使用的冗余版本。
  9. 一种超高可靠性与超低时延通信URLLC中上行免授权传输的方法，应用于网络侧设备，包括：
    发送配置参数，所述配置参数包括第一指示信息，所述第一指示信息指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
    当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据。
  10. 如权利要求9所述的方法，其中，
    所述配置参数还包括第二指示信息，所述第二指示信息指示传输次数。
  11. 如权利要求10所述的方法，其中，
    当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据，包括：当检测到第一URLLC上行传输时域资源上存在待接收的所述URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于所述URLLC业务的数据。
  12. 如权利要求11所述的方法，还包括，
    如果第一HARQ进程缓存的第一传输块未接收正确，发送调度信息，所述调度信息用于指示用户侧设备在第二URLLC上行传输时域资源重传所述第一HARQ进程所缓存的第一传输块的数据。
  13. 如权利要求9所述的方法，其中，
    当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据，包括：当检测到第一URLLC上行传输时域资源上存在待接收的所述URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于所述URLLC业务的数据，所述URLLC业务的数据还携带第三指示信息，所述第三指示信息用于指示第一HARQ进程与后续相邻的第二HARQ进程是否用于缓存相同传输块的数据。
  14. 如权利要求13所述的方法，还包括，
    当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据之后，
    当所述第三指示信息指示第一HARQ进程与第二HARQ进程缓存相同传 输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，使用第一HARQ进程缓存第一传输块的数据。
  15. 如权利要求13所述的方法，还包括，
    当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据之后，
    当所述第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程缓存第一传输块的数据，所述剩余传输次数为第二指示信息指示的传输次数减去使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一传输块的次数。
  16. 如权利要求10所述的方法，其中，
    所述配置参数还指示所述URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示所述URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。
  17. 一种用户侧设备，包括：
    接收单元，接收配置参数，所述配置参数包括第一指示信息，所述第一指示信息指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
    发送单元，当URLLC业务到达后，在可用的URLLC上行传输时域资源使用对应的HARQ进程，发送所述URLLC业务的数据。
  18. 如权利要求17所述的用户侧设备，其中，
    所述配置参数还包括第二指示信息，所述第二指示信息指示传输次数。
  19. 如权利要求18所述的用户侧设备，其中，
    所述发送单元用于：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于所述URLLC业务的数据；
    所述接收单元，还接收调度信息，所述调度信息用于指示在第二URLLC上行传输时域资源上重传第一HARQ进程发送的第一传输块的数据。
  20. 如权利要求18所述的用户侧设备，其中，
    所述发送单元用于：当URLLC业务到达后，在最近可用的第一URLLC上行传输时域资源使用第一URLLC上行传输时域资源对应的第一HARQ进程发送第一传输块的数据，第一传输块属于所述URLLC业务的数据，第一HARQ进程发送的数据中还携带第三指示信息，所述第三指示信息用于指示发送所述URLLC业务的数据的第一HARQ进程与后续相邻的第二HARQ进程是否用于发送相同传输块的数据。
  21. 如权利要求20所述的用户侧设备，其中，
    所述发送单元还用于：当所述第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上使用第一HARQ进程发送所述第一传输块的数据。
  22. 如权利要求20所述的用户侧设备，其中，
    所述发送单元还用于：当所述第三指示信息用于指示第一HARQ进程与第二HARQ进程用于发送相同传输块时，在第二HARQ进程对应的URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程发送第一传输块的数据，所述剩余传输次数为所述第二指示信息指示的传输次数减去使用第一HARQ进程对应的URLLC上行传输时域资源发送第一传输块的次数。
  23. 如权利要求17或18所述的用户侧设备，其中，
    所述发送单元用于：当URLLC业务到达后，在当前时刻对应的HARQ进程的后续相邻的HARQ进程对应的URLLC上行传输时域资源上，使用所述后续相邻的HARQ进程，发送所述URLLC业务的数据。
  24. 如权利要求18所述的用户侧设备，其中，
    所述配置参数还包括第四指示信息，所述第四指示信息指示所述URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示所述URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源使用的冗余版本。
  25. 一种网络侧设备，包括：
    发送单元，发送配置参数，所述配置参数包括第一指示信息，所述第一 指示信息指示URLLC上行传输时域资源与混合自动重传HARQ进程标识的对应关系；
    接收单元，当接收URLLC业务的数据时，在接收所述URLLC业务的数据的URLLC上行传输时域资源上，使用对应的HARQ进程缓存所述URLLC业务的数据。
  26. 如权利要求25所述的网络侧设备，其中，
    所述配置参数还包括第二指示信息，所述第二指示信息指示传输次数。
  27. 如权利要求26所述的网络侧设备，其中，
    所述接收单元用于：当检测到第一URLLC上行传输时域资源上存在待接收的所述URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于所述URLLC业务的数据。
  28. 如权利要求27所述的网络侧设备，其中，
    所述发送单元还用于：如果第一HARQ进程缓存的第一传输块未接收正确，发送调度信息，所述调度信息用于指示用户侧设备在第二URLLC上行传输时域资源重传所述第一HARQ进程所缓存的第一传输块的数据。
  29. 如权利要求26所述的网络侧设备，其中，
    所述接收单元用于：当检测到第一URLLC上行传输时域资源上存在待接收的所述URLLC业务的数据时，使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一URLLC上行传输时域资源所接收的第一传输块的数据，第一传输块属于所述URLLC业务的数据，所述URLLC业务的数据还携带第三指示信息，所述第三指示信息用于指示第一HARQ进程与后续相邻的第二HARQ进程是否用于缓存相同传输块的数据。
  30. 如权利要求29所述的网络侧设备，其中，
    所述接收单元还用于：
    当所述第三指示信息指示第一HARQ进程与第二HARQ进程缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，使用第一HARQ进程缓存第一传输块的数据。
  31. 如权利要求29所述的网络侧设备，其中，
    所述接收单元还用于：
    当所述第三指示信息指示第一HARQ进程与第二HARQ进程用于缓存相同传输块的数据时，在第二HARQ进程对应的所有URLLC上行传输时域资源上，按剩余传输次数使用第一HARQ进程缓存第一传输块的数据，所述剩余传输次数为第二指示信息指示的传输次数减去使用第一URLLC上行传输时域资源对应的第一HARQ进程缓存第一传输块的次数。
  32. 如权利要求26所述的网络侧设备，其中，
    所述配置参数还指示所述URLLC业务的数据在传输次数中每次发送的冗余版本及冗余版本的发送顺序，或者指示所述URLLC业务的数据在HARQ进程对应的URLLC上行传输时域资源的冗余版本。
  33. 一种用户侧设备，包括：
    处理器；以及
    被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行如权利要求1-8中任一项所述的方法。
  34. 一种计算机可读存储介质，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行如权利要求1-8中任一项所述的方法。
  35. 一种网络侧设备，包括：
    处理器；以及
    被安排成存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行如权利要求9-16中任一项所述的方法。
  36. 一种计算机可读存储介质，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行如权利要求9-16中任一项所述的方法。
PCT/CN2018/098301 2017-08-03 2018-08-02 Urllc中上行免授权传输的方法、用户侧设备和网络侧设备 Ceased WO2019024891A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18842295.0A EP3661290B1 (en) 2017-08-03 2018-08-02 Uplink grant-free transmission method in urllc, user side device, and network side device
US16/631,648 US11357027B2 (en) 2017-08-03 2018-08-02 Uplink grant-free transmission method in URLLC, terminal side device and network side device
ES18842295T ES2941834T3 (es) 2017-08-03 2018-08-02 Método de transmisión sin concesión de enlace ascendente URLLC, dispositivo del lado del usuario y dispositivo del lado de la red

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710656316.XA CN109392099B (zh) 2017-08-03 2017-08-03 Urllc中上行免授权传输的方法、用户侧设备和网络侧设备
CN201710656316.X 2017-08-03

Publications (1)

Publication Number Publication Date
WO2019024891A1 true WO2019024891A1 (zh) 2019-02-07

Family

ID=65232274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098301 Ceased WO2019024891A1 (zh) 2017-08-03 2018-08-02 Urllc中上行免授权传输的方法、用户侧设备和网络侧设备

Country Status (5)

Country Link
US (1) US11357027B2 (zh)
EP (1) EP3661290B1 (zh)
CN (1) CN109392099B (zh)
ES (1) ES2941834T3 (zh)
WO (1) WO2019024891A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114731664A (zh) * 2020-02-07 2022-07-08 Oppo广东移动通信有限公司 信号传输方法、装置及其设备

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108988995B (zh) * 2017-06-02 2020-07-24 华为技术有限公司 一种数据传输的方法和装置
JP7350017B2 (ja) 2018-05-21 2023-09-25 オッポ広東移動通信有限公司 サービス伝送のための方法、装置及び端末
CN111988121A (zh) * 2019-05-24 2020-11-24 中国电信股份有限公司 基于免调度的数据传输方法、基站、终端以及存储介质
CN110856262B (zh) * 2019-09-25 2022-03-01 西安交通大学 一种基于联合时频分集的免授权上行传输方法
CN114303333B (zh) * 2019-11-07 2024-02-09 Oppo广东移动通信有限公司 无线通信方法及设备、终端设备和网络设备
EP4048005A4 (en) * 2019-11-08 2022-09-28 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
WO2021159533A1 (zh) * 2020-02-14 2021-08-19 Oppo广东移动通信有限公司 信息处理方法、装置、存储介质、处理器及电子装置
JP7531597B2 (ja) 2020-02-14 2024-08-09 オッポ広東移動通信有限公司 情報処理方法、装置、記憶媒体、プロセッサ、及び電子デバイス
CN114070478B (zh) * 2020-08-07 2023-06-30 大唐移动通信设备有限公司 一种信息传输方法、终端及网络侧设备
US11968662B2 (en) * 2021-03-23 2024-04-23 Qualcomm Incorporated Uplink configured grant transmission repetition techniques in wireless communications
US12481572B2 (en) * 2021-09-16 2025-11-25 Apple Inc. Control of computer system operation using sensor data

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106255215A (zh) * 2016-08-05 2016-12-21 宇龙计算机通信科技(深圳)有限公司 通信方法及通信装置
CN106385709A (zh) * 2016-10-31 2017-02-08 宇龙计算机通信科技(深圳)有限公司 资源调度方法及资源调度装置
US20170171842A1 (en) * 2015-12-11 2017-06-15 Lg Electronics Inc. Method and user equipment for receiving dowlink channel, and method and base station for transmitting downlink channel

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106507486B (zh) * 2015-09-08 2020-04-28 华为技术有限公司 用于上行数据传输的方法、网络设备和终端设备
CN106507497B (zh) * 2015-09-08 2020-09-11 华为技术有限公司 用于上行数据传输的方法、终端设备和网络设备
CN106550439A (zh) * 2015-09-23 2017-03-29 华为技术有限公司 一种非连续接收的方法以及终端设备
US10701677B2 (en) * 2016-05-12 2020-06-30 Samsung Electronics Co., Ltd. Method and apparatus for uplink resource assignment for cellular network using unlicensed bands
CN105979597B (zh) 2016-06-27 2020-02-21 宇龙计算机通信科技(深圳)有限公司 通信资源的分配方法、分配装置、基站和终端
US10595336B2 (en) * 2016-11-15 2020-03-17 Huawei Technologies Co., Ltd. Systems and methods for grant-free uplink transmissions
JP2020036051A (ja) * 2016-12-28 2020-03-05 株式会社Ｎｔｔドコモ ユーザ装置、及びデータ送信方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170171842A1 (en) * 2015-12-11 2017-06-15 Lg Electronics Inc. Method and user equipment for receiving dowlink channel, and method and base station for transmitting downlink channel
CN106255215A (zh) * 2016-08-05 2016-12-21 宇龙计算机通信科技(深圳)有限公司 通信方法及通信装置
CN106385709A (zh) * 2016-10-31 2017-02-08 宇龙计算机通信科技(深圳)有限公司 资源调度方法及资源调度装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3661290A4 *
ZTE, ZTE MICROELECTRONICS: "HARQ for URLLC UL Grant-free transmission", 3GPP DRAFT; R1-1704428 HARQ FOR UL URLLC GRANT-FREE TRANSMISSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Spokane, USA; 20170403 - 20170407, 2 April 2017 (2017-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051242575 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114731664A (zh) * 2020-02-07 2022-07-08 Oppo广东移动通信有限公司 信号传输方法、装置及其设备

Also Published As

Publication number Publication date
EP3661290B1 (en) 2023-03-08
EP3661290A4 (en) 2020-08-19
CN109392099A (zh) 2019-02-26
US20200178273A1 (en) 2020-06-04
EP3661290A1 (en) 2020-06-03
US11357027B2 (en) 2022-06-07
ES2941834T3 (es) 2023-05-25
CN109392099B (zh) 2019-11-05

Similar Documents

Publication Publication Date Title
WO2019024891A1 (zh) Urllc中上行免授权传输的方法、用户侧设备和网络侧设备
CN111200871B (zh) 接收数据的方法和通信装置
RU2596151C2 (ru) Разработка временных характеристик планирования для системы tdd
JP7141467B2 (ja) 無線通信方法、通信デバイス、チップ及びシステム
WO2019128873A1 (zh) 一种波束训练方法及相关设备
US11122629B2 (en) Media access control protocol data unit transmission method, user equipment and network device
US20230231665A1 (en) Method for feeding back hybrid automatic repeat request acknowledgement (harq-ack) and terminal device
WO2019028771A1 (zh) 传输数据的方法和终端设备
CN110798296B (zh) 下行信号指示、接收方法和设备
WO2020140838A1 (zh) 信息传输方法、装置及设备
WO2019024114A1 (zh) 数据传输的方法、终端设备和网络设备
JP2023525249A (ja) サイドリンクフィードバック情報の送受信方法及び装置
WO2020227868A1 (zh) 传输数据的方法、终端设备和网络设备
WO2020087528A1 (zh) 无线通信方法、终端设备和网络设备
CN121263993A (zh) 用于harq-ack信息位生成及排序的方法及设备
WO2021035541A1 (zh) 一种数据传输方法及相关设备
CN114342286B (zh) 一种数据传输方法和通信设备
CN114374490A (zh) 一种物理下行控制信息的发送方法、设备和通信系统
WO2024109113A1 (en) Method and apparatus for harq-ack codebook determination based on downlink assignment index
TWI785085B (zh) 支援資料重複的方法、發射端設備和接收端設備
WO2016169479A1 (zh) 一种数据传输方法及设备
CN111757350A (zh) 信息传输方法及相关装置
CN118474887A (zh) Dci格式确定方法、设备及可读存储介质
CN114402681B (zh) 一种信息处理方法和终端设备以及网络设备
WO2019153248A1 (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: 18842295

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018842295

Country of ref document: EP

Effective date: 20200225